On Monday 14 November 2005 09:39 am, John Coldrick wrote:
I've been going through the same issues - I was led to the suggestion
the gnome-settings-daemon needed to be running, and suggestions to put
On Monday 14 November 2005 10:00 am, Steven T. Hatton wrote: that that
in autostart. That definitely worked, but caused endless other headaches due to some gnome settings stomping over my KDE settings(running a screensaver, affecting key-repeats). I'm convinced this is *not* the best way to deal with it. I'm still waiting for someone to suggest the "proper" way, if it exists...:P
Once upon a time there was an effort to create a common desktop configuration framework. I don't know if that is a healthy idea for either the GNOME or the KDE. Having independence to experiment without having to take compatability into account is a valuable freedom. OTOH, it would be nice if there were hooks in the KDE for GNOME settings, or in YaST? To be quite honest, I was looking at GNOME yesterday, and realized one of the things I don't like about it is that settings are applied immediately, and there is no "commit" mechanism. The current problem is an example of how the lack of such a commit mechanism causes problems.
An astute analysis -- but what can we peons do until the Messiah arrives? Does anyone have a suggestion as to how to apply the Gnome settings in a KDE environment without, as John notes, stomping all over the KDE settings? All I (and many others) want is to have the Gnome settings apply to Gnome-sensitive applications. And by the way, which package contains gnome-settings-daemon? Is it possible, perhaps, to run that daemon in a session before running the KDE controls so that the KDE controls will rule? Paul