empathy crashed with SIGABRT in raise()

Bug #945359 reported by Melissa
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
New
Undecided
Unassigned

Bug Description

Fresh install of Precise, empathy has crashed this same way 3 times already. This seems to happen after logging out and logging back in.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: empathy 3.3.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
ApportVersion: 1.94-0ubuntu1
Architecture: i386
Date: Fri Mar 2 22:38:14 2012
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
ProcCmdline: empathy
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: empathy
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /lib/i386-linux-gnu/libc.so.6
 __assert_fail () from /lib/i386-linux-gnu/libc.so.6
 _XAllocID () from /usr/lib/i386-linux-gnu/libX11.so.6
Title: empathy crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Melissa (mstrickland12) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #916000, 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.

visibility: private → public
visibility: private → public
tags: removed: need-i386-retrace
Revision history for this message
Bilal Shahid (s9iper1) wrote :

can you please provide the sttack trace in the upstream of master bug.. that would be a great job.
you can see https://live.gnome.org/GettingTraces/Details for the further details

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.