btnx: Send keyboard and mouse combination events with mouse buttons

[daou]

Ok, I tooled around in btnx-config to see if I could gain more understanding of why it's crashing. 90% of this is likely irrelevant, but I might as well post it anyway.

So, I tried running btnx-config from the command line to see it's output.

Warning: invalid button index reported by buttons_check_index.
No previous config file at /etc/btnx/btnx_config. No configuration loaded.
Warning: tree_buttons_empty_store could not get an iter.
Warning: tree_buttons_empty_store could not get an iter.
Aborted

The first three lines I got right as I opened btnx, and the last 2 I got right as I hit ok after detection. Also, after the window closes, btnx-config isn't running anymore.

Now if I run it with the default mxrev configuration file from /etc/btnx/defaults, I get this error:

Warning: invalid button index reported by buttons_check_index.
Warning: tree_buttons_empty_store could not get an iter.
Aborted

I tried also hitting cancel after the button detection to see if maybe that would fix some stuff. Well, it brought me back to the main screen, but that was about it. However, pressing "restart btnx" after pressing the cancel button gives me a different error, regarding to issues with /etc/init.d/btnx, which after make install-generic doesn't show up. If I do a plain ol' make install, I get errors in /etc/init.d/btnx saying "line 34: /lib/init/vars.sh: No such file or directory".

Finally, to top it all off, if I try to use btnx by itself without btnx-config, by copying the default mxrevo config over and running ./btnx, I get:

Opened handler: /dev/input/event0
Opened handler: /dev/input/event1
Opened handler: /dev/input/event2
Opened handler: /dev/input/event3
Opened handler: /dev/input/event4
Opened handler: /dev/input/event5
Opened handler: /dev/input/event6
Opened handler: /dev/input/event7
Opened handler: /dev/input/event8
Opened handler: /dev/input/event9
Opened handler: /dev/input/event10
Error opening button event file descriptor: No such file or directory

Also, to clarify on the scroll wheel thing; I wasn't binding it in btnx, however, scrolling it both before and after btnx sends two events to the computer, something I tried to rectify with lomoco --no-sms. However, lomoco doesn't seem to recognize my mouse. Any other suggestions?

Thanks for the lengthy response,
perrako

I'm not familiar with Sabayon, but hopefully it's not doing anything drastically different to cause these problems.

The default config files are leftovers from btnx-0.2.x and won't work with btnx-0.3.x. But you can make the old default MX Revo config file work, if you add this to the file:

Mouse
vendor_name = Logitech
product_name = MX Revolution
vendor_id = 0x046d
product_id = 0xc51a
EndMouse

And if you are running btnx or btnx-config from command line, make sure you are root. Otherwise, opening the event handlers won't work.

The warning messages are nothing to be worried about. However, the abort message might indicate a seg fault of some kind. If you have gdb, you could try running it to get more detailed output:

(as root)

gdb btnx-config
#now you get a gdb prompt
run

Then do whatever you did last time and see what kind of output the crash gives you.

The restart functionality probably only works on distros that use update-rc.d to make init scripts. Unless you've made a custom btnx init script for your distro that is located at /etc/init.d/btnx

[Perrako]

Sabayon is gentoo based. Also, the error I got in gdb was:

Program received signal SIGSEGV, Segmentation fault.
0xb7e3c0de in ?? () from /usr/lib/libgtk-x11-2.0.so.0

[daou]

Sabayon is gentoo based. Also, the error I got in gdb was:

Program received signal SIGSEGV, Segmentation fault.
0xb7e3c0de in ?? () from /usr/lib/libgtk-x11-2.0.so.0

It didn't give any more detailed output? What version of Gtk+ do you have? You need at least 2.10.11

You can check with the command "pkg-config --modversion gtk+-2.0"

[Perrako]

You done gone fixed it

[daou]

You done gone fixed it

Good to hear!

[daou]

I'm working on the next update to btnx, version 0.3.1. A couple of improvements will be included, such as hotplugging. This has been requested by many people (especially laptop users).

And it looks like btnx-config + btnx-0.3.x is stable enough to release. btnx-0.2.14 will still be available, but won't be updated (unless there's a really good reason).

[daou]

btnx-0.3.1 and btnx-config-0.1.6 can now be "tested". Make sure to update both programs!
They add hotplugging functionality and better support for other distros.

[daou]

No one has mentioned problems with executing Firefox using btnx until now. The command line needs to be a little bit different for Firefox because of it's startup scripts.

I've added this to the FAQ section but here it is as well:

command = /bin/su -c firefox your_username
uid = 0

Make sure UID is set to 0. But don't worry, Firefox won't run as root because su changes the user to whatever you set the your_username argument to.

EDIT: launching a web browser can also be done with KEY_WWW if you don't need to send any arguments to it.

[shimoda]

thanks for develop btnx dao...

I want to test it, but not works for me

I have a Cordless Click Plus...

and with:

$ sudo /usr/sbin/btnx

I received:

Error: no supported mice detected.

In my xorg.conf:

Section "InputDevice"
	Identifier	"Configured Mouse"
	Driver		"mouse"
	Option		"CorePointer"
	Option		"Device"		"/dev/input/mice"
	Option		"Protocol"		"auto"
	Option		"ZAxisMapping"		"4 5"
	Option		"Emulate3Buttons"	"no"
	Option		"Buttons"		"3"
EndSection

what could be wrong?

The Cordless Click Plus use the same receiver than a Cordless Keyboard... Is this important?
(newbie question? )

[daou]

thanks for develop btnx dao...

I want to test it, but not works for me

I have a Cordless Click Plus...

and with:

$ sudo /usr/sbin/btnx

I received:

Error: no supported mice detected.

In my xorg.conf:

Section "InputDevice"
    Identifier    "Configured Mouse"
    Driver        "mouse"
    Option        "CorePointer"
    Option        "Device"        "/dev/input/mice"
    Option        "Protocol"        "auto"
    Option        "ZAxisMapping"        "4 5"
    Option        "Emulate3Buttons"    "no"
    Option        "Buttons"        "3"
EndSection

what could be wrong?

The Cordless Click Plus use the same receiver than a Cordless Keyboard... Is this important?
(newbie question? )

Are you using btnx-0.2.x? If so, your Cordless Click Plus is probably using a different set of Vendor and Product IDs (possibly related to the shared receiver). btnx-0.3.x does the mouse detection differently. You could try using btnx-0.3.x and btnx-config and see if that works for you.