gnome-settings-daemon crashed with signal 5 in _XReply() (XRRSetCrtcConfig)

[Steffen Koch]

gnome-settings-daemon crashed with signal 5 in _XReply()

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-settings-daemon 3.2.2-0ubuntu5
ProcVersionSignature: Ubuntu 3.2.0-6.12-generic 3.2.0-rc6
Uname: Linux 3.2.0-6-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Dec 20 21:05:13 2011
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64+mac (20111206)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XRRSetCrtcConfig () from /usr/lib/x86_64-linux-gnu/libXrandr.so.2
 gnome_rr_crtc_set_config_with_time () from /usr/lib/libgnome-desktop-3.so.2
 ?? () from /usr/lib/libgnome-desktop-3.so.2
Title: gnome-settings-daemon crashed with signal 5 in _XReply()
UpgradeStatus: Upgraded to precise on 2011-12-12 (7 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 XRRSetCrtcConfig (dpy=0x12102d0, resources=0x1617fd0, crtc=62, timestamp=423990, x=0, y=0, mode=274, rotation=1, outputs=0x1610460, noutputs=1) at ../../src/XrrCrtc.c:147
 gnome_rr_crtc_set_config_with_time (crtc=0x15efac0, timestamp=423990, x=0, y=0, mode=0x1616860, rotation=GNOME_RR_ROTATION_0, outputs=0x15fbb00, n_outputs=1, error=0x7fff8ea9d948) at gnome-rr.c:2225
 configure_crtc (data=0x7fff8ea9d8d0, value=<optimized out>, key=<optimized out>) at gnome-rr-config.c:1617
 configure_crtc (key=<optimized out>, value=<optimized out>, data=0x7fff8ea9d8d0) at gnome-rr-config.c:1606
 g_hash_table_foreach (hash_table=0x15b86a0, func=0x7f6f21d73850 <configure_crtc>, user_data=0x7fff8ea9d8d0) at /build/buildd/glib2.0-2.31.4.tested/./glib/ghash.c:1459

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Martin Albisetti (beuno)]

This is what the desktop looks like, it happens after the screem locks.

[Brian Murray (brian-murray)]

This happend to me after I pressed a key on my bezel on my x201 tablet. I pretty sure it is this key from my keymaps file:

0x67 cyclewindows # bezel circular arrow

[Eddie Kane (eddiekane150)]

just did a apt-get update, apt-get update before shutdown. This bug occurred upon immediate power up.

[Seshu Reddy Cheedepudi (seshucl)]

As on Comment #8:
just did a apt-get update, apt-get dist-upgrade, reboot the system and installed Nvidia driver and restarted again. This bug occurred upon login immediatly.

[Eddie Kane (eddiekane150)]

Odd enough as it is, when i plug in a usb mouse that works.

[Iain Lane (laney)]

Got this when changing workspaces (xmonad + gnome fallback)

[Tyler R (hunterkasy)]

this happened to me after I let the computer run all night, got back on in the morning and it had this crash mine was on a 32 bit system

[Dan Kegel (dank)]

This has happened to me about once a day for the last five days, usually immediately upon login.
I'm only testing 64 bit precise, haven't checked to see if it happens in 32 bits as well.

[Bill Risch (brisch)]

Like privious poster it happens on startup. I just launched firefox and the problem occurred.
Also on 64 bit precise

[Rachel Greenham (rachel-strangenoises)]

Getting this trying to log in on an xdmcp session from a mac running Xephyr. Not sure if this error is related to initial attempt to log in with default Unity desktop, or subsequent attempt to log in with Unity2d, which is at least partially functional (various display bugs eg: short titlebars)

[Jeffrey Bouter (jbouter)]

Applied to me when I resized my VirtualBox window (In which Precise is running).

[Shelby Cain (alyandon)]

Happened while logging into box via x2go client - gnome-session --session=ubuntu-2d

[Alexi Helligar (alexih)]

Applied to me when I resized my VirtualBox window (In which Precise is running).

[Andres Sanchez (afsanchez93-deactivatedaccount)]

Applied to me when I resized my VirtualBox window (In which Precise is running).

[Romain Chossart (romainchossart)]

Happens to me sometimes when I use xrandr to make my monitor output "--above" my laptop's monitor.
I use a Awesome Window Manager on a Gnome session (the content of my /usr/share/gnome-session/sessions/gnome-awesome.session is attached)