Oh no! Something has gone wrong.

Michael Schwendt mschwendt at gmail.com
Wed Aug 31 18:36:30 UTC 2011

On Mon, 29 Aug 2011 20:11:04 -0700, AW (Adam) wrote:

> GNOME devs refer to the screen as the 'fail whale'. It shows up if any
> key Shell component crashes in a loop. The key message to look for is
> "respawning too quickly", thus:
> (gnome-settings-daemon:1639): GnomeDesktop-WARNING **: could not get output property for DVI-0, rc: 15
> (gnome-settings-daemon:1639): GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed
> (gnome-settings-daemon:1639): color-plugin-WARNING **: failed to enumerate directory /home/misc16/.color/icc: No such file or directory
> g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
> gnome-session[1328]: WARNING: App 'gnome-settings-daemon.desktop' respawning too quickly
> so that's your problem there, I think. alt-f4 should get rid of the fail
> whale, and abrt-gui should be able to report the g-s-d crash.

Hey! This has changed the world here. With Alt-F4 I continued, opened a
terminal and ran /usr/libexec/gnome-settings-daemon &> g-s-d.LOG
Initially, it printed the same warnings as in xsession-errors and then
terminated without crashing. Therefore ABRT didn't intercept anything.
Afterwards I've run into other issues (one being a reproducible crash
in gnome-shell I've reported) and small display corruption, which made
me reboot, and now I cannot reproduce the g-s-d problem at login time.
Not with my "test1" account either. I've restored a backup of my "misc16"
account files, and still cannot reproduce it anymore.

> You're not running glibc 2.14.90-6 , are you? It's known to be broken. I
> ran it for a bit today and found g-s-d would crash.

No, -4 and never had -6 installed.

Fedora release 16 (Verne) - Linux 3.1.0-0.rc3.git0.0.fc16.x86_64
loadavg: 0.09 0.06 0.05

More information about the test mailing list