Description of problem: Trying to lock the gnome3 desktop with "ctrl+alt+l", but nothing happens: the screen remains unlocked. Version-Release number of selected component (if applicable): gnome-shell-3.6.0-1.fc18.x86_64 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
same with gnome-shell-3.6.1-1.fc18.x86_64
is gnome-settings-daemon running ? do other keyboard shortcuts such as fn-f4 work ? is screen lock turned off ?
(In reply to comment #2) > is gnome-settings-daemon running ? yes > do other keyboard shortcuts such as fn-f4 work ? yes, for example alt+f2 > is screen lock turned off ? no
After starting gnome-screensaver manually, ctrl+alt+l is working :-) But if I make an entry for gnome-screensaver by gnome-sesion-properties, gnome-screensaver is not running after logging out and logging in again!
Workaround for me: Adding the line [ "$DISPLAY" != "" ] && /bin/gnome-screensaver& to ~/.bash_profile
(In reply to comment #4) > After starting gnome-screensaver manually, ctrl+alt+l is working :-) That is bad - since GNOME 3.6, gnome-screensaver is supposed to be only used in fallback mode, in the normal GNOME session locking is provided by the shell. Are there any errors in ~/.cache/gdm/session.log? > But if I make an entry for gnome-screensaver by gnome-sesion-properties, > gnome-screensaver is not running after logging out and logging in again! Yes, gnome-screensaver uses an autostart condition to only start in fallback.
(In reply to comment #3) > (In reply to comment #2) > > is gnome-settings-daemon running ? > > yes > > > do other keyboard shortcuts such as fn-f4 work ? > > yes, for example alt+f2 > > > is screen lock turned off ? > Alt-f2 is different - it is handled by the shell. I was asking to see if gnome-settings-daemons media-keys plugin was loaded + working.
Another question: are you using gdm or another display manager ?
(In reply to comment #6) > (In reply to comment #4) > > After starting gnome-screensaver manually, ctrl+alt+l is working :-) > > That is bad - since GNOME 3.6, gnome-screensaver is supposed to be only used > in fallback mode, in the normal GNOME session locking is provided by the > shell. > > Are there any errors in ~/.cache/gdm/session.log? File does not exist :-(
(In reply to comment #8) > Another question: are you using gdm or another display manager ? GDM
(In reply to comment #7) > (In reply to comment #3) > > (In reply to comment #2) > > > is gnome-settings-daemon running ? > > > > yes > > > > > do other keyboard shortcuts such as fn-f4 work ? > > > > yes, for example alt+f2 > > > > > is screen lock turned off ? > > > > Alt-f2 is different - it is handled by the shell. 1. there is no fn key on my desktop pc 2. I've only the f1-f12 key. Nothing happens if pressing f1,f2,f3 or f4. > I was asking to see if gnome-settings-daemons media-keys plugin was loaded + > working. Question: how to check whether gnome-settings-daemons media-keys plugin was loaded and working?
(In reply to comment #9) > > Are there any errors in ~/.cache/gdm/session.log? > > File does not exist :-( Hmm, seems there is more wrong on your system than just c-a-l...
(In reply to comment #12) > (In reply to comment #9) > > > > Are there any errors in ~/.cache/gdm/session.log? > > > > File does not exist :-( > > Hmm, seems there is more wrong on your system than just c-a-l... Problem solved! After some investigation, I found out that the actual DM was lxdm, and not gdm. After switching to gdm by systemctl disable lxdm.service; systemctl enable gdm.service, rebooting and logging in again, and removing the line "[ "$DISPLAY" != "" ] && /bin/gnome-screensaver&" from my ~/.bash_profile, I nevertheless could lock the screen with c-a-l! Please excuse for trouble, I thought that gdm was running and not lxdm. Kind regards Joachim Backes
https://bugzilla.gnome.org/show_bug.cgi?id=683060 has a patch to make screen locking work in this situation (gnome-shell + !gdm). We should get that into F18
Looks like this is fixed, at least as of gnome-shell-3.6.2-6.fc18.x86_64.
Oh, sorry. Someone will need to re-test with lxdm; I misread that part and was testing with gdm.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.