Bug 702471 - Suspending with keyboard key does not lock my session whereas suspending from menu does
Summary: Suspending with keyboard key does not lock my session whereas suspending from...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-desktop
Version: 19
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-05 18:26 UTC by Jirka Daněk
Modified: 2015-02-17 13:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 13:44:34 UTC
Type: ---


Attachments (Terms of Use)

Description Jirka Daněk 2011-05-05 18:26:20 UTC
Description of problem:
I have a BENQ USB keyboard with some multimedia keys in top row. One of these keys is marked with a Waning crescent moon and pressing it suspends my computer.

Similar effect can be archieved in the menu in the top right corner.

The results differ in a subtle ways.

Pressing the key makes my screen to go dark in an instance, then the computer shuts down. After switching it on with power button on PC case, the session appears as it previously was, I am still logged in and can immediately resume working.

Doing it in the menu, the screen fades into black, then suddenly lights up again, revealing my desktop once more, then the computer shuts down. Swithcing it back on, the Session is locked screen appears and I have to log in before I can work again.

When I say the computer shuts down, in both cases I mean the fans stop spinning and the LEDs on the case switch off. I am sure that it is really suspended to RAM. 

I report this behavior 1) because some people may be unplesantly surprised their session in not locked when suspended using keyboard 2) this "flickering" (fading out and immediately coming back in) of screen is a bit annoying.

My hw profile: http://www.smolts.org/client/show/pub_56adb9dd-c210-4a9d-870e-6ebef7f8d37a

Comment 1 Fedora End Of Life 2013-04-03 17:26:47 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 2 Fedora End Of Life 2015-01-09 16:39:27 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-02-17 13:44:34 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.