Bug #254238 “update manager crashes on upgrade” : Bugs : update-manager package : Ubuntu

Revision history for this message

Sebastien Bacher (seb128) wrote on 2008-08-03:

#1

why do you think that's a gnome-utils bug? reassigning to update-manager

Revision history for this message

Ara Pulido (ara) wrote on 2008-08-04:

#2

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information. You may find it helpful to read "How
to report bugs effectively" [WWW]
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at [WWW]
http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).

Other information that might be useful:

1) The version of the brasero package you have installed (the output of "apt-cache policy update-manager" is good for this)
2) The output of running update-manger from a console.

Changed in update-manager:
importance:	Undecided → Critical
status:	New → Incomplete

Revision history for this message

Michael Vogt (mvo) wrote on 2008-08-11:

#3

Thanks for your bugreport.

Please attach the files in /var/log/dist-upgrade to this bugreport.
Thanks Michael

Revision history for this message

roger thomas (roger-thomas-100) wrote on 2008-08-11: dist-upgrade log

#4

apt.log Edit (61.4 KiB, text/x-log; name=apt.log; charset=UTF-8)

I have 'attached' file dist-upgrade. Hope it reaches you.Good luck
There was a message after distro upgrade that there was a database
crash.

Revision history for this message

roger thomas (roger-thomas-100) wrote on 2008-08-12:

#5

apt.log Edit (61.4 KiB, text/x-log; name=apt.log; charset=UTF-8)

Please find enclosed file var/log/dist-upgrade.There was a crash report
( Database crash) at end of Upgrade from Gutsy to Hardy.
Kind regards,Roger

Revision history for this message

tdflanders (thomasdelbeke) wrote on 2008-08-24:

#6

Hi, I upgrade several times to 8.10 so far with update-manager -d. I could not finish the upgrade becuase the display crashed and I had to use to soft reboot. After that I got no error report pop up, and when I ran update manager again, I could not upgrade completely, but I could do a partial upgrade. Mostly Intrepid was rendered to stable and I had to start over again. It always crashed when I was doing something CPU or ROM intensive, like trying to open DRM protected files with totem or something. The last time I upgraded, it also crashed, but I managed to get a working version, that still has display freezes from time to time, see my last bug report. It could be that this has nothing to do with this, in which case I apologize for spamming, but I tought I just give it a try. Cheers, Thomas .

Revision history for this message

roger thomas (roger-thomas-100) wrote on 2008-08-24: Re: [Bug 254238] Re: update manager crashes on upgrade

#7

Hi Thomas ,thanks for info - I think that there are 2 separate problems:
1)Update manager loops when it encounters errors in updates (it should
issue error warning or return to status-quo rather than looping)
2)Why are some 'updates' issued with errors in them ? Possibly one of
the library files is wrong.
Kind regards,Roger
> Hi, I upgrade several times to 8.10 so far with update-manager -d. I
> could not finish the upgrade becuase the display crashed and I had to
> use to soft reboot. After that I got no error report pop up, and when I
> ran update manager again, I could not upgrade completely, but I could do
> a partial upgrade. Mostly Intrepid was rendered to stable and I had to
> start over again. It always crashed when I was doing something CPU or
> ROM intensive, like trying to open DRM protected files with totem or
> something. The last time I upgraded, it also crashed, but I managed to
> get a working version, that still has display freezes from time to time,
> see my last bug report. It could be that this has nothing to do with
> this, in which case I apologize for spamming, but I tought I just give
> it a try. Cheers, Thomas .
>

Revision history for this message

tdflanders (thomasdelbeke) wrote on 2008-08-24:

#8

Download full text (3.8 KiB)

Yes,

thanks Roger. I don't know a lot about UNIX yet, but that could be the problem indeed for me. I remember that the last time I upgraded to Intrepid it also failed, and I was down to a partial upgrade again. I don't know a lot of commands in the terminal yet, so what I usually do is the following cycle:

$ sudo apt-get update
$ sudo apt-get upgrade
$ sudo apt-get dist-upgrade
$ sudo apt-get install -f
$ sudo dpkg --configure -a
$ sudo update-manager -d
$ sudo reboot

When I think I messed it up too much, I try to do:

$ sudo dpkg-reconfigure -a

I always kept getting the following message for one package, and when that was resolved I got the same message for another package:

$ sudo apt-get upgrade

0 newly installed, 0 upgraded, 0 removed, 1 not upgraded
The following package was held back:
"package name"

and also:

$ sudo apt-get update:

failed to fetch package "package-name"

When that happened I did:

$ sudo apt-get source "package-name"
$ sudo apt-get install "package-name"
$ sudo apt-get build-dep "package-name"
$ sudo dpkg-reconfigure "package-name"

followed by the above described commands, and kept on trucking.

Finally I ran into a package I could not get either way. So what I did instead was to run:

$ sudo synaptic

After that I tried fix broken packages and mark all upgrades. After that I clicked on repositories and changed the server from main server to UK server and finally to Ireland server (I live in Belfast). After that I clicked on reload in synaptic and tried fix broken packages and mark all upgrades again. Now the apply button turned green and I could download some new packages. After that I repeated my familiar ritual in the terminal. That is how I finally got a working configuration which is up to date. Therefore maybe I think you are right, there could be broken packages.

I will now try to repeat this by installing hardy on virtual box and upgrade it to Intrepid. I will try to document every step. If any of the devolopers have an idea, they should ask me about it. First I must go offline today however, as I need to put in another 2 GB ROM chip. My Vista Ultimate with Office 2007 Ultimate and Systran is to slow under Virtual Box 1.6.4. Nowing my own technical prawess, I could be offline for a long time, hehe.

Thanks again and cheers,

Thomas

----- Original Message ----
From: roger thomas <email address hidden>
To: <email address hidden>
Sent: Sunday, August 24, 2008 11:41:16 AM
Subject: Re: [Bug 254238] Re: update manager crashes on upgrade

Hi Thomas ,thanks for info - I think that there are 2 separate problems:
1)Update manager loops when it encounters errors in updates (it should
issue error warning or return to status-quo rather than looping)
2)Why are some 'updates' issued with errors in them ? Possibly one of
the library files is wrong.
Kind regards,Roger
> Hi, I upgrade several times to 8.10 so far with update-manager -d. I
> could not finish the upgrade becuase the display crashed and I had to
> use to soft reboot. After that I got no error report pop up, and when I
> ran update manager again, I could not upgrade completely, but I could do
> a partial upgrade. Mostly Intrepid was rendered ...

Yes,

thanks Roger. I don't know a lot about UNIX yet, but that could be the problem indeed for me. I remember that the last time I upgraded to Intrepid it also failed, and I was down to a partial upgrade again. I don't know a lot of commands in the terminal yet, so what I usually do is the following cycle:

$ sudo apt-get update
$ sudo apt-get upgrade
$ sudo apt-get dist-upgrade
$ sudo apt-get install -f
$ sudo dpkg --configure -a
$ sudo update-manager -d
$ sudo reboot

When I think I messed it up too much, I try to do:

$ sudo dpkg-reconfigure -a

I always kept getting the following message for one package, and when that was resolved I got the same message for another package:

$ sudo apt-get upgrade

0 newly installed, 0 upgraded, 0 removed, 1 not upgraded
The following package was held back:
"package name"

and also:

$ sudo apt-get update:

failed to fetch package "package-name"

When that happened I did:

$ sudo apt-get source "package-name"
$ sudo apt-get install "package-name"
$ sudo apt-get build-dep "package-name"
$ sudo dpkg-reconfigure "package-name"

followed by the above described commands, and kept on trucking.

Finally I ran into a package I could not get either way. So what I did instead was to run:

$ sudo synaptic

After that I tried fix broken packages and mark all upgrades. After that I clicked on repositories and changed the server from main server to UK server and finally to Ireland server (I live in Belfast). After that I clicked on reload in synaptic and tried fix broken packages and mark all upgrades again. Now the apply button turned green and I could download some new packages. After that I repeated my familiar ritual in the terminal. That is how I finally got a working configuration which is up to date. Therefore maybe I think you are right, there could be broken packages.

I will now try to repeat this by installing hardy on virtual box and upgrade it to Intrepid. I will try to document every step. If any of the devolopers have an idea, they should ask me about it. First I must go offline today however, as I need to put in another 2 GB ROM chip. My Vista Ultimate with Office 2007 Ultimate and Systran is to slow under Virtual Box 1.6.4. Nowing my own technical prawess, I could be offline for a long time, hehe.

Thanks again and cheers,

Thomas

----- Original Message ----
From: roger thomas <roger.thomas-100@ntlworld.com>
To: thomasdelbeke@yahoo.com
Sent: Sunday, August 24, 2008 11:41:16 AM
Subject: Re: [Bug 254238] Re: update manager crashes on upgrade

Hi Thomas ,thanks for info - I think that there are 2 separate problems:
1)Update manager loops when it encounters errors in updates (it should
issue error warning or return to status-quo rather than looping)
2)Why are some 'updates' issued with errors in them ? Possibly one of
the library files is wrong.
Kind regards,Roger
> Hi, I upgrade several times to 8.10 so far with update-manager -d. I
> could not finish the upgrade becuase the display crashed and I had to
> use to soft reboot. After that I got no error report pop up, and when I
> ran update manager again, I could not upgrade completely, but I could do
> a partial upgrade. Mostly Intrepid was rendered to stable and I had to
> start over again. It always crashed when I was doing something CPU or
> ROM intensive, like trying to open DRM protected files with totem or
> something. The last time I upgraded, it also crashed, but I managed to
> get a working version, that still has display freezes from time to time,
> see my last bug report. It could be that this has nothing to do with
> this, in which case I apologize for spamming, but I tought I just give
> it a try. Cheers, Thomas .
>

-- 
update manager crashes on upgrade
https://bugs.launchpad.net/bugs/254238
You received this bug notification because you are a direct subscriber
of the bug.

Revision history for this message

Ed Sherry (esoldfuz004) wrote on 2008-08-29:

#9

Sorry don't understand all the terms used above but on the last updates sent(around 8-20-08) . My update manger came up with a error message: error message occured message said E: dpkg was interrupted,you must manually run 'dpkg--configure-a'correct problem E_cache->open () failed,please report--- This locked up computer and update failed requiring a reboot to start back up-- now update manger is locked with the above message message and appears to be stuck with this error message appearing whenever update manger is opened I'm using a updated version 7.1 to 8.04

Revision history for this message

roger thomas (roger-thomas-100) wrote on 2008-08-29:

#10

This bug seems to be related to (and partly caused by) bug #253462

Revision history for this message

tdflanders (thomasdelbeke) wrote on 2008-09-09:

#11

Update-manager-c-d-1.png Edit (158.1 KiB, image/png)

Hi there,

once again: I cannot confirm this bug at the moment, as I cannot get VBox-2.0 to work under 8.10-alfa-5. I hope this will change soon. Hopefully these slides I had stored can give you some info. Cheers, Thomas.

Revision history for this message

tdflanders (thomasdelbeke) wrote on 2008-09-09:

#12

Update-manager-c-d-2.png Edit (74.4 KiB, image/png)

Revision history for this message

tdflanders (thomasdelbeke) wrote on 2008-09-30:

#13

Download full text (5.6 KiB)

Your mail to 'launchpad-users' with the subject

feedback

Is being held until the list moderator can review it for approval.

The reason it is being held:

Post to moderated list

Either the message will get posted to the list, or you will receive
notification of the moderator's decision. If you would like to cancel
this posting, please visit the following URL:

https://lists.ubuntu.com/mailman/confirm/launchpad-users/f104883df70e01b653d6db90a22d81685b686ecd

Bad confirmation string
Invalid confirmation string: f104883df70e01b653d6db90a22d81685b686ecd.

Note that confirmation strings expire approximately 3 days after the initial subscription request. If your confirmation has expired, please try to re-submit your subscription. Otherwise, re-enter your confirmation string.
launchpad-users list run by kiko at async.com.br, matthew.revell at canonical.com, joey at canonical.com
launchpad-users administrative interface (requires authorization)
Overview of all lists.canonical.com mailing lists

Delivered by Mailman
version 2.1.8 Python Powered Gnu's Not Unix

Hi there,

I am going to stop reporting bug reports for now, as you people will not read them anyway.

I have confirmed with the help of canonical support that the laptop I am using has no defective hardware. The BIOS is not broke, since I have reflashed the BIOS with an upgraded version, from the Acer website. For the few bugs I could easily reproduce this does not change a thing. What we have found out is that the BIOS developed by the Phoenix people for Acer, does not support 4 GB. Acer claims that the system supports 4 GB, but the people from Phoenix must have limited the BIOS to 3 GB, since it was made for use with Windows 32-bit. The system has two identical sodim sockets and I have two identical 2 GB chips, that were sold to me fully installed by an official eBay reseller. I have tested both sockets and both chips by memtest86+ 1.65 1.70 and 2.01. Everything came up clean except the alfa 5 2.01 test, which had a bug, but is now fixed. I had a problem before when trying to upgrade to Vista Ultimate, as the 32-bit only recognises 3 GB. Back then a faulty memtest86+ test surfaced. I have the memtest86+ version in backup, but it is preinstalled and backed up with Windows Live OneCare and I have no idea how to determine the version number. Really it does not change anything, as when I remove one of the chips, the same bugs seem to persist. That is, the ones that are easily reproducible. I now get less crashes both due to the fact that I now only run Ubuntu repositories, other than VirtualBox 2.0.2 and Skype-debian as described in the community docs, as well as alfa 6 and maybe also because I only use 2 GB and the BIOS update. I do use many multiverse and restricted applications though.

I maybe still able to help with the following data:

My AptonCD bug persists. Only faster since I now use only 2 GB RAM. I have tracked and described this behaviour with gnome-system-monitor and Valgrind log several weeks ago, but Tormod would not look into it since he suspected hardware failure. The problem is there that APTonCD writes everything away to the RAM chip(s) and crashes when...

Your mail to 'launchpad-users' with the subject

feedback

Is being held until the list moderator can review it for approval.

The reason it is being held:

Post to moderated list

Either the message will get posted to the list, or you will receive
notification of the moderator's decision.  If you would like to cancel
this posting, please visit the following URL:

https://lists.ubuntu.com/mailman/confirm/launchpad-users/f104883df70e01b653d6db90a22d81685b686ecd

Bad confirmation string
Invalid confirmation string: f104883df70e01b653d6db90a22d81685b686ecd.

Note that confirmation strings expire approximately 3 days after the initial subscription request. If your confirmation has expired, please try to re-submit your subscription. Otherwise, re-enter your confirmation string.
launchpad-users list run by kiko at async.com.br, matthew.revell at canonical.com, joey at canonical.com
launchpad-users administrative interface (requires authorization)
Overview of all lists.canonical.com mailing lists

Delivered by Mailman
version 2.1.8     Python Powered     Gnu's Not Unix

Hi there,

I am going to stop reporting bug reports for now, as you people will not read them anyway.

I have confirmed with the help of canonical support that the laptop I am using has no defective hardware. The BIOS is not broke, since I have reflashed the BIOS with an upgraded version, from the Acer website. For the few bugs I could easily reproduce this does not change a thing. What we have found out is that the BIOS developed by the Phoenix people for Acer, does not support 4 GB. Acer claims that the system supports 4 GB, but the people from Phoenix must have limited the BIOS to 3 GB, since it was made for use with Windows 32-bit. The system has two identical sodim sockets and I have two identical 2 GB chips, that were sold to me fully installed by an official eBay reseller. I have tested both sockets and both chips by memtest86+ 1.65 1.70 and 2.01. Everything came up clean except the alfa 5 2.01 test, which had a bug, but is now fixed. I had a problem before when trying to upgrade to Vista Ultimate, as the 32-bit only recognises 3 GB. Back then a faulty memtest86+ test surfaced. I have the memtest86+ version in backup, but it is preinstalled and backed up with Windows Live OneCare and I have no idea how to determine the version number. Really it does not change anything, as when I remove one of the chips, the same bugs seem to persist. That is, the ones that are easily reproducible. I now get less crashes both due to the fact that I now only run Ubuntu repositories, other than VirtualBox 2.0.2 and Skype-debian as described in the community docs, as well as alfa 6 and maybe also because I only use 2 GB and the BIOS update. I do use many multiverse and restricted applications though.

I maybe still able to help with the following data:

My AptonCD bug persists. Only faster since I now use only 2 GB RAM. I have tracked and described this behaviour with gnome-system-monitor and Valgrind log several weeks ago, but Tormod would not look into it since he suspected hardware failure. The problem is there that APTonCD writes everything away to the RAM chip(s) and crashes when they are full, without utilising the  2 GB swap I have.

The gvfs trash bug I reported as new because of a different title was actually caused by opening different applications with nautilus, it gave a wastebin popup and all other stuff, nautilus and firefox include just crashed. It also occured sometimes on startup, but since I keep my wastebin empty and with all the updates it stopped happening. Maybe some people don't know how to solve their wastebin permissions issue.

The consolekit bug resurfaced only once, during an upgrade of hardy to the latest 8.10 alfa. I tried to open a deluge torrent video file that had not ended downloading fully, I got a freeze up and a fatal system crash requiring reinstall. I could not rescue the system since HAL had not finished installing. I noted however an error message in the terminal pointing out a console kit conflict. I have copied it manually, but it is rather long. Just ask if you need it. I think I installed X kernel or core dump through synaptic and I have backed up var and etc, but I do not know how to use that. I asked for feedback on this earlier but have not received it.

The landscape bug that is still open (sysinfo) may be reproducible. I had my landscape account open in a firefox tap. I ran '$ sudo dpkg-reconfigure -aup low'. When I got to landscape config I accidentally pressed yes, yes and did not fill in username and password. Then it crashed.

I also asked for help on how to find my bug reports that were closed down as invalid, to recover my comments. Tormod said I should activate something in the GUI, but has not tolled me how to.

Canonical asked me specifically not to Google for stress testing tools and try them out, since if it crashes something the will have to provide assistance for that too. They wanted to search for suitable tools for this in main, but I agreed that I should not use up their time for that since I do not have any major problems in hardy.

I have spent a lot of time on trying to reflash the BIOS, since my Freedos live cd displayed an error code and the RedHat flashrom tool would not work and such. Anyway, I found it was easier and faster for me to format the entire disk to ntfs and relash from Windows, as I had to reformat anyway.

I have not a lot of time available anymore since the holidays are over, so ask me in first person if you need to know something or give me instructions on how to recover my closed reports first, or I will have to let everything time out.

Thank you for helping make Ubunu better,

Thomas

Revision history for this message

tdflanders (thomasdelbeke) wrote on 2008-10-04:

#14

Hi Sebastien,

I have upgraded from 8.04 to 8.10 beta. I had one mor crash, but asymtomatic. You can close this down for my part.

Revision history for this message

tdflanders (thomasdelbeke) wrote on 2008-10-09:

#15

Hi there,

this is the terminal output from trying to rescue my system after yet another fatal system crash. This actually happened several weeks ago. I had asked on the launchpad digest mail list what to do with this, but I did not receive a reply yet. Probably this was because of the works on the launchpad system. The crash happened while upgrading from Hardy to Intrepid (then alfa 4 or 5) with '$ sudo update-manager -c -d'. I post this here and on bug # 269651, before opening another bug report. I copied this meticulously on the envelop from my bank statements. I just retrieved it while cleaning the room.

Cheers,

Thomas

thomas@thomas:~$ sudo dpkg-reconfigure hal
Failed to open connection to system message bus: Failed to connect to socket /var/run/dbus/system_bus_socket:
Connection refused
invoke-rc.d: initscript dbus, action "force-reload" failed.
polkit-auth: This operation requires the system message bus and Consolekit to be running
/usr/lib/policykit/polkit-read-auth-helper: symbol
lookup error: /usr/lib/policykit/polkit-read-auth-helper:
undefined symbol: kit-getpwnam
polkit-auth: Not Authorized To Read Authorizations For Other Users:
uid 0 is not authorized to read authorizations for uid 111
(requires org.freedesktop.policykit.read)
thomas@thomas-laptop:~$
update-rc.d: warning: multiuser is deprecated ; specify runlevels manually

Revision history for this message

roger thomas (roger-thomas-100) wrote on 2008-10-21:

#16

The problems have been solved by the mass updates to 8.04 on 15th & 16th October.
Best wishes,Roger

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2008-11-20:

#17

hi Roger, thank you for your feedback. We are closing this report due to your last comment regarding this being fixed with an update. The original issue looked like something between apt-listbugs and update-manager.

Thanks you for your time and don't hesitate to submit any new bug.

Changed in update-manager:
status:	Incomplete → Fix Released

Revision history for this message

tdflanders (thomasdelbeke) wrote on 2008-11-23:

#18

.xsession-errors Edit (12.6 KiB, text/plain)

Hi,

I have no idea whether this is the same bug, but I have very similar symptoms while upgradin to Jaunty:

thomas@ubuntu:~$ lsb_release -rd ; uname -a ; apt-cache policy linux update-manager gdb apport-gtk VirtualBox gnome-terminal ; hwinfo > hwinfo_log
Description: Ubuntu 8.10
Release: 8.10
Linux ubuntu 2.6.27-8-generic #1 SMP Thu Nov 6 17:33:54 UTC 2008 i686 GNU/Linux
linux:
  Installed: 2.6.27.8.12
  Candidate: 2.6.27.8.12
  Version table:
*** 2.6.27.8.12 0
        500 http://archive.ubuntu.com intrepid-proposed/restricted Packages
        100 /var/lib/dpkg/status
     2.6.27.7.11 0
        500 http://archive.ubuntu.com intrepid/restricted Packages
        500 cdrom://Ubuntu 8.10 _Intrepid Ibex_ - Release i386 (20081028) intrepid/restricted Packages
update-manager:
  Installed: 1:0.93.35
  Candidate: 1:0.93.35
  Version table:
*** 1:0.93.35 0
        500 http://archive.ubuntu.com intrepid-proposed/main Packages
        100 /var/lib/dpkg/status
     1:0.93.34 0
        500 http://archive.ubuntu.com intrepid-updates/main Packages
     1:0.93.32 0
        500 http://archive.ubuntu.com intrepid/main Packages
        500 cdrom://Ubuntu 8.10 _Intrepid Ibex_ - Release i386 (20081028) intrepid/main Packages
gdb:
  Installed: 6.8-3ubuntu2
  Candidate: 6.8-3ubuntu2
  Version table:
*** 6.8-3ubuntu2 0
        500 http://archive.ubuntu.com intrepid/main Packages
        500 cdrom://Ubuntu 8.10 _Intrepid Ibex_ - Release i386 (20081028) intrepid/main Packages
        100 /var/lib/dpkg/status
apport-gtk:
  Installed: 0.119
  Candidate: 0.119
  Version table:
*** 0.119 0
        500 http://archive.ubuntu.com intrepid/main Packages
        500 cdrom://Ubuntu 8.10 _Intrepid Ibex_ - Release i386 (20081028) intrepid/main Packages
        100 /var/lib/dpkg/status
gnome-terminal:
  Installed: 2.24.1.1-0ubuntu1
  Candidate: 2.24.1.1-0ubuntu1
  Version table:
*** 2.24.1.1-0ubuntu1 0
        500 http://archive.ubuntu.com intrepid-updates/main Packages
        100 /var/lib/dpkg/status
     2.24.1-0ubuntu1 0
        500 http://archive.ubuntu.com intrepid/main Packages
        500 cdrom://Ubuntu 8.10 _Intrepid Ibex_ - Release i386 (20081028) intrepid/main Packages
W: Unable to locate package VirtualBox
thomas@ubuntu:~$

Hi,

I have no idea whether this is the same bug, but I have very similar symptoms while upgradin to Jaunty:

thomas@ubuntu:~$ lsb_release -rd ; uname -a ; apt-cache policy linux update-manager gdb apport-gtk VirtualBox gnome-terminal ; hwinfo > hwinfo_log
Description:	Ubuntu 8.10
Release:	8.10
Linux ubuntu 2.6.27-8-generic #1 SMP Thu Nov 6 17:33:54 UTC 2008 i686 GNU/Linux
linux:
  Installed: 2.6.27.8.12
  Candidate: 2.6.27.8.12
  Version table:
 *** 2.6.27.8.12 0
        500 http://archive.ubuntu.com intrepid-proposed/restricted Packages
        100 /var/lib/dpkg/status
     2.6.27.7.11 0
        500 http://archive.ubuntu.com intrepid/restricted Packages
        500 cdrom://Ubuntu 8.10 _Intrepid Ibex_ - Release i386 (20081028) intrepid/restricted Packages
update-manager:
  Installed: 1:0.93.35
  Candidate: 1:0.93.35
  Version table:
 *** 1:0.93.35 0
        500 http://archive.ubuntu.com intrepid-proposed/main Packages
        100 /var/lib/dpkg/status
     1:0.93.34 0
        500 http://archive.ubuntu.com intrepid-updates/main Packages
     1:0.93.32 0
        500 http://archive.ubuntu.com intrepid/main Packages
        500 cdrom://Ubuntu 8.10 _Intrepid Ibex_ - Release i386 (20081028) intrepid/main Packages
gdb:
  Installed: 6.8-3ubuntu2
  Candidate: 6.8-3ubuntu2
  Version table:
 *** 6.8-3ubuntu2 0
        500 http://archive.ubuntu.com intrepid/main Packages
        500 cdrom://Ubuntu 8.10 _Intrepid Ibex_ - Release i386 (20081028) intrepid/main Packages
        100 /var/lib/dpkg/status
apport-gtk:
  Installed: 0.119
  Candidate: 0.119
  Version table:
 *** 0.119 0
        500 http://archive.ubuntu.com intrepid/main Packages
        500 cdrom://Ubuntu 8.10 _Intrepid Ibex_ - Release i386 (20081028) intrepid/main Packages
        100 /var/lib/dpkg/status
gnome-terminal:
  Installed: 2.24.1.1-0ubuntu1
  Candidate: 2.24.1.1-0ubuntu1
  Version table:
 *** 2.24.1.1-0ubuntu1 0
        500 http://archive.ubuntu.com intrepid-updates/main Packages
        100 /var/lib/dpkg/status
     2.24.1-0ubuntu1 0
        500 http://archive.ubuntu.com intrepid/main Packages
        500 cdrom://Ubuntu 8.10 _Intrepid Ibex_ - Release i386 (20081028) intrepid/main Packages
W: Unable to locate package VirtualBox
thomas@ubuntu:~$

Revision history for this message

tdflanders (thomasdelbeke) wrote on 2008-11-23:

#19

hwinfo_log Edit (228.1 KiB, text/plain)

Revision history for this message

tdflanders (thomasdelbeke) wrote on 2008-11-23:

#20

gdb-update-manager.txt Edit (22.2 KiB, text/plain)

Revision history for this message

tdflanders (thomasdelbeke) wrote on 2008-11-23:

#21

gdb-update-manager-2.txt Edit (20.4 KiB, text/plain)

Revision history for this message

tdflanders (thomasdelbeke) wrote on 2008-11-23:

#22

debug Edit (31.2 KiB, text/plain)

Revision history for this message

tdflanders (thomasdelbeke) wrote on 2013-06-19: FW: thomas delbeke

#23

http://alparslanparlak.com/op/pgm/fhpygl/rhnsgx/yycx/vbeet.html
thomas delbeke
opuem/div>

Revision history for this message

tdflanders (thomasdelbeke) wrote on 2018-05-21:

#24

http://mission.itafaji.com

Thomas Delbeke

Ubuntu
update-manager package

update manager crashes on upgrade

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntuupdate-manager package

update manager crashes on upgrade

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
update-manager package