This bug was fixed in the package udev - 147~-1
---
udev (147~-1) karmic; urgency=low
FFE LP: #427356.
* Update to GIT HEAD (pre 147 release):
- worker signal mask corrected. LP: #407428.
- database format change to avoid path length issues. LP: #377121.
- multiple
Ok.
Thanks a lot!
--
Acer 6920: Some scancodes not/wrong registered
https://bugs.launchpad.net/bugs/407940
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Thanks! I added the remaining keys to udev trunk. However, hold
doesn't exist, I mapped it to stop for now. Please let me know if that
isn't appropriate.
** Changed in: udev (Ubuntu)
Status: Incomplete = Fix Committed
--
Acer 6920: Some scancodes not/wrong registered
Hold locks the panel, so that no keys can be pressed by mistake. stop is
something different (there's another key for it).
Actually it isn't necessary to map this key to anything because it works by
itself, but as it produces a scancode I think we can also map it to something.
Maybe some
That is, I think I've mixed that up with stopcd now. I don't know what
stop actually is but it doesn't sound very accurate for me.
--
Acer 6920: Some scancodes not/wrong registered
https://bugs.launchpad.net/bugs/407940
You received this bug notification because you are a member of Ubuntu
Bugs,
Alexander Hartl [2009-08-24 15:48 -]:
Hold locks the panel, so that no keys can be pressed by mistake.
Ah, thanks for pointing this out.
Actually it isn't necessary to map this key to anything because it
works by itself
I agree. It shouldn't be overloaded with something else, it would
Yes, € and $ are correct but they don't work anyway...
They can't work in X.org because they have a key code 255, that's a
known limitation of X (there's a bug report for it, but I'm offline
right now and can't find it). Nothing we can fix in udev and the
keymaps, unfortunately.
Ah, ok.
a...@alex-note:~$ sudo /lib/udev/keymap -i input/event5
** Pressing new keys but nothing happens **
OK, that means that these keys are on a different input device.
Apparently you have something called a Logitech USB receiver. Can you
please try whether you see these keys on input/event6
OK, that means that these keys are on a different input device. Apparently
you have something called a Logitech
USB receiver.
That's my Logitech wireless mouse.
Can you please try whether you see these keys on input/event6 (unlikely, but
possible) or input/event7 (more
likely)?
No, they
Hello Alex,
Alexander Hartl [2009-08-07 16:05 -]:
OK, that means that these keys are on a different input device.
Apparently you have something called a Logitech USB receiver.
That's my Logitech wireless mouse.
Ah, then the input devices I mentioned are not related to the missing
a...@alex-note:~$ killall gnome-settings-daemon gnome-power-manager
a...@alex-note:~$ xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\)
*\(.*\), .*$/keycode \2 = \3, state = \1/p'
keycode 36 = (keysym 0xff0d, Return), state = 0x0
** Pressing all new keys, €, $ and bluetooth-switch, but
** Attachment added: udev-db.txt
http://launchpadlibrarian.net/29934701/udev-db.txt
--
Acer 6920: Some scancodes not/wrong registered
https://bugs.launchpad.net/bugs/407940
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Martin, I haven't caught up with the stuff that moved in from udev-
extras yet - do you know what we do about this kind of thing?
** Changed in: udev (Ubuntu)
Importance: Undecided = Low
** Changed in: udev (Ubuntu)
Status: New = Confirmed
** Changed in: udev (Ubuntu)
Assignee:
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Please exercise the steps at
https://wiki.ubuntu.com/Hotkeys/Troubleshooting to determine DMI
information and on which device these hotkeys occur, and attach the
collected information. Thanks!
** Changed in:
14 matches
Mail list logo
