GNOME Bugzilla – Bug 660571
Contact list crashes when choosing 'available' option (from empathy or gnome-shell)
Last modified: 2011-10-11 21:13:48 UTC
Starting program: /usr/bin/empathy [Thread debugging using libthread_db enabled] [New Thread 0x7fffdf315700 (LWP 14038)] [New Thread 0x7fffdeb14700 (LWP 14039)] [New Thread 0x7fffde313700 (LWP 14040)] [New Thread 0x7fffddb12700 (LWP 14041)] [New Thread 0x7fffdd311700 (LWP 14042)] [New Thread 0x7fffd33eb700 (LWP 14043)] [New Thread 0x7fffd144e700 (LWP 14047)] [New Thread 0x7fffd0c4d700 (LWP 14048)] [New Thread 0x7fffd044c700 (LWP 14049)] [New Thread 0x7fffcfc4b700 (LWP 14050)] [New Thread 0x7fffcf44a700 (LWP 14051)] [New Thread 0x7fffcec49700 (LWP 14052)] [New Thread 0x7fffce448700 (LWP 14053)] [New Thread 0x7fffcdc47700 (LWP 14054)] [New Thread 0x7fffcd446700 (LWP 14055)] [Thread 0x7fffcec49700 (LWP 14052) exited] [Thread 0x7fffd144e700 (LWP 14047) exited] [Thread 0x7fffcfc4b700 (LWP 14050) exited] [Thread 0x7fffcd446700 (LWP 14055) exited] [Thread 0x7fffcdc47700 (LWP 14054) exited] [Thread 0x7fffd0c4d700 (LWP 14048) exited] [Thread 0x7fffd044c700 (LWP 14049) exited] [Thread 0x7fffd33eb700 (LWP 14043) exited] [Thread 0x7fffcf44a700 (LWP 14051) exited] [Thread 0x7fffce448700 (LWP 14053) exited] [New Thread 0x7fffce448700 (LWP 14081)] [New Thread 0x7fffcf44a700 (LWP 14085)] [New Thread 0x7fffd044c700 (LWP 14086)] [New Thread 0x7fffd33eb700 (LWP 14087)] [New Thread 0x7fffd144e700 (LWP 14088)] [Thread 0x7fffd044c700 (LWP 14086) exited] [Thread 0x7fffd33eb700 (LWP 14087) exited] [Thread 0x7fffcf44a700 (LWP 14085) exited] [Thread 0x7fffce448700 (LWP 14081) exited] Program received signal SIGABRT, Aborted. 0x00007ffff07d28e5 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 64 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. in ../nptl/sysdeps/unix/sysv/linux/raise.c
+ Trace 228656
Thread 1 (Thread 0x7ffff7f81980 (LWP 14000))
Inferior 1 [process 14000] will be killed. Quit anyway? (y or n) Not confirmed. A debugging session is active.
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. *** This bug has been marked as a duplicate of bug 659022 ***