I've been running Maverick since the release. A quick test just pressing the buttons and trying to assign them in Keyboard shortcuts says the problem still exist. I'll try the steps outlined earlier in this thread. As was concluded in post #10 it's probably a kernel bug. I'm not sure where Martin Pitts work on udev has gone, but I'll look into that as well.
Truth be told I keep forgetting about this bug, since I hardly use the shortcuts anyway. It's not a showstopper :) Anyway, I've been having some trouble getting an ATI Radeon HD 4350 working with proprietary drivers, and when searching through Xorg.0.log I found this: [ 162.575] (II) config/udev: Adding input device Logitech Logitech Illuminated Keyboard (/dev/input/event3) [ 162.575] (**) Logitech Logitech Illuminated Keyboard: Applying InputClass "evdev keyboard catchall" [ 162.575] (**) Logitech Logitech Illuminated Keyboard: always reports core events [ 162.575] (**) Logitech Logitech Illuminated Keyboard: Device: "/dev/input/event3" [ 162.612] (II) Logitech Logitech Illuminated Keyboard: Found keys [ 162.612] (II) Logitech Logitech Illuminated Keyboard: Configuring as keyboard [ 162.612] (II) XINPUT: Adding extended input device "Logitech Logitech Illuminated Keyboard" (type: KEYBOARD) [ 162.612] (**) Option "xkb_rules" "evdev" [ 162.612] (**) Option "xkb_model" "pc105" [ 162.612] (**) Option "xkb_layout" "se" [ 162.613] (II) config/udev: Adding input device Logitech Logitech Illuminated Keyboard (/dev/input/event4) [ 162.613] (**) Logitech Logitech Illuminated Keyboard: Applying InputClass "evdev keyboard catchall" [ 162.613] (**) Logitech Logitech Illuminated Keyboard: always reports core events [ 162.613] (**) Logitech Logitech Illuminated Keyboard: Device: "/dev/input/event4" [ 162.652] (II) Logitech Logitech Illuminated Keyboard: Found 1 mouse buttons [ 162.652] (II) Logitech Logitech Illuminated Keyboard: Found scroll wheel(s) [ 162.652] (II) Logitech Logitech Illuminated Keyboard: Found relative axes [ 162.652] (II) Logitech Logitech Illuminated Keyboard: Found absolute axes [ 162.652] (II) evdev-grail: failed to open grail, no gesture support [ 162.652] (II) Logitech Logitech Illuminated Keyboard: Found keys [ 162.652] (II) Logitech Logitech Illuminated Keyboard: Configuring as mouse [ 162.652] (II) Logitech Logitech Illuminated Keyboard: Configuring as keyboard [ 162.652] (**) Logitech Logitech Illuminated Keyboard: YAxisMapping: buttons 4 and 5 [ 162.652] (**) Logitech Logitech Illuminated Keyboard: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [ 162.652] (II) XINPUT: Adding extended input device "Logitech Logitech Illuminated Keyboard" (type: KEYBOARD) [ 162.652] (**) Option "xkb_rules" "evdev" [ 162.652] (**) Option "xkb_model" "pc105" [ 162.652] (**) Option "xkb_layout" "se" [ 162.653] (EE) Logitech Logitech Illuminated Keyboard: failed to initialize for relative axes. [ 162.653] (II) Logitech Logitech Illuminated Keyboard: initialized for absolute axes. To me it seems kinda odd trying to configure the keyboard as a mouse... There's no such things as axes on this keyboard, no scroll buttons or anything. I doubt it's relevant for this particular bug, but it's on /dev/input/event4 anyway. Thought I might as well mention it. -- Logitech Illuminated keyboard: Fn + F5/F6 do not produce input event https://bugs.launchpad.net/bugs/337461 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
