update-manager crashed with signal 7

Bug #275425 reported by tdflanders
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

This crash happened while running the following command:

sudo apt-get -fy update ; sudo apt-get -fy upgrade ; sudo apt-get -fy dist-upgrade ; sudo apt-get -fy install ; sudo dpkg --configure -a ; sudo update-manager -c -d ; sudo synaptic

ProblemType: Crash
Architecture: i386
Disassembly: 0xb6a9fec9:
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/update-manager
InterpreterPath: /usr/bin/python2.5
Package: update-manager 1:0.93.17
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python2.5 /usr/bin/update-manager -c -d
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 7
SourcePackage: update-manager
Stacktrace:
 #0 0xb6a9fec9 in ?? ()
 #1 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
Title: update-manager crashed with signal 7
Uname: Linux 2.6.27-4-generic i686
UserGroups:

Revision history for this message
tdflanders (thomasdelbeke) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
tdflanders (thomasdelbeke) wrote :

thomas@thomas-laptop:~$ lsb_release -rd ; uname -a ; apt-cache policy linux apt dpkg synaptic update-manager network-manager gnome-terminal
Description: Ubuntu intrepid (development branch)
Release: 8.10
Linux thomas-laptop 2.6.27-4-generic #1 SMP Wed Sep 24 01:30:51 UTC 2008 i686 GNU/Linux
linux:
  Installed: (none)
  Candidate: 2.6.27.4.4
  Version table:
     2.6.27.4.4 0
        500 http://gb.archive.ubuntu.com intrepid/restricted Packages
apt:
  Installed: 0.7.14ubuntu6
  Candidate: 0.7.14ubuntu6
  Version table:
 *** 0.7.14ubuntu6 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
dpkg:
  Installed: 1.14.20ubuntu6
  Candidate: 1.14.20ubuntu6
  Version table:
 *** 1.14.20ubuntu6 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
synaptic:
  Installed: 0.62.1ubuntu9
  Candidate: 0.62.1ubuntu9
  Version table:
 *** 0.62.1ubuntu9 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
update-manager:
  Installed: 1:0.93.17
  Candidate: 1:0.93.17
  Version table:
 *** 1:0.93.17 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
network-manager:
  Installed: 0.7~~svn20080908t183521+eni0-0ubuntu4
  Candidate: 0.7~~svn20080908t183521+eni0-0ubuntu4
  Version table:
 *** 0.7~~svn20080908t183521+eni0-0ubuntu4 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
gnome-terminal:
  Installed: 2.24.0-0ubuntu1
  Candidate: 2.24.0-0ubuntu1
  Version table:
 *** 2.24.0-0ubuntu1 0
        500 http://gb.archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status
thomas@thomas-laptop:~$

Revision history for this message
tdflanders (thomasdelbeke) wrote :
Revision history for this message
arno_b (arno.b) wrote :

Thank for you report, but:
* can you reproduce the crash?
* can you try to get a backtrace by following the instructions on https://wiki.ubuntu.com/DebuggingProgramCrash and on http://live.gnome.org/GettingTraces/Details. Install packages 'update-manager-core-dbgsym' and 'gdb' and see here for backtrace https://wiki.ubuntu.com/Backtrace

I can't reproduce the crash on intrepid RC

update-manager:
  Installé : 1:0.93.32
  Candidat : 1:0.93.32
 Table de version :
 *** 1:0.93.32 0
        500 ftp://ftp.free.fr intrepid/main Packages
        100 /var/lib/dpkg/status

Marked as incomplete until we have a backtrace and more information.

Changed in update-manager:
status: New → Incomplete
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in update-manager:
status: Incomplete → Invalid
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.