update-manager (crashed) Could not calculate the upgrade

Bug #185038 reported by miked
6
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

Could not calculate the upgrade

An unresolvable problem occurred while calculating the upgrade.

Please report this bug against the 'update-manager' package and include the files in /var/log/dist-upgrade/ in the bug report.
Fresh install of 7.10 live cd with 8.04 update manager -d with apt-get updates. restarted and added some more debugging files.

4 log files uploaded under bug
#84572
[apport] update-manager crashed with BadStatusLine in _read_status()

ProblemType: Crash
Architecture: i386
Date: Mon Jan 21 19:03:01 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/update-manager
InterpreterPath: /usr/bin/python2.5
Package: update-manager 1:0.87.2
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.5 /usr/bin/update-manager
ProcCwd: /root
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/update-manager']
SourcePackage: update-manager
Title: update-manager crashed with BadStatusLine in _read_status()
Uname: Linux HewittRand-desktop 2.6.24-4-generic #1 SMP Mon Jan 14 17:30:39 UTC 2008 i686 GNU/Linux

Revision history for this message
miked (miked11) wrote :
Revision history for this message
miked (miked11) wrote :
Revision history for this message
miked (miked11) wrote :
Revision history for this message
miked (miked11) wrote :

root@HewittRand-desktop:~# sudo apt-get install gdb
Reading package lists... Done
Building dependency tree
Reading state information... Done
gdb is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.
root@HewittRand-desktop:~# sudo gdb update-manager -d 2>&1 | tee gdb-update-manager -d.txt
tee: invalid option -- d
Try `tee --help' for more information.
root@HewittRand-desktop:~# sudo gdb <update-manager -d> 2>&1 | tee gdb-<update-manager -d>.txt
bash: syntax error near unexpected token `2'
root@HewittRand-desktop:~# sudo gdb update-manager 2>&1 | tee gdb-update-manager.txt
GNU gdb 6.7.1-debian
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
"/usr/bin/update-manager": not in executable format: File format not recognized
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program:
No executable file specified.
Use the "file" or "exec-file" command.
(gdb) backtrace full
No stack.
(gdb) info registers
The program has no registers now.
(gdb) thread apply all backtrace
No registers.
(gdb) quit
root@HewittRand-desktop:~#

Revision history for this message
miked (miked11) wrote :

https://wiki.ubuntu.com/DebuggingUpdateManager
[BOTTOM][TOP]How to file

When filing a bug report regarding a problem with a distribution or release upgrade you should add every file in '/var/log/dist-upgrade/', there should be at least 3, as separate attachments. You should also tag your distribution upgrade bug with the release you are moving from and to - for example 'feisty2gutsy'.

[TOP]Bug Tags

Tag

Use case

Link

feisty2gutsy

Bugs related to upgrading from Feisty Fawn to Gutsy Gibbon

[WWW] link

edgy2feisty

Bugs related to upgrading from Edgy Eft to Feisty Fawn

[WWW] link

dapper2edgy

Bugs related to upgrades from Dapper Drake to Edgy Eft

[WWW] link

cdrom-upgrade

Bugs related to an upgrade from CD-ROM or DVD media

[WWW] link

The previously described tags are specific to the UpdateManager application, if you need more general tags please visit Bugs/Tags page.

https://wiki.ubuntu.com/Bugs/Tags#preview
I need help adding tags that don't look like they exist yet. I don't quite understand how to edit that wiki-page either.
Thanks.

Revision history for this message
miked (miked11) wrote :

changed security from private to public

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.