brjoon1021 wrote:Thanks guys. Still problem, though.
gnome setting helper is checked for startup.
Synaptic package changes only had gnome-core, nothing about helper or anything else like it. dbus had no entries in the synaptic history.
* I turned of the Gnome-settings daemon helper on a lark. No error, at least, now. I don't see any detrimental effect to having it off. I still think that the themes look different than when I first installed LMDE though. Can someone confirm that by turning the daemon off, rebooting and taking a look on a known good system ? Unless someone comes up with a fix, I am going to leave this daemon off because it doesn't seem to be needed for anything. I can change themes, settings just fine without it.
This package contains the daemon which is responsible for setting the
various parameters of a GNOME session and the applications that run
under it. It handles the following kinds of settings:
* Keyboard: layout, accessibility options, shortcuts, media keys
* Clipboard management
* Theming: background, icons, GTK+ applications
* Cleanup of unused files
* Mouse: cursors, speed, accessibility options
* Startup of other daemons: screensaver, sound daemon
* Typing break
It also sets various application settings through X resources and
** (gnome-settings-daemon:3848): WARNING **: Invalid value for /desktop/gnome/font_rendering/rgba_order: 'rgba'
** (gnome-settings-daemon:3848): WARNING **: Grab failed for some keys, another application may already have access the them.
LMDE will never be stable, or of the stability of a stable Debian version. Since it is based on testing, many new files just dumped into the repos after Debian Squeeze (formerly Debian Testing until 2 days ago) became stable. One of those new files in testing may be the factor causing the difference on your machine.RavanH wrote:Weird stuff like this keeps happening and I have the impression LMDE is not quite ready to be called stable
amina wrote:As terminal was complaining about "Invalid value for /desktop/gnome/font_rendering/rgba_order: 'rgba'" I set the corresponding value in gconf-editor to just 'rgb'.
The terminal message is gone for sure, and so far the error has not come up again (though I do not see how the two things could be related).
The order of subpixel elements on an LCD screen;
only used when antialiasing is set to "rgba". Possible values are:
"rgb" for red on left (most common),
"bgr" for blue on left,
"vrgb" for red on top,
"vbgr" for red on bottom.
amina wrote:Maybe in the end we find that the actual solution is what the error message always suggested
Users browsing this forum: No registered users and 2 guests