apport-gtk crashed with SIGABRT in raise()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| apport (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I have this problem after upgrade from 12.10 to 13.10
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: apport-gtk 2.10.2-0ubuntu4
ProcVersionSign
Uname: Linux 3.10.0-2-generic i686
ApportLog:
ERROR: apport (pid 3982) Fri Jul 12 21:59:28 2013: called for pid 1950, signal 6, core limit 0
ERROR: apport (pid 3982) Fri Jul 12 21:59:28 2013: script: /usr/share/
ERROR: apport (pid 3982) Fri Jul 12 21:59:28 2013: debug: session gdbus call: (true,)
ERROR: apport (pid 3982) Fri Jul 12 21:59:55 2013: wrote report /var/crash/
ApportVersion: 2.10.2-0ubuntu4
Architecture: i386
Date: Fri Jul 12 21:59:28 2013
ExecutablePath: /usr/share/
InstallationDate: Installed on 2013-01-11 (182 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/share/
Signal: 6
SourcePackage: apport
StacktraceTop:
raise () from /lib/i386-
abort () from /lib/i386-
?? () from /lib/i386-
__assert_fail () from /lib/i386-
?? () from /usr/lib/
Title: apport-gtk crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to saucy on 2013-07-10 (2 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
| Raghuveer Gill (raghuveer-gill) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private Security → Public Security |
| tags: | removed: need-i386-retrace |
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 #1193828, 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.