This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
yes, the same problem still exists in Maverick and Natty alpha
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/178860
Title:
hotkey-setup support for MSI PR200
--
ubuntu-bugs mailing list
Could we confirm that this issue still exists in current releases. The
latest testing seems pretty old, indeed on releases now off support.
Thanks in advance!
** Changed in: linux (Ubuntu)
Status: Incomplete = In Progress
** Changed in: linux (Ubuntu)
Status: In Progress =
This bug report was marked as Triaged a while ago but has not had any
updated comments for quite some time. Please let us know if this issue
remains in the current Ubuntu release,
http://www.ubuntu.com/getubuntu/download . If the issue remains, click
on the current status under the Status column
** Branch linked: lp:debian/sid/acpi-support
** Branch linked: lp:ubuntu/acpi-support
--
hotkey-setup support for MSI PR200
https://bugs.launchpad.net/bugs/178860
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Status: New = Triaged
--
hotkey-setup support for MSI PR200
https://bugs.launchpad.net/bugs/178860
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: udev (Ubuntu)
Status: Invalid = New
--
hotkey-setup support for MSI PR200
https://bugs.launchpad.net/bugs/178860
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: lsinput.log
http://launchpadlibrarian.net/30857479/lsinput.log
--
hotkey-setup support for MSI PR200
https://bugs.launchpad.net/bugs/178860
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: dmesg.log
http://launchpadlibrarian.net/30857476/dmesg.log
--
hotkey-setup support for MSI PR200
https://bugs.launchpad.net/bugs/178860
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
well sorry i don't have time to always have the latest-and-greatest
ubuntu installed :ep
anyway.
restating the issue:
all special function keys work as expected, but they generate unknown keycode
noise in dmesg. when attempting to fix the noise by including keys in a hotkey
map, gnome
Ah, do the brightness keys stop working if you purge the acpi-support
package? That still has a script to handle the acpi event. But I'd
rather have it in udev properly, since acpi-support is destined to go
away, and other models already generate proper brightness key input
events (which causes
** Branch linked: lp:~ubuntu-core-dev/acpi-support/trunk
--
hotkey-setup support for MSI PR200
https://bugs.launchpad.net/bugs/178860
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The log output is:
[ 1346.397356] atkbd.c: Unknown key released (translated set 2, code 0xf7 on
isa0060/serio0).
[ 1346.397359] atkbd.c: Use 'setkeycodes e077 keycode' to make it known.
[ 1346.552737] atkbd.c: Unknown key pressed (translated set 2, code 0xf8 on
isa0060/serio0).
[ 1346.552741]
087 is down, 077 is up.
the file /lib/udev/keymaps has correct mappings, it just needs to be enabled in
95-keymap.rules (my DMI_VENDOR is Micro-Star, not MICRO-STAR)
now everything works, except when the brightness is minimum and i press
Brightness down, the brightness starts blinking rapidly.
This bug was fixed in the package acpi-support - 0.126
---
acpi-support (0.126) karmic; urgency=low
* Drop /etc/acpi/start.d/10-save-dmidecode.sh, which is irrelevant given
the existence of /sys/class/dmi/id/.
* Drop events/panasonic-brightness-{down,up},
so. without acpi-support, i can still see the keypresses through
acpi_listen, everything still works as before and gnome can still be
convinced to start blinking (by pressing brightness down repeatedly) -
but that is now much harder to trigger (and from the looks of it, it's a
different bug)
i'll
reopen a udev task for the DMI_VENDOR case issue.
** Also affects: udev (Ubuntu)
Importance: Undecided
Status: New
** Changed in: udev (Ubuntu)
Importance: Undecided = Medium
** Changed in: udev (Ubuntu)
Status: New = Triaged
** Changed in: udev (Ubuntu)
Assignee:
ha! got something
if the udev keymap is disabled, the keys work as expected without problems.
they show up in acpi_listen and dmesg output as shown above.
and when i kill gnome-power-manager, they also show in xev output (using the
command from Hotkeys/Troubleshooting) - twice:
keycode 233 =
Steve,
wow, I was about to ask you whether to drop video_brightness* scripts,
and there you are and have done it already. Many thanks!
udev rule fixed upstream in
http://git.kernel.org/?p=linux/hotplug/udev.git;a=commit;h=66bf63c
** Changed in: udev (Ubuntu)
Status: Triaged = Fix
if the udev keymap is disabled, the keys work as expected without
problems. they show up in acpi_listen and dmesg output as shown above.
That's all with acpi-support purged? It's probably that your brightness
keys are hardwired and directly control the brightness in hardware. Then
the key events
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
hotkey-setup support for MSI PR200
https://bugs.launchpad.net/bugs/178860
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
no, the keys aren't hardwired, there are still situations where they
don't work. that's in grub menu, i think, and also there were bugs in
some older ubuntu releases that they didn't work until g-p-m started
so, is it normal that the key sends the event twice?
and if it is a kernel bug, where to
matejcik [2009-08-26 17:43 -]:
no, the keys aren't hardwired, there are still situations where they
don't work.
Hm, interesting. So just to confirm, without the udev rule (after a
clean boot, so that the keymap is really reset), and acpid stopped you
still get the correct keys in xev?
It can't be an issue with a hardwired key, since we're seeing X keypress
events. Something has to be passing those up to X from the kernel.
With acpid stopped and the udev rule disabled (as confirmed in the
output of /lib/udev/keymap input/event5 | grep 'f[78]'), what do you see
as output when
with stock udev (without the rule to load micro-star keymap) and acpid
stopped, i still have two key events from xev, as said above
in that situation:
matej...@limetka:~$ sudo /lib/udev/keymap input/event5 | grep 'f[78]'
0x041 f7
0x042 f8
0x0f7 reserved
0x0f8 reserved
0x1f7 reserved
0x1f8
Interesting, that means these key events are coming across the Video Bus
input device.
[...]
/dev/input/event6
bustype : BUS_HOST
vendor : 0x0
product : 0x6
version : 0
name: Video Bus
phys: /video/input0
bits ev : EV_SYN EV_KEY
[...]
Martin, I think this means
Right, reverted upstream in commit bc19bff.
** Changed in: udev (Ubuntu)
Status: Fix Committed = Invalid
--
hotkey-setup support for MSI PR200
https://bugs.launchpad.net/bugs/178860
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Wed, Aug 26, 2009 at 22:25, Steve Langasek
steve.langa...@canonical.comwrote:
Martin, I think this means the udev change should probably be reverted,
since we *don't* want to map these keys a second time.
please bear in mind that there are other keys in the mapping: wifi toggle,
bluetooth
Just to be sure we know what we're looking at, could you run 'sudo
/lib/udev/findkeyboards' and 'sudo /lib/udev/keymap input/event6'?
BTW, maybe this goes without saying, but the input device numbers are
not static; they can be different across every reboot. So perhaps we
should re-check the
matej...@limetka:~$ sudo /lib/udev/findkeyboards
AT keyboard: input/event5
matej...@limetka:~$ sudo /lib/udev/keymap input/event6
### evdev 1.0.0., driver 'Video Bus'
matej...@limetka:~$ sudo /lib/udev/keymap input/event5
### evdev 1.0.0., driver 'AT Translated Set 2 keyboard'
which seems to be
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Please exercise the steps at
https://wiki.ubuntu.com/Hotkeys/Troubleshooting to determine at which
level your hotkey problems occur, and attach the collected information.
Thanks!
** Package changed: udev-extras (Ubuntu) = udev (Ubuntu)
** Changed in: udev (Ubuntu)
Assignee: (unassigned) =
The only documentation I can point you to on this is
https://wiki.ubuntu.com/Hotkeys/Troubleshooting, which I'm not sure
tells you anything you don't already know; and I don't have access to
one of these laptops to reproduce the behavior you're describing. What
is the noise generated in dmesg for
** Changed in: hotkey-setup (Ubuntu)
Assignee: Andreas Moog (andreas-moog) = (unassigned)
--
hotkey-setup support for MSI PR200
https://bugs.launchpad.net/bugs/178860
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
hello,
actually, i can't really tell - i have fixed this on my machine, perhaps not in
the best possible way, but the kernel log is no longer spammed with the
messages, which was the original problem.
and it appears that official hotkey-setup is still unchanged, so that would be
a no.
i am
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
** Changed in:
okay ... i take back the patches, because the brightness key mappings make
gnome-power-manager go haywire. crappy broken thing.
let me learn a bit more about hotkeys first
--
hotkey-setup support for MSI PR200
https://bugs.launchpad.net/bugs/178860
You received this bug notification because you
->
[Bug 178860] Re: hotkey-setup support for MSI PR200
ubuntu-bugs
-- Thread --
-- Date --
<!--
google_ad_client = "pub-7266757337600734";
google_alternate_ad_url = "http:/
38 matches
Mail list logo
