GNOME Bugzilla – Bug 673585
Gnome Display Manager Crashes When HDMI Output is Disconnected
Last modified: 2012-04-05 18:41:00 UTC
I sometimes like to plug my laptop into the tv to watch movies etc and since upgrading to 3.4 I can no longer do this properly. When I unplug the hdmi cable the whole computer freezes and I have to do a hard shutdown. These are the .xsession-errors I am getting. Window manager warning: CurrentTime used to choose focus window; focus window may not be correct. Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen! (epiphany:15260): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed (epiphany:15260): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed Window manager warning: CurrentTime used to choose focus window; focus window may not be correct. Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen! (evolution-alarm-notify:2684): evolution-alarm-notify-WARNING **: alarm.c:254: Requested removal of nonexistent alarm! On reboot I get this error message. I am using gnome-shell with no custom config. I have tried with and without extensions. The only extension I use is alternative status menu from extensions.gnome.org. I have tried the offical gnome 3.4 live cd and have NO problems. I did NOT have this problem in 3.2. I have reinstalled arch so I have pacman logs to give but after reinstalling I still have the issue. The crash happens when logged in and alos at the login screen when the resolution is only 640x480 on both screens. When tv is plugged in, the resolutions on my laptop are 1600x900 and the tv is 1920x1080. I am NOT using fallback mode. Laptop is Gateway NV79C and I have Intel Integrated Graphics. I am running 64-bit Arch Linux. I reported this on the Arch Bug Tracker but I find it hard to believe that this bug would be distro-specific. See here: https://bugs.archlinux.org/task/29285
This isn't likely to be a GDM bug. It sounds like an X driver issue of some sort. Filing with your distribution was appropriate. Alternatively, you can file an upstream report at bugs.freedesktop.org.