Segfault at starting (probable cause :libindicate patch ) on kde
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Empathy |
Invalid
|
Critical
|
|||
empathy (Ubuntu) |
Fix Released
|
Medium
|
Ken VanDine |
Bug Description
I'm forwarding a bug from upstream.
https:/
Empathy has a segfault when starting. Here is the backtrace from gdb:
#0 0x0056e1e3 in g_type_
#1 0x0056a0b5 in g_signal_
#2 0x0806e6ea in empathy_
#3 0x005768cf in g_type_
#4 0x0055b6f8 in ?? () from /usr/lib/
#5 0x0806e47b in event_manager_
#6 0x0055c8ec in g_object_newv () from /usr/lib/
#7 0x0055d4ea in g_object_new_valist () from /usr/lib/
#8 0x0055d66e in g_object_new () from /usr/lib/
#9 0x0806e2bb in empathy_
#10 0x0807de46 in empathy_
#11 0x005768cf in g_type_
#12 0x0055b6f8 in ?? () from /usr/lib/
#13 0x0807dcfb in indicator_
#14 0x0055c8ec in g_object_newv () from /usr/lib/
#15 0x0055d4ea in g_object_new_valist () from /usr/lib/
#16 0x0055d66e in g_object_new () from /usr/lib/
#17 0x0807dbfb in empathy_
#18 0x08075beb in empathy_
#19 0x0805bac1 in main (argc=1, argv=0xbffff7f4) at empathy.c:868
As far as I tested bug impactes the version 2.28.0, but not the 2.27.* branch.
Remark 1 : this bug could be KDE-specific in the sense that I don't have the crash when I start Empathy in Gnome.
Remark 2 : when I launch Empathy in Valgrind, I don't have the problem. I attach the log of Valgrind (but it does not contains the segfault)
Changed in empathy (Ubuntu): | |
assignee: | nobody → Ken VanDine (ken-vandine) |
Changed in empathy: | |
importance: | Unknown → Critical |
status: | Unknown → Invalid |
I have to correct one statement : the Valgrind's log contains in fact some segfault. A friend who knows about read it and said me that the lines with "Invalid write of size 4" and "Invalid read of size 4" indicate the segfault. However, Empathy did not crashed during the Valgrind cession.
All my friends but me are developpers:)