Thanks for debugging this. I'm also adding xorg to this bugreport since
it appears something in X is intercepting the keyevent and blanking the
screen. Could you do the following:
Paste in output of: lspci -nn | grep VGA
Attach /var/log/Xorg.0.log
To triagers/developers:
1) xev is showing
** Description changed:
Binary package hint: gnome-power-manager
Laptop: Dell Latitude D630.
When pressing the suspend key (Fn-F1), only the display gets turned off,
instead of suspending the laptop.
In the settings, I have the following:
When the suspend button is pressed: Su
Output of
$ gnome-power-manager --verbose | tee gpm.debug.log.txt
attached.
You can see keycode 213 (XF86Suspend) being "grabbed" during
initialisation (first few rows).
I pressed the button at time 18:24:00, nothing was generated in the log
as you can see.
Compared to that, I pressed the power
Thanks for the info, it does look like ubuntu recognizes the suspend
key being pressed.
Could you try:
killall gnome-power-manager
gnome-power-manager --verbose
(I could get the --verbose to work that way)
There should be a lot of messages in the terminal at first and more
once you hit the suspend
The suspend key is recognized correctly. Here the xev output:
KeyPress event, serial 34, synthetic NO, window 0x141,
root 0xff, subw 0x0, time 21205448, (100,89), root:(1302,142),
state 0x0, keycode 213 (keysym 0x1008ffa7, XF86Suspend), same_screen YES,
XLookupString gives 0 bytes:
Thanks for testing it and confirming that your bug isn't a duplicate. To debug
hotkeys, see and follow the inatructions at:
https://wiki.ubuntu.com/Hotkeys/Troubleshooting
to make sure that ubuntu recognizes (Fn-F1) as suspend and not "blank screen"
Also, see
https://wiki.ubuntu.com/DebuggingGNOM
Further: Now when I suspend and resume, the screen is not locked anymore
(i.e. I don't have to type in a password). This was definitely not the
case directly after installation. Screen locking e.g. by manually
activating screen saver works normally. I have a feeling these issues
could be related. O
Hi Scott,
This is not a duplicate of Bug 407491. I tried the fixed version from a
PPA mentioned there and this problem still persists. Moreover, I am
using i386, and as I understood from the other bug, it affects only
amd64.
I updated the bug description, because I found out that Fn-F1 now turns
