Bug 747989

Summary: Samsung N210 netbook: Suspend key doesn't work
Product: [Fedora] Fedora Reporter: Horst H. von Brand <vonbrand>
Component: gnome-power-managerAssignee: Richard Hughes <hughsient>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: cbm, hughsient, rhughes
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-15 13:47:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Horst H. von Brand 2011-10-21 16:03:30 UTC
Description of problem:
The suspend key (Fn+Esc) has no effect anymore

Version-Release number of selected component (if applicable):
gnome-power-manager-3.2.1-1.fc16.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Press Fn+Esc when in the Gnome shell
2.
3.
  
Actual results:
Nothing

Expected results:
Machine suspends

Additional info:
xev says:
KeymapNotify event, serial 29, synthetic NO, window 0x0,
    keys:  95  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0

It seems to alternate btween 95 and 1 in the first position. Other (not all) Fn+* combinations do work (e.g., Fn+F9 disables WiFi, Fn+F10 disables touchpad.

Comment 1 Colin Macdonald 2011-11-04 08:27:13 UTC
Not Samsung specific: I see this (same symptoms anyway) on a Thinkpad X201.  Also on F16.  Works fine on F15 (at least last time I used it a few weeks ago).

xev has similar output, although interestingly only the *first time* one presses fn-f4.  After that, there is a timeout of about 30 seconds or so when fn-f4 does not register anything in xev.

FocusOut event, serial 29, synthetic NO, window 0x3400001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 29, synthetic NO, window 0x3400001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 29, synthetic NO, window 0x0,
    keys:  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

After the roughly 30 seconds, fn-f4 will cause output in xev again.

Comment 2 Horst H. von Brand 2011-11-07 19:24:10 UTC
BTW, this used to work, then didn't work and worked again (in rawhide); then a lot of weird errors made me install 16 beta from scratch, and now it doesn't work. Last tried on Saturday, November 5.

Comment 3 Richard Hughes 2011-11-15 13:47:03 UTC

*** This bug has been marked as a duplicate of bug 749949 ***