Red Hat Bugzilla – Bug 100532
gnome-display-properties settings don't survive across logins
Last modified: 2007-11-30 17:10:31 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
Description of problem:
I'd expected the properties set with Preferences -> Screen resolution to be
retained across logins, but they aren't: every login session starts with the
default resolution, and the user has to change preferences again to get the
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.Start Preferences -> Screen Resolution
3.Change the resolution, mark it as applying to this host only, and confirm the
5.Log in again, immediately (no networking, hostname or any such changes)
Actual Results: Resolution will not be the one selected in the previous login
Expected Results: I understand it should be, but is this a bug or an
That is a bug. This should work, and does for me.
However, can you please try again with the latest control-center and
gnome-session from rawhide? We've now gone from the gnome 2.2 backport we had to
the normal code in gnome 2.4.
Its also possible that you upgraded control-center but not gnome-session, and
gnome-session is what sets the resolution on login.
Err... Are you sure you marked it as `host only', as per the instructions to
duplicate the problem? I've just verified that it indeed works if applied to
all hosts, but gconf-editor doesn't show any entries other than default within
the screen section, where I'd have expected to find host-specific configurations.
I can duplicate this too. investigating.
I get this between two computers on a NFS mounted home directory. I
figured my problem was a gnome gconfd-2 locking issue. If logging in
and out quickly duplicates this, possibly gconfd-2 hasn't shutdown,
since it usually hangs around for a minute or two after user logout.
This file locking is noticable when the home directory won't umount if
a user selects "reboot/shutdown" from the logout menu.
I'm going through bugs assigned to me and attempting to clean some of the older,
fixed ones up.
This bug hasn't changed in over a year old now. Are you still seeing the problem?
(This a batch message is being sent to all my bugs that haven't changed in a year)
Problem is fixed in FC3, maybe even in FC2.