GNOME Bugzilla – Bug 728554
Setting RANDR primary output crashes gnome-shell
Last modified: 2014-04-22 09:02:39 UTC
When trying to start Gnome session, gnome-shell segfaults with following stacktrace: Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGTRAP, Trace/breakpoint trap.
+ Trace 233494
$1 = {type = 0, display = 0x1f6f2a0, resourceid = 696, serial = 344, error_code = 8 '\b', request_code = 139 '\213', minor_code = 30 '\036'} (gdb) This error event is generated by RRSetOutputPrimary request, which I confirmed under awesomewm, by running 'xrandr --output eDP-1-0 --primary' with result: ~ $ xrandr --output eDP-1-0 --primary X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 139 (RANDR) Minor opcode of failed request: 30 (RRSetOutputPrimary) Serial number of failed request: 31 Current serial number in output stream: 33 This is with intel+nvidia hybrid setup. Attached xorg.conf.
Created attachment 274728 [details] Xorg configuration
*** This bug has been marked as a duplicate of bug 725802 ***