software-center crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
software-center (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
1) xubuntu 12.10 i386 daily build 16 September 2012
2) software-center 5.3.13
3) I did not expect the software center to crash and kick me out of the desktop so I would have to log back in.
4)I had firefox open looking at xubuntu testcases, so the test case instructions said to install some apps I did. I was in the process of removing the default games in xubuntu and then the software center crashed. After the software center crashed I was kicked out of the desktop. I then had to log back in to the desktop. Both firefox and the software-center were closed at this point wit apport icon on the panel so I ended up in launchpad reporting a sofware-center crash.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: software-center 5.3.13
ProcVersionSign
Uname: Linux 3.5.0-14-generic i686
ApportVersion: 2.5.1-0ubuntu7
Architecture: i386
Date: Sun Sep 16 21:25:40 2012
ExecutablePath: /usr/share/
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120916)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: software-center
StacktraceTop:
raise () from /lib/i386-
abort () from /lib/i386-
?? () from /lib/i386-
__assert_fail () from /lib/i386-
_XAllocID () from /usr/lib/
Title: software-center crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #930823, 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.