GNOME Bugzilla – Bug 662023
gnome-panel crashes with multiple screens
Last modified: 2012-03-16 15:30:12 UTC
this report has been filed here: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/875829 "When multiple X screens are configured not using Xinerama or TwinView, gnome-panel segfaults on start. teevee@complete:~$ gnome-panel (gnome-panel:7486): Gtk-CRITICAL **: gtk_style_context_get: assertion `priv->widget_path != NULL' failed Segmentation fault" "(gdb) r Starting program: /usr/bin/gnome-panel [Thread debugging using libthread_db enabled] [New Thread 0x7fffed986700 (LWP 8258)] [New Thread 0x7fffed185700 (LWP 8259)] warning: the debug information found in "/usr/lib/debug//usr/lib/libxml2.so.2.7.8" does not match "/usr/lib/libxml2.so.2" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/usr/lib/libxml2.so.2.7.8" does not match "/usr/lib/libxml2.so.2" (CRC mismatch). (gnome-panel:8255): Gtk-CRITICAL **: gtk_style_context_get: assertion `priv->widget_path != NULL' failed Program received signal SIGSEGV, Segmentation fault. thread_memory_magazine2_free (mem=0x7ffff73c36a7, ix=<optimized out>, tmem=<optimized out>) at /build/buildd/glib2.0-2.30.0/./glib/gslice.c:808 808 /build/buildd/glib2.0-2.30.0/./glib/gslice.c: No such file or directory. in /build/buildd/glib2.0-2.30.0/./glib/gslice.c (gdb) bt
+ Trace 228826
I have the same issue also
I updated the version. Ubuntu 11.10 ships gnome 3.2. The traceback references GTK+3, etc. It can't be 2.32.
I'm having the same issue on my updated 11.10 Ubuntu Oneiric. Also 2 monitors configured as separate screens, and same segementation fault error.
I have update yesterday to gnome3 and having the same issue. I have two screen configured and the gnome-panel now dies on start.
changed my video card (now a GT520) and got it to work in twinview mode (separate screens still fails though). Looks like you need modern hardware or more video RAM (my previous GT8600 had only 256Mb) in order to get gnome3 working in multi-monitor environments...
I have the same problem. Gnome shell doesn't start with separate x screen configuration.
Have the same problem. Gnome 3 doesn't start with separate X screen configuration.
I am witnessing the same thing with Fedora 15 x86_64 with GNOME 3.2.1 and NVIDIA propriety drivers. glxinfo / glxgears runs fine. I get this error when I run multiple screens with TwinView turned off and Xinerama turned off. sudo gdb gnome-shell GNU gdb (GDB) Fedora (7.3.1-47.fc15) Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/gnome-shell...Reading symbols from /usr/lib/debug/usr/bin/gnome-shell.debug...done. done. (gdb) r --replace Starting program: /usr/bin/gnome-shell --replace warning: the debug information found in "/usr/lib/debug//usr/lib64/libtelepathy-logger.so.2.2.0.debug" does not match "/usr/lib64/libtelepathy-logger.so.2" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/usr/lib64/libtelepathy-logger.so.2.2.0.debug" does not match "/usr/lib64/libtelepathy-logger.so.2" (CRC mismatch). Missing separate debuginfo for /usr/lib64/libtelepathy-logger.so.2 Try: yum --disablerepo='*' --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/4b/10438f6a294bb44a13a5d8542ca3984e49da0b.debug [Thread debugging using libthread_db enabled] Detaching after fork from child process 1279. [New Thread 0x7fffdd776700 (LWP 1286)] Detaching after fork from child process 1287. [New Thread 0x7fffdcf75700 (LWP 1291)] Detaching after fork from child process 1292. [New Thread 0x7fffd7fff700 (LWP 1293)] [New Thread 0x7fffd77fe700 (LWP 1294)] Detaching after fork from child process 1295. Window manager warning: Log level 8: gtk_style_context_get: assertion `priv->widget_path != NULL' failed Program received signal SIGSEGV, Segmentation fault. *INT_cairo_pattern_reference (pattern=0x1) at cairo-pattern.c:761 761 CAIRO_REFERENCE_COUNT_IS_INVALID (&pattern->ref_count)) Missing separate debuginfos, use: debuginfo-install freetype-freeworld-2.4.4-6.fc15.x86_64 (gdb) thread apply all Please specify a command following the thread ID list (gdb) bt
+ Trace 229536
Id Target Id Frame 5 Thread 0x7fffd77fe700 (LWP 1294) "gnome-shell" pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165 4 Thread 0x7fffd7fff700 (LWP 1293) "threaded-ml" 0x00007fffedf42bd3 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 3 Thread 0x7fffdcf75700 (LWP 1291) "gnome-shell" 0x00007fffedf42bd3 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 2 Thread 0x7fffdd776700 (LWP 1286) "gnome-shell" 0x00007fffedf42bd3 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 * 1 Thread 0x7ffff7f809e0 (LWP 1249) "gnome-shell" *INT_cairo_pattern_reference (pattern=0x1) at cairo-pattern.c:761 (gdb)
Seems more like this is gtk+. Moving.
I can also repport this issue and while googling it seems like there is almost everyone that uses two screens (without xinerama or twinview) that has this problem. There should be quite a few users with this configuration that has to choose to not use gnome3 or not use their second monitor. Please consider raising priority of this bug!!
Dear Olav, is this for sure sure or it just seems?
I get the exact(?) same error when running mutter --replace. Could this points toward a gtk+ error?
I have this problem too. I cannot run gnome-classic mode either. This is a really bad problem for anyone with dual monitors using dual X-servers. (gnome-panel:3447): Gtk-CRITICAL **: gtk_style_context_get: assertion `priv->widget_path != NULL' failed (gnome-panel:3447): Gtk-CRITICAL **: gtk_style_context_get: assertion `priv->widget_path != NULL' failed gnome-session[3263]: WARNING: Application 'gnome-panel.desktop' killed by signal
Here's a stack dump from running: gdb gnome-panel [Thread debugging using libthread_db enabled] [New Thread 0x7fffede2d700 (LWP 5512)] [New Thread 0x7fffed424700 (LWP 5513)] (gnome-panel:5508): Gtk-CRITICAL **: gtk_style_context_get: assertion `priv->widget_path != NULL' failed Program received signal SIGSEGV, Segmentation fault. 0x00007ffff458ff0f in g_slice_free1 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 (gdb) bt
+ Trace 229653
The above trace was from gnome-panel 3.2.1-2+b1.
We need a stacktrace with debug packages installed for glib2, gtk3 and gnome-panel... Can you please provide that?
What about the stacktrace at the beginning of this report?
The one at the beginning is better but misses symbols for gtk3.
Clearly this ticket also applies to gtk2. Is gtk2 not supported any longer? jcoffland@slick:~$ gdb gnome-panel GNU gdb (GDB) 7.3-debian Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/gnome-panel...(no debugging symbols found)...done. (gdb) r Starting program: /usr/bin/gnome-panel [Thread debugging using libthread_db enabled] [New Thread 0x7fffef4eb700 (LWP 13891)] [New Thread 0x7fffeeae2700 (LWP 13892)] (gnome-panel:13888): Gtk-CRITICAL **: gtk_style_context_get: assertion `priv->widget_path != NULL' failed Program received signal SIGSEGV, Segmentation fault. thread_memory_magazine2_free (mem=0x7ffff73c5307, ix=<optimized out>, tmem=<optimized out>) at /tmp/buildd/glib2.0-2.30.2/./glib/gslice.c:808 808 /tmp/buildd/glib2.0-2.30.2/./glib/gslice.c: No such file or directory. in /tmp/buildd/glib2.0-2.30.2/./glib/gslice.c (gdb) bt
+ Trace 229666
(In reply to comment #19) > Clearly this ticket also applies to gtk2. Is gtk2 not supported any longer? gtk_style_context_get does not exist in gtk2
So what would it take to get this working? I would like to be able to use gnome-panel with dual screens using dual x-servers. I know there are many others with this configuration because I've worked on other bugs for this setup in the past. It's not that I'm just being stubborn about moving to Gnome3, Unity, gnome-shell, etc. It's that they also don't work with my setup and appear to have even more serious problems with dual x-servers. It's a little embarrassing when Windows users are running 5 or 6 monitors on one machine and I cannot even get two to work reasonably in Gnome3. I believe a lot of the anger around gnome3 is because people have had serious problems using fallback mode let alone gnome3. I think it is great that gnome3 is blazing a new trail but in the meantime, while it's still becoming robust, we need a smooth transition. Fixes like this go along way to appeasing the angry masses. Please let me know how I can help.
same problem here
Joseph's stacktrace in comment 19 misses two symbols at the very beginning... Can anybody else who has the same problem please provide another stacktrace with debug symbols?
maybe this bug is related to https://bugzilla.gnome.org/show_bug.cgi?id=648156 ?!
Created attachment 209135 [details] xorg.conf for use with seperate screens (LCDs) this is my xorg.conf file for running separate screens (two LCDs, 1 30" and 1 24") with NVIDIA's driver and TwinView and Xinerama disabled.
gnome-panel full bt. I booted into run-level 3 and started X with startx. I don't get the fallback GNOME. I start a terminal and run "gdb gnome-panel". Here's the full backtrace: [allen@StudioXPS8100 ~]$ gdb gnome-panel GNU gdb (GDB) Fedora (7.3.50.20110722-10.fc16) Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/gnome-panel...Reading symbols from /usr/lib/debug/usr/bin/gnome-panel.debug...done. done. (gdb) r --replace Starting program: /usr/bin/gnome-panel --replace [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffe7837700 (LWP 3673)] [New Thread 0x7fffe6e24700 (LWP 3677)] (gnome-panel:3576): Gtk-CRITICAL **: gtk_style_context_get: assertion `priv->widget_path != NULL' failed Program received signal SIGSEGV, Segmentation fault. thread_memory_magazine2_free (mem=0x7ffff73c7807, ix=<optimized out>, tmem=<optimized out>) at gslice.c:808 808 chunk->data = NULL; (gdb) bt full
+ Trace 229822
gnome-shell full bt. I booted into run-level 3 and started X with startx. I get the fallback GNOME (the above for gnome-panel is incorrect; I always get the fallback GNOME session). I start a terminal and run "gdb gnome-shell". Here's the full backtrace: [allen@StudioXPS8100 ~]$ gdb gnome-shell GNU gdb (GDB) Fedora (7.3.50.20110722-10.fc16) Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/gnome-shell...Reading symbols from /usr/lib/debug/usr/bin/gnome-shell.debug...done. done. (gdb) r --replace Starting program: /usr/bin/gnome-shell --replace [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffdd266700 (LWP 6625)] [New Thread 0x7fffdca65700 (LWP 6626)] [New Thread 0x7fffd7fff700 (LWP 6630)] [New Thread 0x7fffd77fe700 (LWP 6634)] Window manager warning: Log level 8: gtk_style_context_get: assertion `priv->widget_path != NULL' failed Program received signal SIGSEGV, Segmentation fault. *INT_cairo_pattern_reference (pattern=0x1) at cairo-pattern.c:761 761 CAIRO_REFERENCE_COUNT_IS_INVALID (&pattern->ref_count)) (gdb) bt full
+ Trace 229823
To reproduce in without special hw: Xephyr :1 -screen 800x600 -screen 800x600 & export -n DBUS_SESSION_BUS_ADDRESS export DISPLAY=:1 gnome-panel With a single screen, the panel works fine gtk3-demo works fine with 2 screens This is a problem related to native windows and bg-image; the relevant code is in gnome-panel/panel-widget.c:panel_widget_realize
Should be fixed with http://git.gnome.org/browse/gtk+/commit/?id=5d579811843f81db9866ac81afc5297f776cfb3b And the followup crashes should be fixed with the next 2 commits.
I'm not sure if this is an issue with mutter or gtk+, but this commit causes serious trouble with mutter (window title bar is black allover, close button is garbled, tons of debug messages in .xsession error) When reverting it in a current git checkout everything is normal again. By the way, I'm running current GNOME 3.3.91+
(In reply to comment #30) > I'm not sure if this is an issue with mutter or gtk+, but this commit causes > serious trouble with mutter (window title bar is black allover, close button is > garbled, tons of debug messages in .xsession error) > > When reverting it in a current git checkout everything is normal again. > > By the way, I'm running current GNOME 3.3.91+ This is bug #671796, and there's a patch there too.
For the record: the committed fix breaks gnome-control-center, too. See bug #672173 for details.