After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 329253 - changing background colour doesn't take effect
changing background colour doesn't take effect
Status: RESOLVED FIXED
Product: gdm
Classification: Core
Component: general
2.13.x
Other All
: Normal minor
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2006-01-30 19:51 UTC by Héctor Rivas Gándara
Modified: 2006-01-30 22:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Héctor Rivas Gándara 2006-01-30 19:51:39 UTC
Please describe the problem:
in gdmsetup, I changed the background colour, but it doens't seem to have any
effect, whenver I log-in, I still see the old/default colour...


Steps to reproduce:
1. gdmsetup, I changed the background colour
2. reboot gdm


Actual results:
The /etc/X11/gdm/gdm.conf-custom changes the color, but when the session starts,
the old color (defined in /etc/X11/gdm/gdm.conf) is set.

Expected results:
The color defined in /etc/X11/gdm/gdm.conf-custom must overwrite
/etc/X11/gdm/gdm.conf

Does this happen every time?
Yes

Other information:

The problem is in the /etc/X11/gdm/PreSession/Default script, starting at line 28.

This script tries to set the background using the xset command. To get the
background color, it parses the /etc/gdm/gdm.conf, not the new
/etc/gdm/gdm.conf-custom.

This bug is in the gdm original source, in config/Presession.in file.
Comment 1 Brian Cameron 2006-01-30 22:53:20 UTC
Ah yes, thanks for catching this issue.  The PreSession script should be using the "gdmflexiserver --command="GET_CONFIG <key>" command to get the config data since the daemon knows the right value for the keys.  This is better than hacking the script to directly try to read the config file directly.  The whole point in redesigning the GDM config is so that client programs never have to know how config is implemented, and should just call the daemon with "GET_CONFIG" to find out something.

I've corrected this in CVS head so it should work in the next release.