update-manager crashed with SIGSEGV
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| update-manager (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
The Software Updater failed to get repository information the first time I ran it. When I clicked Retry, it crashed a short while later.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: update-manager 1:0.185
ProcVersionSign
Uname: Linux 3.8.0-14-generic x86_64
ApportVersion: 2.9.2-0ubuntu4
Architecture: amd64
Date: Tue Mar 26 11:38:12 2013
ExecutablePath: /usr/bin/
GsettingsChanges:
b'com.
b'com.
b'com.
b'com.
b'com.
InstallationDate: Installed on 2012-12-06 (110 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121205)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/bin/
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f49bec94aad: mov 0x8(%rax),%ecx
PC (0x7f49bec94aad) ok
source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: update-manager
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: update-manager crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo
| Christopher Kyle Horton (christhehorton) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-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 #1156442, 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.