GTK2 font settings

Stephan Kulow coolo at kde.org
Wed Apr 9 12:51:04 BST 2003


On Wednesday 09 April 2003 12:38, Lubos Lunak wrote:
> On Friday 28 of March 2003 19:25, Lubos Lunak wrote:
> > On Friday 28 of March 2003 18:58, David Faure wrote:
> > > On Friday 28 March 2003 18:28, Havoc Pennington wrote:
> > > > On Fri, Mar 28, 2003 at 11:02:39AM +0100, Craig Drummond wrote:
> > > > > Why does the gnome-settings-daemon insist on owning the desktop?
> > > >
> > > > gnome-settings-daemon is similar to krdb - basically what it does is
> > > > propagate gconf settings out to lots of non-gconf stuff. So it sets
> > > > some X resources, grabs some X keys, sets XKB properties, sets the
> > > > background, all this type of thing.
> > > >
> > > > I don't think it owns the desktop
> > >
> > > Check the XKillClient call at the end of
> > > http://bugs.kde.org/show_bug.cgi?id=31619
> >
> >  Maybe kdesktop should use a separate XServer connection for setting these
> > pixmaps, use XSetCloseDownMode() and close this separete connection. That
> > would prevent others from killing it. It's maybe even part of the "spec"
> > for setting the background pixmaps for englightenment that the old pixmap
> > should be killed :-/.
> 
>  Just for the recond: After having completed a solution that managed to 
> survive that XKillClient(), I found out that this was kdesktop bug after all 
> - whoever copied it from Esetroot apparently didn't realize that kdesktop 
> shouldn't set ESETROOT_PMAP_ID at all. So it doesn't now.
> 
I think, this was there so that apps like xchat can find the backgroup pixmap 
to get a transparent background.

Greetings, Stephan





More information about the kde-core-devel mailing list