Comment 24 for bug 132833

Hi there,

Most of the solutions here just obscure the bug, Sebastien Bacher is right in this.
The reason that the "camelcolor" appears is the wrong usage of gdmflexiserver.

The gdmflexiserver -a (authenticate) should be a more direct approach to the real reason that we all seem to get the "camelcolor" screen.
For me it does not make a difference, here is my ~/.xserver-error log (set -x) and see what (not) happens:

Pay particular attention to:
------
Refusing to initialize GTK+.
+ BACKCOLOR=
------
which is the direct reason for the camelcolor to appear.

=================================================
+ echo /usr/bin/xsetroot
+ XSETROOT=/usr/bin/xsetroot
+ [ x/usr/bin/xsetroot != x ]
+ CHECKBACKCOLOR=OK
+ [ xTHEMED = xTHEMED ]
+ gdmflexiserver -a --command=GET_CONFIG greeter/GraphicalThemedColor :0

(process:5969): Gtk-WARNING **: This process is currently running setuid or setgid.
This is not a supported use of GTK+. You must create a helper
program instead. For further details, see:

    http://www.gtk.org/setuid.html

Refusing to initialize GTK+.
+ BACKCOLOR=
+ echo
+ sed s/^\([^ ]*\) .*$/\1/
+ CHECKBACKCOLOR=
+ [ x = xOK ]
+ BACKCOLOR=
+ [ x != xOK ]
+ gdmflexiserver -a --command=GET_CONFIG greeter/BackgroundType :0

(process:5973): Gtk-WARNING **: This process is currently running setuid or setgid.
This is not a supported use of GTK+. You must create a helper
program instead. For further details, see:

    http://www.gtk.org/setuid.html

Refusing to initialize GTK+.
+ BACKTYPE=
+ [ x = xOK 1 ]
+ [ x = xOK 2 ]
+ [ x = x ]
+ BACKCOLOR=#dab082 #<----YES, THE F%$%ing CAMELCOLOR IS HERE
+ /usr/bin/xsetroot -cursor_name left_ptr -solid #dab082
+ exit 0

================================================

grtz, tom