After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 347855 - Pressing brightness keys on laptops wakes up the screensaver
Pressing brightness keys on laptops wakes up the screensaver
Status: RESOLVED FIXED
Product: gnome-screensaver
Classification: Deprecated
Component: general
2.14.x
Other All
: Normal normal
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2006-07-18 00:08 UTC by Oliver Grawert
Modified: 2006-07-27 23:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14

Attachments
ignore_brightness_keys (636 bytes, patch)
2006-07-18 00:09 UTC, Oliver Grawert 		none Details | Review

Description Oliver Grawert 2006-07-18 00:08:42 UTC 
Please describe the problem:
if you press the brightness key for a laptop display this wakes up the screensaver, in ubuntu we use a patch to avoid that.

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Oliver Grawert 2006-07-18 00:09:38 UTC 
Created attachment 69079 [details] [review]
ignore_brightness_keys

ubuntu patch to solve the isssue
Comment 2 William Jon McCann 2006-07-18 17:52:48 UTC 
Are those hardware keycodes the same on all keyboards?  Where is this defined?
Comment 3 Matthew Garrett 2006-07-19 13:09:40 UTC 
They're defined in /usr/include/linux/input.h. I'm not aware that other platforms have standardised in any way.
Comment 4 Matthew Garrett 2006-07-19 13:11:55 UTC 
Sorry, I should probably have clarified that. They're the keycodes from /usr/include/linux/input.h after they've gone through the keycode munging that the console layer and X perform. The mapping is non-trivial, but those Linux keycodes will always generate those X keycodes.
Comment 5 William Jon McCann 2006-07-27 23:24:36 UTC 
Fixed in the development version. The fix will be available in the next major release. Thank you for your bug report.