update manager failed check after 12.04 upgrade
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| bzr-gtk (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
immediately after upgrading from 11.10 to 12.04 beta, opened update manager and ran a check for new updates.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bzr-gtk 0.103.0+bzr769-1
ProcVersionSign
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelMo
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
Date: Thu Mar 1 21:56:20 2012
ExecutablePath: /usr/bin/bzr-notify
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/bzr-notify
SegvAnalysis:
Segfault happened at: 0x7f3f39e6c71b <vfprintf+155>: callq 0x7f3f39eb5a20 <strchrnul>
PC (0x7f3f39e6c71b) ok
source "0x7f3f39eb5a20" (0x7f3f39eb5a20) ok
destination "(%rsp)" (0x7fffd4d90fc0) not located in a known VMA region (needed writable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: bzr-gtk
StacktraceTop:
g_type_get_qdata () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: bzr-notify crashed with SIGSEGV in g_type_get_qdata()
UpgradeStatus: Upgraded to precise on 2012-03-02 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
| Lon (lonhutt) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| visibility: | 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 #903444, 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.