Description of problem: Some recent change in rawhide lost the "lock screen" feature. I can't find a menu item of an applet to easily lock the screen. I may not be reporting against the right package? Please redirect as needed. Version-Release number of selected component (if applicable): gnome-screensaver-2.20.0-12.fc8.x86_64 How reproducible: 100% Steps to Reproduce: 1.login to gnome desktop session 2.look for "lock screen" 3. Actual results: gone Expected results: Ability to easily lock the screen when walking away from the computer for a while. Additional info:
Very odd. Why do you have an f8 build of gnome-screensaver installed, when this is a supposedly a rawhide bug report ?
Sorry, must have got the rpm version from the other system i was comparing with. Version installed is: gnome-screensaver-2.23.3-0.2008.05.29.3.fc10.x86_64
Hmm, I have that version installed, and I do have the lock screen menuitem and the lock screeen applet.
I tried a different user on the same system, and that had a Lock menu item and applet, so I seem to have damaged some $HOME/.* file, but what? I tried: rpm -ivh --replacepkgs gnome-session gnome-panel gnome-screensaver GConf but that didn't fix it. Is there a way to reinitialize a default gnome desktop?
is gnome-screensaver actually running in the problematic session ?
Yes, its running, and it works. It can lock the screen when it times-out. I just can't lock the screen manually from a menu or applet.
This one still has me totally stumped. With "ellson" not logged in, I used root to: mv /home/ellson /home/ellson.SAVE mkdir /home/ellson chown ellson:ellson ellson Then I rm'd everything in /tmp and /var/tmp, including all the .files, then I rebooted. On the freshly booted system I logged in as ellson. My desktop was cam up as the default, *except* that I still have no lock screen menu item!!! Logging in as other users gets a lock screen menu item. So where-o-where is this per-user state being kept ?
s/was cam/came/
I suspect your path is screwed up. The code is: if (panel_is_program_in_path ("gnome-screensaver-command") && panel_is_program_in_path ("gnome-screensaver-preferences")) use_gscreensaver = TRUE; Check that both of these commands are in the $PATH as seen by gnome-panel
Both are in my $PATH and in the $PATH of other userids. ellson@ontap:Desktop> which gnome-screensaver-command /usr/bin/gnome-screensaver-command ellson@ontap:Desktop> which gnome-screensaver-preferences /usr/bin/gnome-screensaver-preferences ellson@ontap:Desktop> whoami ellson Note that this problem occurs even for a brand-new userid IFF it is called "ellson"
The "problem" was likely caused by me playing with "pessulus". Corrected by running: System -> Preferences -> Lockdown Editor and re-enabling lock screen. My bad.