HOWTO: Configuring Logitech mice in Ubuntu 6.06: New Guide

[sudo_t43p]

I can't really say since I don't know too much about xbindkeys.

Try with [Control_R]\[ISO_Left_Tab] or [Control_R]\[Pagedown]

BR,
Chrisse

[sudo_t43p]

Can I ask what you did and what your xorg.conf looks like, mine just refuses to work, its only the app tab button and the horizontal scrolls that do not work.....

Don´t have my xorg left from testing this mouse (messing arround with lots of stuff at the moment).

But if you could post the most relevant stuff from xev I can try to help you.

[antiplex]

hi folks!

after spending hours on getting my logitech mx5000 desktop-set (mouse & keyboard) both working without deactivating the keyboards media-keys i finally got almost everything going (using feisty beta!) that i wanted, so thanks for all the hints that came along in the original howto as well as in many of the postings of the preceding 43 pages (that was a lot to read!).

in posting #368 user 'kobewan' recommended using 'xte' (can be found in the 'xautomation'-package) because it should handle keypress and releasevents better than 'xvfz'.
i don't doubt that this is correct but still have some problems getting things to work. what i try to do is to trigger my compiz-expose-plugin which currently is configured to use the key kombination of 'keydown Contol_L' + 'keydown Alt_L' + 'key Up' with mousebutton #10 of my logitech mx1000 bluetooth mouse. when using a keyboard, as soon as you release any of the still pressed 'Control_L' or 'Alt_L' keys, the expose-function will end.

so basically what kobewan posted sounds like it might be what i'm looking for, right? (... because some keys need to remain pressed for a while)
this is my current ~/.xbindkeysrc:

#button10 testing
"/usr/bin/xte 'keydown Control_L' 'keydown Alt_L' 'key Up' &"
 b:10

# workaround for releasing btn10
".btn10rel.sh &" 
 b:10 + Release

as you can see, i call a script (that of couse i made executable already) called '.btn10rel.sh' which has the following content:

#!/bin/bash
#
  /usr/bin/xte 'keyup Alt_L' 'keyup Control_L'

when i check button10 with 'xev' without haveing 'xbindkeys' running it seems to work fine because what i get is:

ButtonPress event, serial 28, synthetic NO, window 0x3000001,
    root 0x52, subw 0x0, time 3558958910, (88,66), root:(100,140),
    state 0x0, button 10, same_screen YES

ButtonRelease event, serial 28, synthetic NO, window 0x3000001,
    root 0x52, subw 0x0, time 3558960073, (88,66), root:(100,140),
    state 0x0, button 10, same_screen YES

now when i start 'xbindkeys' and run 'xev' again, this is what i get when pressing button10:

KeyPress event, serial 31, synthetic NO, window 0x3000001,
    root 0x52, subw 0x0, time 3559859591, (130,123), root:(165,203),
    state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyPress event, serial 31, synthetic NO, window 0x3000001,
    root 0x52, subw 0x0, time 3559859592, (130,123), root:(165,203),
    state 0x4, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

FocusOut event, serial 31, synthetic NO, window 0x3000001,
    mode NotifyGrab, detail NotifyAncestor

FocusOut event, serial 31, synthetic NO, window 0x3000001,
    mode NotifyUngrab, detail NotifyPointer

FocusIn event, serial 31, synthetic NO, window 0x3000001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 31, synthetic NO, window 0x0,
    keys:  1   0   0   0   32  0   0   0   1   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0

and this when releasing it:

EnterNotify event, serial 31, synthetic NO, window 0x3000001,
    root 0x52, subw 0x0, time 3559863870, (130,123), root:(165,203),
    mode NotifyUngrab, detail NotifyAncestor, same_screen YES,
    focus YES, state 12

KeymapNotify event, serial 31, synthetic NO, window 0x0,
    keys:  82  0   0   0   32  0   0   0   1   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0

all that i can see from this is that 'Control_L' and 'Alt_L' seem to get (fake-)pressed correctly, but 'Up' or everything written to my script probably never gets (fake-)pressed which is exactly what i recognize on my desktop. what i mean is: when i press button10, nothing happens (since 'Up' seems to be missing), and after releasing button 10 'Control_L' and 'Alt_L' remain pressed until i manually press them.

the script is in my homedir, is this correct?
any ideas how to get this working?

[detyabozhye]

Yes, it should be in your home dir. A lot of the xbindkeys, kvkbd, and xte stuff is a bit over my head though, so I don't really knoe about the rest.

[antiplex]

i thought that maybe 'kobewan' could help, i already pm'ed and informed him about my previous posting.
however, i guess i solved my problem in a different way by switching from compiz to beryl where the expose-function seems to bind mousclicks in a more ... let's say logitech-friendly way. scrolling left/right works fine with xbindkeys... so everything's fine for the moment

[tweedledee]

i thought that maybe 'kobewan' could help, i already pm'ed and informed him about my previous posting.
however, i guess i solved my problem in a different way by switching from compiz to beryl where the expose-function seems to bind mousclicks in a more ... let's say logitech-friendly way. scrolling left/right works fine with xbindkeys... so everything's fine for the moment

The problem with the approach you were trying is discussed at various points in another thread (http://ubuntuforums.org/showthread.php?t=316441), but the gist of it is that xbindkeys doesn't properly handle attempts to attach a script/function to both the press & release of a mouse button (in fact, it's much more reliable when bound to the release). So while what you described makes sense, it won't work. Your workaround seems to be a better solution for you.

[dpb]

Followed these how-to instructions on Edgy, and ran into a couple problems. I was wondering if anyone could help? Basically I'm getting the following in my Xorg log file:

(II) MX Rev-usb-0000:00:1d.2-2/input0: Init
(II) evdev brain: Rescanning devices (2).
(II) MX Rev-usb-0000:00:1d.2-2/input0: On
(II) MX Rev-usb-0000:00:1d.2-2/input0: Off
(II) Open ACPI successful (/var/run/acpid.socket)
(II) NVIDIA(0): Setting mode "1600x1200,1600x1200"
(II) MX Rev-usb-0000:00:1d.2-2/input0: On
(II) evdev brain: Rescanning devices (3).
(II) MX Rev-usb-0000:00:1d.2-2/input0: Off
(II) MX Rev-usb-0000:00:1d.2-2/input0: Off

Looks like the thing is being recognized, but immediately turning off. When I get up into X11, the mouse simply "doesn't work".

Any suggestions?

-D

[BLTicklemonster]

Fiesty's last upgrade had a new xorg or xorg.conf or something, and of course, seeing as how it was an upgrade, no, X would not load. So, I installed my nvidia drivers for the gazillionth time, thank you Ubuntu update writers for not figuring out how to make an upgrade put anyone's video drivers right (what good is a computer upgrade if it renders the computer useless until fiddled with). Of course every time I reboot now, x dies. Huh. Never had this problem before, so today I installed the driver and before starting x, I dpkg-reconfigure xserver-xorg, and guess what? There's a new section in there with mouse info. If you answer it ok all the way assuming that's correct, bam, my logitech mx 310 doesn't work. No scroll, no forward back buttons, nothing.

I have yet to fix this, and I've been working on it all evening.


Good God, they come out with the best Ubuntu version ever, and immediately dweeb it out.

Yay.

(certainly there's a fix on the horizon, but I'm thinking I'm going to drop feisty and go back to edgy if I can't find a fix for the mouse and the video drivers.)

*edit:

Aw great, my logout screen is gone now, too.

WTF?

[bg1256]

sudo dpkg-reconfigure -phigh xserver-xorg

As for nvidia, here's what I did:

sudo apt-get install linux-restricted-modules 'uname -r'
sudo apt-get update
sudo apt-get install nvidia-glx-new

And apparently, some people need to:

sudo nvidia-glx-config enable

Hope it helps... for what it's worth, this guide hasn't worked for me since Dapper...oh well.

[BLTicklemonster]

For nvidia, this is what worked for me:

nano /etc/default/linux-restricted-modules-common

and add the following line to the file

DISABLED_MODULES="nv nvidia"

This solution should work when you upgrade the packages next time.

as far as the mouse, you think that dpkg will work?