Well, after my last post I eventually found that
is a better way of retrieving missing X window support after first start of btnx.Code:export XAUTHORITY='/home/username/.Xauthority'
Put this in your script file along with export DISPLAY=':0.0' and your mouse button should execute X apps every time.
Hope this helps.
Hmmm... how did you get it to work? I'm using 7.10, at the moment and tried to install it from the gutsy repos, and that worked. However, when running the btnx-config it doesn't seem to actually find any event handler. I click the button, wait 5 seconds, then move my mouse around and press all the buttons but get nothing. =/
Note: I have run through the following FAQ in the past trying to get my mouse to work properly.
https://help.ubuntu.com/community/MX...9%7C%281000%29
EDIT: I did some digging in the trouble shooting sections of the manual. Figured out it was my xorg.conf file, since I had customized it to use evdev as per the above linked guide. Fixed up my xorg.conf and poof, issues resolved.
Still working on setting up the buttons, but should be able to do that now. ^.^
Last edited by oni5115; May 5th, 2008 at 06:34 AM. Reason: Figured it out...
echo -e "\x6f\x61\x73\x61\x6c\x6f\x6e\x65\x6e\x40\x67 \b\x6d\x61\x69\x6c\x2e\x63\x6f\x6d"
It compiles! Ship it!
It seems like I found a solution for "lomoco (and other similar tools) not working in hardy" problem.
I have been used lomoco to disable the smart-scrolling function and was disappointed when noticed, that this trick was not working any more. After a little research I found out that lsusb was also almost fully non-functional (only -t option was giving any output).
This lead to little bit of searching around the web and I found something like this.
After a little bit of tinkering I got this piece from there
and added it as a separate udev rule - I made it as '/etc/udev/rules.d/50-libusb.rules'Code:SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device", \ NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", MODE="0644"
Then just restart udev and here you have it - lsusb works as it should and lomoco works too.
Only one thing remains though - I had not yet managed to add this 'lomoco --no-sms' command to some elegant place to fire up. Until now it has been in '/etc/rc.local' but it would be perfect, if it could be added to '/etc/udev/rules.d/99-btnx.rules' somehow to be initiated on hotplugging...
Last edited by tim71; May 5th, 2008 at 04:59 PM.
Some of this could be integrated into btnx, the automatic exec and udev rules. However, it sounds to me like this is a bug in Hardy (especially if tools as fundamental as lsusb aren't working), and if it is, it would not be a good idea to place workarounds for it in btnx. Have you thought about filing a bug report?
Last edited by daou; May 5th, 2008 at 05:21 PM.
echo -e "\x6f\x61\x73\x61\x6c\x6f\x6e\x65\x6e\x40\x67 \b\x6d\x61\x69\x6c\x2e\x63\x6f\x6d"
It compiles! Ship it!
As I understand, it is not a bug, but just leaving the (deprecated) 'CONFIG_USB_DEVICE_CLASS' option unactivated when kernel was compiled.
http://readlist.com/lists/vger.kerne...69/347220.html
http://www.mail-archive.com/linux-ke...msg162394.html
http://www.google.com/search?q=CONFI...&start=20&sa=N
P.S. This workaround is not "being used in btnx" - I added the separate udev rule on the global system level, that has nothing to do with btnx. However this lomoco thing would be really nice to be working on hotplugging with btnx. Maybe I just did not bother to tinker enough with this lomoco/btnx udev "integration" - it just did not work when I added this action in /'etc/udev/rules.d/99-btnx.rules' although btnx itself stopped and started as it should.
Last edited by tim71; May 5th, 2008 at 06:15 PM.
echo -e "\x6f\x61\x73\x61\x6c\x6f\x6e\x65\x6e\x40\x67 \b\x6d\x61\x69\x6c\x2e\x63\x6f\x6d"
It compiles! Ship it!
It would need the additional options - lomoco has many functions as command line options.
And I would like to point out again: this lomoco udev-integrating is not Hardy-specific thing - I had this command in rc.local before (and it works there), but it's obvious, that it could use a better place for execution - especially considering the hotplugging option.
Last edited by tim71; May 5th, 2008 at 08:10 PM.
If this issue could be considered as a bug, then... someone else already has issued a bugreport.
Last edited by tim71; May 6th, 2008 at 10:51 AM.
Bookmarks