update-manager crashed with SIGSEGV in memset()

Bug #552112 reported by kyleabaker
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: update-manager

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu.
Description: Ubuntu lucid (development branch)
Release: 10.04

2) The version of the package you are using, via 'apt-cache policy packagename' or by checking in Synaptic.
update-manager:
  Installed: 1:0.133.9
  Candidate: 1:0.133.9
  Version table:
 *** 1:0.133.9 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

3) What you expected to happen
Start smoothly

4) What happened instead
Crashed on startup

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: update-manager 1:0.133.9
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Mar 30 18:30:11 2010
ExecutablePath: /usr/bin/update-manager
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.6 /usr/bin/update-manager --dist-upgrade
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f98e2b33cbf <memset+1183>: rep stos %rax,%es:(%rdi)
 PC (0x7f98e2b33cbf) ok
 source "%rax" ok
 destination "%es:(%rdi)" (0x7f18cc7ba000) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: update-manager
StacktraceTop:
 memset () from /lib/libc.so.6
 ?? ()
 ?? ()
 PyEval_EvalFrameEx ()
 PyEval_EvalCodeEx ()
Title: update-manager crashed with SIGSEGV in memset()
UserGroups:

Revision history for this message
kyleabaker (kyleabaker) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 memset () at ../sysdeps/x86_64/memset.S:674
 set_table_resize (so=0x1f69960,
 set_add (so=0x7f18cc7ba000, key=0x0)
 PyEval_EvalFrameEx (f=0x2a64ad0,
 PyEval_EvalCodeEx (co=0x1b5a8a0,

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in update-manager (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Daniel Hahler (blueyed)
visibility: private → public
Revision history for this message
Tim Casey (tjcasey) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates.

It would help us a lot if you could test a current, supported, Ubuntu version. If you test it, and it is still an issue, we would appreciate if you could upload updated logs by running the following command;

apport-collect 552112

We'd also appreciate you uploading the log files from '/var/log/dist-upgrade/' to this bug report as separate attachments.

Please let us know if you're not aware of how to do these tasks, and thanks again for helping us out.

Changed in update-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for update-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in update-manager (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.