GNOME Bugzilla – Bug 138885
Crashed after adding a buddy.
Last modified: 2005-10-05 16:03:51 UTC
Distribution: Fedora Core release 1 (Yarrow) Package: gossip Severity: normal Version: GNOME2.5.92 0.7.4 Gnome-Distributor: GNOME.Org Synopsis: Crashed after adding a buddy. Bugzilla-Product: gossip Bugzilla-Component: General Bugzilla-Version: 0.7.4 BugBuddy-GnomeVersion: 2.0 (2.5.92) Description: Description of the crash: I'ev added a buddy and he added me to it's list, afterwards he accidentally removed me from the list. While we were chatting i removed him from my list and added him again. After filling in the buddy details gossip crashed, also the window had the buddy in Unsorted group instead of adding him to the correct one. I don't know if any of this is related to the crash but anyways that was the only thing it was happening with gossip. Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? First time. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gossip' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -1084944256 (LWP 18409)] 0x00affc32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 45634
Thread 1 (Thread -1084944256 (LWP 18409))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-04-02 15:24 ------- Unknown version 0.7.4 in product gossip. Setting version to "0.7". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gossip". Setting to default milestone for this product, '---' Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Gossip crashed after I added a new buddy. It showed me the buddy in the contact list and in the correct group, just before I got the SIGSEGV dialog. I think I clicked on a buddy (a different one) before I got the crash, but I'm not entirely certain. Backtrace was generated from '/usr/bin/gossip' (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)...(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)...[New Thread 16384 (LWP 15074)] (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)...(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)... 0x40b33be8 in waitpid () from /lib/libpthread.so.0
+ Trace 51608
Thread 1 (Thread 16384 (LWP 15074))
I got a similair crash before, when I moved another buddy to the 'Buddies' group (instead of 'Unsorted'). I did not save the stack trace.
Reassigning to gail based on the stack trace (kick me if I'm wrong). Note that the only other stack trace that appears to contain gail_tree_view_ref_focus_cell() in the stack trace is bug 146836.
This happened again, after I added another buddy. This time I am sure that I did not click anywhere in the buddy list -- after the buddy was added and shown in the list, gossip crashed on its own. The traceback looks the same again -- gail_tree_view_ref_focus_cell in two threads.
I assume that you are running with the GCONF accessibility key /desktop/gnome./interface/accessibility enabled. What version of gail are you using?
some recent changes in gailtreeview may have impacted this bug positively. We haven't reproduced it ourselves, so we cannot confirm.
closing since there's no feedback on whether this bug is still live with CVS HEAD gail. Please reopen if you see the bug with cvs head gail.