empathy crashed with SIGSEGV in vfprintf()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
empathy (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: empathy
Emapthy Crashed after login
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: empathy 2.33.4-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
Date: Thu Mar 31 21:21:52 2011
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
ProcCmdline: empathy
ProcEnviron:
SHELL=/bin/bash
LC_MESSAGES=
LANGUAGE=en_IN:en
LANG=en_IN
SegvAnalysis:
Segfault happened at: 0x827dd6e <vfprintf+11278>: repnz scas %es:(%edi),%al
PC (0x0827dd6e) ok
source "%es:(%edi)" (0x0000007f) not located in a known VMA region (needed readable region)!
destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
vfprintf () from /lib/i386-
__vasprintf_chk () from /lib/i386-
g_vasprintf () from /lib/i386-
g_strdup_vprintf () from /lib/i386-
g_markup_
Title: empathy crashed with SIGSEGV in vfprintf()
UpgradeStatus: Upgraded to natty on 2011-03-26 (5 days ago)
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video
XsessionErrors:
(nautilus:1412): Gtk-WARNING **: Change Desktop Background: missing action Change Desktop Background
(nautilus:1412): Gtk-WARNING **: Ubuntu Documentation: missing action Ubuntu Documentation
(nautilus:1412): Gtk-WARNING **: Change Desktop Background: missing action Change Desktop Background
(nautilus:1412): Gtk-WARNING **: Ubuntu Documentation: missing action Ubuntu Documentation
(nautilus:1412): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #726173, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.