GNOME Bugzilla – Bug 634848
empathy-2.32.0.1: tp_proxy_get_object_path: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV)
Last modified: 2010-12-31 03:20:55 UTC
Created attachment 174458 [details] Backtrace abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: empathy component: empathy crash_function: tp_proxy_get_object_path executable: /usr/bin/empathy kernel: 2.6.35.6-48.fc14.x86_64 package: empathy-2.32.0.1-3.fc14 rating: 4 reason: Process /usr/bin/empathy was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1289744004 uid: 500 Fedora Bug: https://bugzilla.redhat.com/show_bug.cgi?id=606094
paste here the attach bt [New Thread 27790] [New Thread 27793] Core was generated by `empathy'. Program terminated with signal 11, Segmentation fault.
+ Trace 224674
Thread 1 (Thread 27790)
Thanks for the bug. I looked at the code and didn't see any obvious reason why account would be NULL. Can you reproduce this crash? Any chance to get empathy logs before the crash?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!