GNOME Bugzilla – Bug 649676
Gnome-Shell segfaults when two monitors is connected.
Last modified: 2011-07-23 19:34:45 UTC
I have an issue starting Gnome 3 when i have two monitors connected causing a segfault with the following error. [ 1117.070047] gnome-shell: segfault at 5 ip 00007fb5bada7f59 sp 00007fffedc92070 error 4 in libcairo.so.2.11000.2[7fb5bad6f000+a9000]
This issue only appears when my second monitor is either plugged in or specified in the xorg configuration. If i plug out one monitor or comments out the section in the Xorg configuration Gnome-Shell starts without any issues *iam right now filing this bug from Gnome 3*
However because of this issue i have to plug back the second monitor and start another Desktop Envoirment eg XFCE when i want to watch movies on the second monitor / TV - and when going back to Gnome i need to plug out one monitor. I do need to point out that this hapens on both my Desktop PC & Laptop with a pretty much identical setup. Here's some hardware information.
Distrubition: Arch Linux - 64
GPU: Nvidia GTS 450
GPU Drivers: nvidia 270.41.06-1
Distrubition: Arch Linux - 64
GPU: Nvidia GT 420M
GPU Drivers: nvidia 270.41.06-1
May 7 18:00:04 Peteware kernel: [ 1111.720682] HDMI hot plug event: Pin=5 Presence_Detect=0 ELD_Valid=0
May 7 18:00:04 Peteware kernel: [ 1111.790992] HDMI hot plug event: Pin=5 Presence_Detect=0 ELD_Valid=1
May 7 18:00:05 Peteware kernel: [ 1112.436590] HDMI: detected monitor SAMSUNG
May 7 18:00:05 Peteware kernel: [ 1112.436592] at connection type HDMI
May 7 18:00:05 Peteware kernel: [ 1112.436595] HDMI: available speakers: FL/FR
May 7 18:00:05 Peteware kernel: [ 1112.436598] HDMI: supports coding type LPCM: channels = 2, rates = 44100 48000 88200, bits = 16 20 24
May 7 16:00:09 Peteware rtkit-daemon: Successfully made thread 10850 of process 10850 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
May 7 16:00:09 Peteware rtkit-daemon: Successfully made thread 10881 of process 10881 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
May 7 18:00:09 Peteware kernel: [ 1117.070047] gnome-shell: segfault at 5 ip 00007fb5bada7f59 sp 00007fffedc92070 error 4 in libcairo.so.2.11000.2[7fb5bad6f000+a9000]
May 7 18:00:09 Peteware gnome-session: WARNING: Application 'gnome-shell.desktop' killed by signal
May 7 18:00:10 Peteware kernel: [ 1117.373764] gnome-shell: segfault at 5 ip 00007ff1e6f3cf59 sp 00007fffd8df69a0 error 4 in libcairo.so.2.11000.2[7ff1e6f04000+a9000]
May 7 18:00:10 Peteware gnome-session: WARNING: Application 'gnome-shell.desktop' killed by signal
May 7 18:00:10 Peteware gnome-session: WARNING: App 'gnome-shell.desktop' respawning too quickly
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Starting program: /usr/bin/gnome-shell
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffe6d2e700 (LWP 4969)]
[New Thread 0x7fffe652d700 (LWP 4970)]
[New Thread 0x7fffe4fc4700 (LWP 4971)]
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff65c0f59 in cairo_pattern_reference () from /usr/lib/libcairo.so.2
(gdb) thread apply all bt
(Thread 0x7ffff7fae920 (LWP 4966))
Please install debug packages for lib(cairo), (lib)gtk3, (lib)glib2 and mutter and attach an updated stacktrace.
I am also experiencing this issue using the proprietary ATI drivers (catalyst). gnome-shell works fine on the open source ones. If I figure out how to turn these debug options on, I'll post a trace.
Pete, do you have multiple X screens configured in xorg.conf? If you do, then this is a dupe of bug 648156. TwinView is what you should be using if that's the case.
Cole, the same is valid for you. Do you use multiple X screens?
Yes, I believe that is what aticonfig gave me. But TwinView is a feature fo the nVidia drivers, correct? Do I need to be using Xinerama?
(In reply to comment #6)
> Yes, I believe that is what aticonfig gave me. But TwinView is a feature fo
> the nVidia drivers, correct? Do I need to be using Xinerama?
I never used the catalyst drivers (formerly fglrx) but I hear that they have lots of issues with gnome-shell. You should be much better served by using the free radeon drivers.
Anyway what I suggest you to use is a driver which conforms to XRandR 1.2 (or greater) like the free radeon driver which will allow the Display panel in gnome-control-center to configure your multi-display setup without static xorg.conf configurations.
> I never used the catalyst drivers (formerly fglrx) but I hear that they have
> lots of issues with gnome-shell. You should be much better served by using the
> free radeon drivers.
The free drivers work amazingly. Unfortunately, I want OpenCL support, which is why I'm using fglrx. I guess it's back to KDE for now.
any conclusion on bug report ? If there is no further information required, bug should be moved out of needinfo state.
I can confirm that it works if i use Xinerama.
However this is something i do absolutley not want, the way i have configured Xorg is to give my TV it's own desktop *And i have configured the layout like this*
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" 2000 0
Why i am doing this is to prevent the mouse pointer to reach the other screen, since that's just so annoying. I am using a script called mouse-switchscreen i execute when i want to move my mouse pointer between screens. Gnome 2.x did this wonderful and i see no reason why i should be forces to use either Xinerama or TwinView.
The second reason is that there's just too much Video Tearing when watching movies on my TV through Gnome-Shell. So the most perfect solution would be if i could start a Gnome-Fallback that does not use the composite extension on my TV, and use Gnome-Shell on my Primiary Desktop Screen.
However this is also not possible - since there's no option for me from what i found to configure the gnome-session to allow such.
So my quick an dirty solution have been to.
1. Start a WM on DISPLAY:0.1
2. Start Gnome Shell on DISPLAY:0.0 to prevent gnome shell to start on the second screen.
The best solution would simply be Add a feature to the gnome-session that allows me to specify wich WM should be on wich screen.
*** This bug has been marked as a duplicate of bug 648156 ***