GNOME Bugzilla – Bug 336896
Invoking Alt-F2 crashes panel
Last modified: 2006-08-31 11:53:17 UTC
Steps to reproduce: 1. Invoke Alt-F2 2. Type in command to run 3. Panel crashes, dialogue "I've detected a panel already running, and will now exit." appears ad infinitum. 4. doing "kill 2912" or "killall gnome-panel" just makes the same dialogue return. Stack trace: $ gdb gnome-panel GNU gdb 6.4-debian Copyright 2005 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i486-linux-gnu"...(no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (gdb) run Starting program: /usr/bin/gnome-panel (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1224418656 (LWP 12384)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) ---Type <return> to continue, or q <return> to quit--- (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) GTK Accessibility Module initialized (no debugging symbols found) (no debugging symbols found) Bonobo accessibility support initialized (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Comment: This is where the dialogue appears, and on clicking on "OK" this appears:] Program exited with code 0377. (gdb) thread apply all bt (gdb) bt No stack. (gdb) Other information: I'm running the current development release of Ubuntu Dapper.
Hi, thanks for your bug report but the backtrace is not really helpful, can you install gnome-panel-dbg (sudo apt-get install gnome-panel-dbg) and attach the backtrace again with debugging symbols?
Sorry for the simple question, but how do I stop gnome-panel so I can run it with gdb? If I kill it it just comes back again. Thanks.
Well, I don't really know, some signal will probaly do it, but you don't need that. You can find out the pid of gnome-panel with "ps ax | grep gnome-panel" and then do a "gdb -p PID", you can then type "continue", produce the crash, and should then be able to get the bracktrace.
1. open terminal 2. gnome-session-remove gnome-panel 3. gdb /path/to/gnome-panel make sure you have debugging packages of gnome-panel, glib and the most important Gnome libraries installed.
Ok, I hope this is more helpful. Tell me if not. # "gdb -p xxxx" for gnome-panel. 0xffffe410 in __kernel_vsyscall () (gdb) continue Continuing. # Alt-F2 to run "gonf-editor" (I can't reproduce the crash with other # programs--this is the one it happens consistently with). Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1224111456 (LWP 26807)] 0xb7b7572d in gtk_tree_model_filter_convert_iter_to_child_iter () from /usr/lib/libgtk-x11-2.0.so.0 (gdb) continue Continuing. # When I type continue this time, the dialogue "The application gnome-panel # has quit unexpectedly. Restart ? ..." etc. I do "Restart Application" # Program exited with code 01. # # gnome-panel restarts, and I get the dialogue "I have detected another panel # already running and will exit now." # This time (maybe some package has changed since I first reported the # problem) this last dialogue only appears once, whereas in the past every # time I clicked it it would appear again.
I am confused. so it is gconf-editor that you can make crash? the initial stack trace however is from a crashed gnome-panel. or are we talking about two different problems here? if so, please open a new report for the gconf-editor problem (bug-buddy automatically opens a new report).
gconf-editor is not crashing. When I use the Alt-F2 dialogue to open it, gnome-panel crashes. gnome-panel only crashes when I open certain applications with the Alt-F2 dialogue, such as gconf-editor and a couple others, but I can use it to open most applications without a problem.
This is most probably bug #326362. Does it still happen with GTK+ >= 2.8.16?
I'm using libgtk2.0 2.8.17-1ubuntu1, if that helps, and it still happens.
Can confirm this happens to me with the commands 'gconf-editor' and any 'killall' command.
It should be fixed in GTK+ 2.10. *** This bug has been marked as a duplicate of 326362 ***