GNOME Bugzilla – Bug 336311
Gnome panel crashes
Last modified: 2007-01-02 19:00:16 UTC
Distribution: Fedora Core release 5 (Bordeaux) Package: gnome-panel Severity: major Version: GNOME2.14.0 2.14.x Gnome-Distributor: Red Hat, Inc Synopsis: Gnome panel crashes Bugzilla-Product: gnome-panel Bugzilla-Component: Panel Bugzilla-Version: 2.14.x BugBuddy-GnomeVersion: 2.0 (2.14.0) Description: Description of the crash: Gnome panel crashes Steps to reproduce the crash: 1. I started gaim (appeared in notification area) 2. I stopped it. 3. Gnome panel crashed. Expected Results: Crash How often does this happen? I got this problem twice today. I am not sure, but I think first time it was also connected with notification area. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) `shared object read from target memory' has disappeared; keeping its symbols. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208371536 (LWP 17506)] (no debugging symbols found) 0x007ce402 in __kernel_vsyscall ()
+ Trace 67289
Thread 1 (Thread -1208371536 (LWP 17506))
---------------------------------------------------------------------- Samochod zwany EOS... >>> http://link.interia.pl/f191c ------- Bug created by bug-buddy at 2006-03-28 08:06 -------
crash in gtk+, reassigning Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. install the gtk+ debugging package, please.
Looks more like an a11y problem to me. Notice the gail functions in the stacktrace
*** Bug 339995 has been marked as a duplicate of this bug. ***
*** Bug 342794 has been marked as a duplicate of this bug. ***
Reassigning to gail for now.
I'm going to need some help from the gtk+ team on this one...
*** Bug 349449 has been marked as a duplicate of this bug. ***
mclasen? comment #6
I need a stack trace with symbols - the above stack trace isn't very useful since gdb seems to just be grabbing the first public symbols it finds in some of the sources... ?
(In reply to comment #9) > I need a stack trace with symbols - the above stack trace isn't very useful > since gdb seems to just be grabbing the first public symbols it finds in some > of the sources... ? How to install libraries to have full stack (I prefer yum installation)? And which ones do I need to install? I am not able to reproduce my bug report with gaim but I think I have similar problem with meld (easy reproducable but meld is Python app - does it matter?)
http://live.gnome.org/GettingTraces/DistroSpecificInstructions should give you some information
Is it enough? Meld crashed when started with 2 directories compare - it was creating file/directories trees in 2 panels. I installed 2 debug packages: gtk2-debuginfo-2.8.20-1.i386.rpm libgnomeui-debuginfo-2.14.1-1.fc5.1.i386.rpm Backtrace was generated from '/usr/bin/meld' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208723776 (LWP 18558)] (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) 0x009ad402 in ?? ()
+ Trace 72335
Thread 1 (Thread -1208723776 (LWP 18558))
looks better, please install a gail/libgail debugging package as well
(In reply to comment #13) > looks better, please install a gail/libgail debugging package as well With gail/libgail debugging package - seems the same for me, where are gail calls? Backtrace was generated from '/usr/bin/meld' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208453440 (LWP 2822)] (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) 0x009ad402 in ?? ()
+ Trace 72340
Thread 1 (Thread -1208453440 (LWP 2822))
The crash occurs when calling gtk_tree_model_get_iter for a treemodel that has just successfully passed GTK_IS_TREE_MODEL, obtained from a GtkTreeView that passed GTK_IS_TREE_VIEW. Either GTK+ is at fault here, or some other data passed to gtk_tree_model_get_iter is bad. Possibly the 'path' is invalid or stale (though one might argue that GTK+ should not segv in this case)... Attaching a small patch that might help.
Created attachment 72802 [details] [review] possible fix for this issue?
Please check the above patch and see if it addresses the problem. I can't be sure, but it's possibly related.
Created attachment 72891 [details] gnome-panel crash with debugging symbols GNOME Panel crash with debugging symbols. I got this crash in Ubuntu box. Whenever I invoke at-poke gnome-panel will crash. I have also installed SLAB menu.
note that the trace from Comment #14 differs from the one in Comment #12
Comment on attachment 72891 [details] gnome-panel crash with debugging symbols looks like no debug symbols for libgail?
Bill: Installed all dbg packages, not sure, why there is no debugging symbols. Maybe once I get it, I will update this bug.
Nagappan, are you able to test the attached patch?
Bill, I haven't tried the patch. Let me update my CVS copy and will update this bug soon.
namaste nags, any news here? :-)
Hi Andre :) I'm unable to reproduce this bug with OpenSuSE 10.2. Maybe we can close this bug and If I'm able to reproduce, I will reopen this bug.
okay, thanks for the quick answer :-)
> Hi Andre :) > I'm unable to reproduce this bug with OpenSuSE 10.2. Maybe we can close this > bug and If I'm able to reproduce, I will reopen this bug. Please, leave it open for a while. I upgraded my system to Fedora Core 6 today and I still have this problem. It is 100% reproducable and I hope to find some time in coming month to investigate problem.
tomekem, if you can test the attached patch I would be grateful, it may solve your problem (I was awaiting feedback before putting the patch back)
Patch works! Thanks for help. I took sources for gail-1.9.2, applied your patch and copied new libgail.so to my system - now it's fine. I chcecked that your if-statement is called - in my case it was called 40 times. Do you need more help to find out what's wrong or you leave this fix as is?
*** Bug 391609 has been marked as a duplicate of this bug. ***