I think I've found the culprit now. Doing some research lead me to bug report #519340.
Invoking gnome-settings-daemon on the command line using parameters --debug and --no-daemon showed up the following error message: ERROR: Caught a segmentation fault while loading plugin file: /usr/lib/gstreamer-0.10/libgstlv2.so Please either: - remove it and restart. - run with --gst-disable-segtrap and debug. Could not initialize GStreamer: Fehler beim erneuten Einlesen der Registry , child terminated by signal Please excuse the English-German mix, I use a German localized system. It seems as if the last gstreamer0.10-plugins-bad update caused this. I tried do downgrade but I just got the message: dpkg: Fehler beim Bearbeiten von gstreamer0.10-plugins-bad_0.10.13-1_amd64.deb (--install): Versuche, »/usr/lib/gstreamer-0.10/libgstrtpmanager.so« zu überschreiben, welches auch in Paket gstreamer0.10-plugins-good 0:0.10.16-2 ist The file /usr/lib/gstreamer-0.10/libgstrtpmanager.so seems to be in both g-p-bad and g-p-good now. I realized that there must be more packages affected from this issue. Pidgin also stopped working with a similar error message. I think this bug should be reassigned as my first suggestion about libglib2.0-0 seemed to be wrong... Regards, Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
