Red Hat Bugzilla – Bug 155280
xscreensaver not started in console session when vncserver running
Last modified: 2008-02-07 22:10:42 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Firefox/1.0.2 Fedora/1.0.2-1.3.1
Description of problem:
when vncserver is running the vnc session gets xscreensaver started correctly, however the same user logging into the console does not. My guess is that gnome-session is perfomring a simple minded check to see if xscreensaver is
running an simply not starting it if it sees a prcess owned by the same user. A work around is to explicitly add xscreensaver to you session with the session editor.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. boot system with vncsever enabled
2. login at console
Actual Results: no xscreensaver daemon running
Expected Results: xscreensaver daemon should be started
Your guess sounds plausible. It would be gnome-settings-daemon not
gnome-session, though. If that is the case, the fix will probably be to just
not do the check because xscreensaver already does it when it starts.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Fedora Core 3 is not maintained anymore.
Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.