Description of problem: Trying to launch applications from their icons on the GNOME panel crashes the desktop and logs you out. Version-Release number of selected component (if applicable): gnome-panel-3.0.0.1-4.fc15.i686 How reproducible: Always Steps to Reproduce: 1. Login using "Classic GNOME with compiz" option. 2. Drag an application icon to the GNOME panel at the top of the screen. 3. Click the application icon to launch it, and the WM crashes (and is restarted). 4. Click the application a second time, and the desktop throws up its hands and logs you out. Actual results: gnome-panel crashes, making users very unhappy. Expected results: The "classic" GNOME desktop behaviour. Additional info: From my dmesg log: gnome-panel[5322]: segfault at c ip 465e6547 sp bfb2e230 error 4 in libgtk-3.so.0.0.10[4640e000+42f000] gnome-panel[5447]: segfault at c ip 465e6547 sp bfc63bd0 error 4 in libgtk-3.so.0.0.10[4640e000+42f000] gnome-panel[5695]: segfault at c ip 465e6547 sp bf988340 error 4 in libgtk-3.so.0.0.10[4640e000+42f000] gnome-panel[5804]: segfault at c ip 465e6547 sp bfe61240 error 4 in libgtk-3.so.0.0.10[4640e000+42f000] gnome-panel[6070]: segfault at c ip 465e6547 sp bffa5940 error 4 in libgtk-3.so.0.0.10[4640e000+42f000] gnome-panel[6397]: segfault at c ip 465e6547 sp bfca77f0 error 4 in libgtk-3.so.0.0.10[4640e000+42f000] gnome-panel[6492]: segfault at c ip 465e6547 sp bf9b4ab0 error 4 in libgtk-3.so.0.0.10[4640e000+42f000] gnome-panel[6771]: segfault at c ip 465e6547 sp bfd486f0 error 4 in libgtk-3.so.0.0.10[4640e000+42f000] gnome-panel[6908]: segfault at c ip 465e6547 sp bff4d8c0 error 4 in libgtk-3.so.0.0.10[4640e000+42f000] gnome-panel[7146]: segfault at c ip 465e6547 sp bfbf2490 error 4 in libgtk-3.so.0.0.10[4640e000+42f000] gnome-panel[7454]: segfault at c ip 465e6547 sp bfda0a80 error 4 in libgtk-3.so.0.0.10[4640e000+42f000] gnome-panel[7756]: segfault at c ip 465e6547 sp bfc774e0 error 4 in libgtk-3.so.0.0.10[4640e000+42f000] gnome-panel[7836]: segfault at c ip 465e6547 sp bf9f3090 error 4 in libgtk-3.so.0.0.10[4640e000+42f000] gnome-panel[8430]: segfault at c ip 465e6547 sp bfd802c0 error 4 in libgtk-3.so.0.0.10[4640e000+42f000] Launching applications from the menus is fine. (Fortunately.)
Created attachment 501472 [details] core file from crash I have a small collection of core files, some from gnome-panel and others from /usr/libexec/notification-daemon. This one is from gnome-panel.
Created attachment 501473 [details] Another core file from gnome-panel
Created attachment 501474 [details] Yet another gnome-panel core
Created attachment 501475 [details] core file from notification-daemon
The applications I was using to crash gnome-panel were gnome-terminal and firefox.
I can confirm this bug. I got: gnome-panel-3.0.0.1-4.fc15.x86_64 gnome-panel-libs-3.0.0.1-4.fc15.x86_64 gdm-3.0.4-1.fc15.x86_64 compiz-0.9.4-2.fc15.x86_64 compiz-gnome-0.9.4-2.fc15.x86_64 kmod-nvidia-2.6.38.7-30.fc15.x86_64-270.41.06-2.fc15.1.x86_64 kmod-nvidia-270.41.06-2.fc15.1.x86_64 This bug makes GNOME w/ Compiz almost unusable.
And I have a Radeon RV350 card, so it's nothing to do with the NVIDIA binary blob.
This is the same issue as https://bugzilla.redhat.com/show_bug.cgi?id=699915 that was prematurely closed. I can reproduce it 100% on a 64-bit Fedora 15.
BTW, my Fedora 15 is not a fresh install, it is an upgrade from Fedora 14.
*** Bug 699915 has been marked as a duplicate of this bug. ***
Created attachment 505442 [details] contents of /var/spool/abrt subdirectory for gnome-panel crash
This looks like the same bug I was planning to report. I did an upgrade from F14 to F15 on x86_64 (two computers), and am using the fallback-mode with 8 workspaces, and about 10 icons on a single panel. If I "open" two or three applications from the icons, all is well. But then, with the 3d or 4th, the panel crashes. I know that it is the panel from looking at /var/log/messages. I also found that I could avoid the crashes if I launch the application by right-clicking on the panel icon and selecting "Launch". I noticed that, when I did this, the panel stayed in place. When I simply clicked on the icon (the thing that caused the crash), the panel would disappear and then return, a useless piece of glitz that I'm sure is meant to appeal to the "younger audience" that Gnome 3 is meant to attract. (I am 67 and have been using RedHat/Fedora since 1996.) Furthermore, I discovered that I could solve the entire problem by turning off "animations" by using dconf-editor. So I have done that, and the problem is solved for me. The problem is solved for me, and easily solved in general by turning off animations (whatever they are) for everyone, so I probably won't be able to respond to further requests for information. Therefore, I am going to try to attach two tar files that seem to be related to the crashes, from /var/spool/abrt, if I can find the place to add attachments. (Apparently they did not get sent automatically.) If I can't, then my email is baron.edu, and anyone can request them.
Created attachment 505444 [details] I hope the secont promised attachment (not sure the first got through)
I think I found another hint. This just happens when running with compiz. Currently I have activated the fallback mode, but I am using metacity and this does not cause any problems. Jonathan, are you running compiz?
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- after drag'n'drop "Terminal" from Programs -> System tools -> Terminal to panel.
Got the same crashes as Jonathan reported. However I'm running the new GNOME3 desktop. I start the panel from a terminal window with gnome-panel --replace It crashes when Left-click on on launcher (the application to be launched start normally, but the panel crashes)
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- 1.- I don't know ._.
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- tweeked gnome 3 panel witch on reboot disappeared along with window borders now using gnome with compiz session
Hello, I am getting the same error with Fedora 15 in Gnome3 fallback mode. I am running the default WM (which is Mutter I think?). Definitely not Compiz, as I don't even have it installed.
I can confirm jonathan baron's fix, running: "dconf write /org/gnome/desktop/interface/enable-animations false" makes this crash go away, and if I set: "dconf write /org/gnome/desktop/interface/enable-animations true" the crash reappears. I'm running F15 i686.
More information -- I'm running fallback mode with an ATI Technologies Inc RV350 AP [Radeon 9600] (PCI ID: 1002:4150), using the Open Source 'radeon' driver. The system was upgraded to F15-beta from F14 with 'preupgrade', then updated to release F15 with standard YUM. It's got the latest yum updates installed.
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- I logged into "classic Gnome with Compiz". I navigated to Firefox in the Applications menu, dragged the Firefox icon to the panel, and clicked on the icon to open Firefox. Firefox started successfully, and the ABRT notification came up. I was able to reproduce it by quitting Firefox and then clicking on the icon to restart Firefox.
Hitting the same issue, here's a debug back trace and a couple print outs: Program received signal SIGSEGV, Segmentation fault. _gtk_style_context_coalesce_animation_areas (context=0x0, widget=0xdb8710) at gtkstylecontext.c:3160 3160 priv = context->priv; (gdb) thread apply all bt Thread 4 (Thread 0x7f1b9bfff700 (LWP 5477)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:219 #1 0x00000039ee002405 in g_cond_timed_wait_posix_impl (cond=<optimized out>, entered_mutex=<optimized out>, abs_time=<optimized out>) at gthread-posix.c:242 #2 0x00000039eb8188bf in g_async_queue_pop_intern_unlocked (queue=0xc004d0, try=0, end_time=0x7f1b9bffebd0) at gasyncqueue.c:415 #3 0x00000039eb86aa89 in g_thread_pool_wait_for_new_task (pool=0xbf3f70) at gthreadpool.c:274 #4 g_thread_pool_thread_proxy (data=<optimized out>) at gthreadpool.c:308 #5 0x00000039eb8683a6 in g_thread_create_proxy (data=0xe88910) at gthread.c:1955 #6 0x00007f1bb2688af1 in start_thread (arg=0x7f1b9bfff700) at pthread_create.c:305 #7 0x00007f1bb23c7b7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 3 (Thread 0x7f1bab052700 (LWP 5072)): #0 0x00007f1bb23bf293 in __poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00000039eb842d24 in g_main_context_poll (n_fds=3, fds=0x7f1ba4001150, priority=<optimized out>, timeout=-1, context=0xb4fa90) at gmain.c:3405 #2 g_main_context_iterate (context=0xb4fa90, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3087 #3 0x00000039eb84360d in g_main_loop_run (loop=0xb4fa70) at gmain.c:3300 #4 0x00000039f04b4564 in gdbus_shared_thread_func (data=<optimized out>) at gdbusprivate.c:276 #5 0x00000039eb8683a6 in g_thread_create_proxy (data=0xb4fb80) at gthread.c:1955 #6 0x00007f1bb2688af1 in start_thread (arg=0x7f1bab052700) at pthread_create.c:305 #7 0x00007f1bb23c7b7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7f1baa644700 (LWP 5073)): #0 0x00007f1bb23bf293 in __poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00000039eb842d24 in g_main_context_poll (n_fds=1, fds=0x7f1b9c001170, priority=<optimized out>, timeout=-1, context=0xb29f80) at gmain.c:3405 #2 g_main_context_iterate (context=0xb29f80, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3087 #3 0x00000039eb84360d in g_main_loop_run (loop=0x7f1b9c001150) at gmain.c:3300 #4 0x00007f1baa64eb6b in dconf_context_thread (data=0xb29f80) at dconfcontext.c:11 #5 0x00000039eb8683a6 in g_thread_create_proxy (data=0xb2a5f0) at gthread.c:1955 #6 0x00007f1bb2688af1 in start_thread (arg=0x7f1baa644700) at pthread_create.c:305 #7 0x00007f1bb23c7b7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7f1bb2f059a0 (LWP 5071)): #0 _gtk_style_context_coalesce_animation_areas (context=0x0, widget=0xdb8710) at gtkstylecontext.c:3160 #1 0x00000039f927a2eb in _gtk_widget_draw_internal (clip_to_size=1, cr=0x39f46a7f20, widget=0xdb8710) at gtkwidget.c:5710 #2 _gtk_widget_draw_internal (widget=0xdb8710, cr=0x39f46a7f20, clip_to_size=<optimized out>) at gtkwidget.c:5680 #3 0x00000039f927a461 in gtk_widget_send_expose (widget=0xdb8710, event=<optimized out>) at gtkwidget.c:5951 #4 0x00000039f914857c in gtk_main_do_event (event=0x7fffe8dbb760) at gtkmain.c:1797 #5 0x00000039fc8341af in _gdk_window_process_updates_recurse (window=0xd5d240 [GdkX11Window], expose_region=0xe7f910) at gdkwindow.c:3855 #6 0x00000039fc83377f in gdk_window_process_updates_internal (window=0xd5d240 [GdkX11Window]) at gdkwindow.c:4011 #7 0x00000039fc833bf0 in gdk_window_process_all_updates () at gdkwindow.c:4142 #8 0x00000039f90c8426 in gtk_container_idle_sizer (data=<optimized out>) at gtkcontainer.c:1606 #9 0x00000039fc819daf in gdk_threads_dispatch (data=0xd3a000) at gdk.c:741 #10 0x00000039eb8427ed in g_main_dispatch (context=0xab62a0) at gmain.c:2441 #11 g_main_context_dispatch (context=0xab62a0) at gmain.c:3014 #12 0x00000039eb842fc8 in g_main_context_iterate (context=0xab62a0, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3092 #13 0x00000039eb84360d in g_main_loop_run (loop=0xbee7e0) at gmain.c:3300 #14 0x00000039f914771d in gtk_main () at gtkmain.c:1358 #15 0x000000000042160f in main (argc=1, argv=0x7fffe8dbbb58) at main.c:115 (gdb) f 0 #0 _gtk_style_context_coalesce_animation_areas (context=0x0, widget=0xdb8710) at gtkstylecontext.c:3160 3160 priv = context->priv; (gdb) up #1 0x00000039f927a2eb in _gtk_widget_draw_internal (clip_to_size=1, cr=0x39f46a7f20, widget=0xdb8710) at gtkwidget.c:5710 5710 _gtk_style_context_coalesce_animation_areas (context, widget); (gdb) list 5705 0, cr, 5706 &result); 5707 } 5708 5709 context = gtk_widget_get_style_context (widget); 5710 _gtk_style_context_coalesce_animation_areas (context, widget); 5711 } 5712 5713 /** 5714 * gtk_widget_draw: (gdb) print *widget $1 = {parent_instance = {g_type_instance = {g_class = 0x0}, ref_count = 0, qdata = 0x0}, priv = 0xdb8750}
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Firefox was open from desktop panel.
I tried disabling animation, but I still get the ABRT notification when I click on a panel icon.
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- FC14->FC15 upgrade In start gnome-fallback-mode Add launchers to panel Launch program with launcher This happens any-time a launcher in the panel (not in the menues!) is klicked
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Whenever i open a new gnome-terminal from a gnome-panel, the gnome-panel got crashed. I have created shorcut to gnome-terminal in gnome-panel, i am not able to remove that shorcut.
(In reply to comment #27) > Whenever i open a new gnome-terminal from a gnome-panel, the gnome-panel got > crashed. I have created shorcut to gnome-terminal in gnome-panel, i am not able > to remove that shorcut. you have to press alt on the keyboard when click your right mouse button. I had to google to find this out ...
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- This happens when I log in to "Classic GNOME with Compiz" session.
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- sertwertasert
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- sergsrtwst
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- dtgsgfgsdfg
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Rebooted - spontaneous crash
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Gnome-panel crashed when starting Evolution in fallback mode. It also crash when starting Empathy, maybe something related to the notification area.
(In reply to comment #34) > Package: gnome-panel-3.0.0.1-4.fc15 > Architecture: x86_64 > OS Release: Fedora release 15 (Lovelock) > > Comment > ----- > Gnome-panel crashed when starting Evolution in fallback mode. It also crash > when starting Empathy, maybe something related to the notification area. Well, I saw this bug report too late, it's effectively when launching every app from a launcher on the gnome panel... Disabling the compositing manager avoids this problem.
Confirming this bug here too. Running GNOME with Compiz on an ATI Radeon HD4200. Clicking a launcher link once crashes gnome-panel and opens the app. Once gnome-panel restarts, clicking on another launcher crashes gnome-panel, then crashes gnome completely, requiring me to log out and back in again.
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- moved the firefox icon to the panel
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Started the computer, and open the Google Chrome.
I can confirm this bug. It comes out even with the simple metacity compositor enabled. It also happens in qemu non-accelerated virtual machines.
Package: gnome-panel-3.0.0.1-4.fc15.x86_64 This bug makes unusable compiz with gnome-panel under Fedora 15. Combination metacity + gnome-panel is OK. Combination of another panel with compiz is OK also, including fbpanel, lxpanel, xfce4-panel, not crashed after launcher click at least. The bug can be reproduced to easy. Start gnome+compiz session, then just add any launcher to gnome-panel and click it. Probably, first click will cause restart, but second one effectively crashes gnome-panel and all session. If any gnome-terminal still opened, it is possible to ignore black screen of death pressing Alt-F4, then restart panel from terminal command prompt: $ gnome-panel --replace Again, click the launcher and see 11th signal message after gnome-panel crash.
I'm getting this. Is this not this bug from gnome-panel: https://bugzilla.gnome.org/show_bug.cgi?id=641325 The fix has made it to the gnome-panel code, but I don't know if it's included in gnome-panel-3.0.0.1 as shipping with FC15. If it hasn't, and that would fix the issue, could we please have the patch applied? The application launchers are unusable in gnome-panel without this being fixed.
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Started Pidgin in GNOME classic from the panel launcher.
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Started virt-manager from gnome-panel launcher.
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Started Pidgin from the task bar in GNOME classic
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- i logout gnome 3 and start gnome in classic way with compiz
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- it crashed again when i restart gnome classic
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- crashed all time in gnome classic with compiz when i run a program from taskbar or play with workspaces!
So does the fix in comment #43 fix this? If so has it been applied to an update I could get? This is a very annoying bug.
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Don't know
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- pressed home icon near "Places"
(In reply to comment #20) > I can confirm jonathan baron's fix, running: > "dconf write /org/gnome/desktop/interface/enable-animations false" > > makes this crash go away, and if I set: > "dconf write /org/gnome/desktop/interface/enable-animations true" > the crash reappears. I'm running F15 i686. upgraded to F15 from F13, running compiz, this 'dconf' makes the problem go away for me too. I have ati graphics driver, not the free one. I was about to restore to F13 from backups, until I saw the 'dconf' workaround here. May I please get a new gnome-panel with the fix in it? Thanks!
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- open pidgin from gnome 3 fallback panel cause the panel to crash
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- crashed by starting firefox
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- I don't know
It looks like a fix was committed upstream: http://git.gnome.org/browse/gnome-panel/commit/?id=8c275a2adf4ad99297a17cabf251344837620831 It haven't checked it yet though.
I've just tested the patch, it works fine.
Package: gnome-panel-3.0.0.1-4.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- enter on compiz
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping