wapport-gtk crashed with SIGABRT in raise()

Bug #936719 reported by o79
0
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
New
Undecided
Unassigned

Bug Description

After start-up appears such error

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: apport-gtk 1.91-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
NonfreeKernelModules: wl
ApportLog:
 ERROR: apport (pid 5705) Sun Feb 19 22:55:45 2012: called for pid 5668, signal 11
 ERROR: apport (pid 5705) Sun Feb 19 22:55:45 2012: executable: /usr/lib/chromium-browser/chromium-browser (command line "/usr/lib/chromium-browser/chromium-browser")
 ERROR: apport (pid 5705) Sun Feb 19 22:55:45 2012: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
 ERROR: apport (pid 5705) Sun Feb 19 22:55:49 2012: wrote report /var/crash/_usr_lib_chromium-browser_chromium-browser.1000.crash
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Sat Feb 18 00:34:44 2012
ExecutablePath: /usr/share/apport/apport-gtk
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120213)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gtk
Signal: 6
SourcePackage: apport
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
 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
Title: apport-gtk crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
o79 (o79) 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 #901675, 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
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.