GNOME Bugzilla – Bug 169987
Renaming group 'Unsorted'
Last modified: 2005-03-11 17:48:31 UTC
Distribution: Debian 3.1 Package: gossip Severity: normal Version: GNOME2.10.0 0.8 Gnome-Distributor: Ubuntu Synopsis: Renaming group 'Unsorted' Bugzilla-Product: gossip Bugzilla-Component: General Bugzilla-Version: 0.8 BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: When You add a new contact to your roster it's added to group 'unsorted'. I tried to rename that one and not to move contact through context menu. Steps to reproduce the crash: 1. Add a new contact to your roster. (I added transport via Psi a it was added to my roster in Gossip) 2. Rename group 'Unsorted' to other name like 'Transports'. Expected Results: That I have a new group named 'Transports'. How often does this happen? Everytime when I try it. Additional Information: I didn't try it with common contact (only with transports). Debugging Information: Backtrace was generated from '/usr/bin/gossip' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (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) [Thread debugging using libthread_db enabled] [New Thread -1221959552 (LWP 8251)] (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) 0xffffe410 in __kernel_vsyscall ()
+ Trace 56721
Thread 1 (Thread -1221959552 (LWP 8251))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-11 12:37 ------- Unknown version 0.8 in product gossip. Setting version to "unspecified". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gossip". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was freezing@adslink.cz. 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.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. Matches the stack trace in bug 168172, which has been marked as a duplicate of 155735. *** This bug has been marked as a duplicate of 155735 ***