GNOME Bugzilla – Bug 631856
crash in Empathy: trying to connect to gta...
Last modified: 2011-03-29 16:13:26 UTC
Version: 2.32.0 What were you doing when the application crashed? trying to connect to gtalk Distribution: 3 Gnome Release: 2.32.0 2010-09-27 (Ubuntu) BugBuddy Version: 2.31.92 System: Linux 2.6.32-24-generic #43-Ubuntu SMP Thu Sep 16 14:58:24 UTC 2010 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10900000 Selinux: No Accessibility: Disabled GTK+ Theme: Ambiance Icon Theme: ubuntu-mono-dark GTK+ Modules: gnomesegvhandler, canberra-gtk-module Memory status: size: 511811584 vsize: 511811584 resident: 31051776 share: 21692416 rss: 31051776 rss_rlim: 18446744073709551615 CPU usage: start_time: 1286785871 rtime: 425 utime: 400 stime: 25 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/empathy' [Thread debugging using libthread_db enabled] [New Thread 0x7f48fe77f710 (LWP 6795)] 0x00007f490da476dd in __libc_waitpid (pid=6868, stat_loc=<value optimized out>, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 224099
Thread 1 (Thread 0x7f491289c960 (LWP 6790))
A debugging session is active. Inferior 1 [process 6790] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (19 sec old) --------------------- ** (gnome-session:2447): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2447): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2447): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2447): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2447): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2447): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2447): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2447): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2447): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2447): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2447): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2447): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2447): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2447): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged ** (gnome-session:2447): DEBUG: GsmDBusClient: obj_path=/org/freedesktop/DBus interface=org.freedesktop.DBus method=NameOwnerChanged --------------------------------------------------
*** Bug 631858 has been marked as a duplicate of this bug. ***
Any chance you could install telepathy-glib and folks debug packages, reproduce and post a better trace? Re-assigning to folks as it seems folks related.
(In reply to comment #2) > Any chance you could install telepathy-glib and folks debug packages, reproduce > and post a better trace? > > Re-assigning to folks as it seems folks related. Setting to NEEDINFO until we get a more-complete stack trace.
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!
*** Bug 635813 has been marked as a duplicate of this bug. ***
^^the last dup have a better trace^^
Shouldn't this be reopened since bug #635813 has a much better trace?
Yes, this should be reopened, but I don't think it can be fixed unless we get a valgrind log of the problem, since it's almost certainly being caused by memory corruption elsewhere. If you can reproduce the problem and get a valgrind memcheck log of it, please re-open this bug report and attach the log. Thanks!
Added fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=641532