-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 21 October 2002 20:31, Chris Cheney wrote:
Hmm...anyway, this is messed up the way it works now. I didn't notice as it worked for me up until now, but basically the way that kdm now reads the background settings is definetly out of order, so to speak. So it needs fixing before the release candidate comes out, because that really sucks if you're changing settings that seem to be ok in the control center but never work for real. Ralf > Ralf, > > I am not sure, kde just does it that way, if you look at what I am doing > with the build it isn't anything special. I did modify > kdm/kfrontend/genkdmconf.c slightly so that it would generate a default > debian config. However as far as I can tell I did not modify anything > wrt a backgroundrc, it just started getting generated a few months ago. > > Chris > > On Mon, Oct 21, 2002 at 08:14:19PM +0200, Ralf Nolden wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Hi, > > > > I just noticed that the way kdm handles the background greeter settings > > in debian has changed to a very non-standard way of writing it's own > > backgroundrc into /etc/kde3/kdm/, while the way that also the control > > center handles things is to do this inside /etc/kde3/kdm/kdmrc. > > > > Is there a reason or intention why this got broke ? Otherwise, I'll have > > a look into that over the coming days (guess thursday when most of my > > other work is done and I only need to prepare my talks for LWE next > > week). > > > > Ralf - -- We're not a company, we just produce better code at less costs. - -------------------------------------------------------------------- Ralf Nolden [EMAIL PROTECTED] The K Desktop Environment The KDevelop Project http://www.kde.org http://www.kdevelop.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9tEoLu0nKi+w1Ky8RAicQAJoD+Tma/ilpGMOqHteJUbpyKV3bdwCfTiLp H4UTCCBW4Nu2+d3naNWG4fc= =uw2D -----END PGP SIGNATURE-----
