** Changed in: empathy
Status: Unknown = Invalid
** Changed in: empathy
Importance: Unknown = Critical
--
Segfault at starting (probable cause :libindicate patch ) on kde
https://bugs.launchpad.net/bugs/435262
You received this bug notification because you are a member of Ubuntu
Bugs,
reported said that this bug can't be reproduced now.
** Changed in: empathy (Ubuntu)
Status: New = Fix Released
--
Segfault at starting (probable cause :libindicate patch ) on kde
https://bugs.launchpad.net/bugs/435262
You received this bug notification because you are a member of Ubuntu
** Changed in: empathy (Ubuntu)
Assignee: (unassigned) = Ken VanDine (ken-vandine)
--
Segfault at starting (probable cause :libindicate patch ) on kde
https://bugs.launchpad.net/bugs/435262
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
and your brother too :p
** Changed in: empathy (Ubuntu)
Importance: Undecided = Medium
** Bug watch added: GNOME Bug Tracker #595980
http://bugzilla.gnome.org/show_bug.cgi?id=595980
** Also affects: empathy via
http://bugzilla.gnome.org/show_bug.cgi?id=595980
Importance: Unknown
I think you should also say that this segfault happens on kde
** Summary changed:
- Segfault at starting (probable cause :libindicate patch )
+ Segfault at starting (probable cause :libindicate patch ) on kde
--
Segfault at starting (probable cause :libindicate patch ) on kde
** Attachment added: Valgrind's log.
http://launchpadlibrarian.net/32310716/valgrind.log
--
Segfault at starting (probable cause :libindicate patch )
https://bugs.launchpad.net/bugs/435262
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
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
