who's setting a wild-card'ed background color resource.

George Hartzell hartzell at kestrel.alerce.com
Tue Oct 21 15:48:55 PDT 2003


George Hartzell writes:
 > 
 > I just got done updating ports on my 4.8 (4.8-RELEASE-p7) laptop,
 > using the current ports tree (as of a couple of days ago).
 > 
 > [...]
 > 
 > The problem is: my custom background colors have disappeared.
 > 
 > [...]
 > 
 > I think what's killing me is this resource:
 > 
 >   *background:    #dcdad5
 > 
 > [...]
 > 
 > I can't figure out where it's getting set.  Is is part of one of the
 > myriad themes that the various gnome things use?
 > 
 > Pointers/suggestions would be appreciated.

I managed to solve the puzzle of "who is setting this", by following
the trail of breadcrumbs that I discovered by doing this:

    find /usr/X11R6 -type f -print | xargs grep -i beNiceToColormap

(beNiceToColorMap was a resource in the same suspicious block as the
background setting).

It seems that it's some portion of the
gnome-control-center/theme-manager/gnome-settings-daemon that's
"helping" me out with this.

There are a bunch of relevant files in
/usr/X11R6/share/gnome/control-center-2.0/xrdb, which are being used
as templates.

So, now the question is, how to control this behaviour.  I've
currently just commented out the entries that I don't like.  It sounds
like KDE has a check-box somewhere that controls whether it applies
colors etc... to non-kde apps.  Is there something like that in gnome
that I've missed?

g.



More information about the freebsd-gnome mailing list