update-manager crashed with SystemExit in exit(): 0
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| update-manager (Ubuntu) |
New
|
Medium
|
Unassigned | ||
Bug Description
update-manager crashed with SystemExit in exit(): 0
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: update-manager 1:0.190
ProcVersionSign
Uname: Linux 3.10.0-6-generic i686
NonfreeKernelMo
ApportVersion: 2.12-0ubuntu2
Architecture: i386
CrashCounter: 1
CurrentDmesg.txt:
[ 23.030248] ATL1E 0000:02:00.0 eth0: NIC Link is Up <100 Mbps Full Duplex>
[ 70.134604] usbcore: registered new interface driver snd-usb-audio
[ 70.185751] init: udev-fallback-
[ 70.327197] bio: create slab <bio-1> at 1
[ 70.536768] Adding 4192252k swap on /dev/mapper/
Date: Tue Aug 6 08:12:50 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/
ExecutableTimes
GsettingsChanges:
b'com.
b'com.
b'com.
b'com.
b'com.
InstallationDate: Installed on 2013-07-24 (12 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130721)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/bin/
ProcCwd: /home/ufo
PythonArgs: ['/usr/
SourcePackage: update-manager
Title: update-manager crashed with SystemExit in exit(): 0
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
| mario (mario-vidmar7) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| tags: | removed: need-duplicate-check |
| Changed in update-manager (Ubuntu): | |
| importance: | Undecided → Medium |
| information type: | Private → Public |
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 #1024590, 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.