apport-gtk crashed with SIGABRT in raise()

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

Bug Description

Erro con apport cuando intentaba reportar un bug en ubuntu 12.04

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: apport-gtk 1.91-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic i686
ApportLog:
 ERROR: apport (pid 577) Sun Feb 19 07:53:10 2012: called for pid 26273, signal 6
 ERROR: apport (pid 577) Sun Feb 19 07:53:10 2012: script: /usr/share/apport/apport-gtk, interpreted by /usr/bin/python2.7 (command line "/usr/bin/python /usr/share/apport/apport-gtk")
 ERROR: apport (pid 577) Sun Feb 19 07:53:10 2012: debug: session gdbus call: (true,)

 ERROR: apport (pid 577) Sun Feb 19 07:54:21 2012: wrote report /var/crash/_usr_share_apport_apport-gtk.1000.crash
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Sun Feb 19 07:53:10 2012
DuplicateOf: https://bugs.launchpad.net/bugs/931361
ExecutablePath: /usr/share/apport/apport-gtk
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gtk
ProcEnviron:
 LANGUAGE=es_VE:es
 PATH=(custom, no user)
 LANG=es_VE.UTF-8
 SHELL=/bin/bash
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: Upgraded to precise on 2012-02-19 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
psamuel (persaudsamuel) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

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

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.