Unable to upgrade to 11.10 using kpackagekit

Bug #873411 reported by Thorsteinn A. Malmjursson
52
This bug affects 12 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Fix Released
High
Unassigned
Oneiric
Won't Fix
High
Unassigned

Bug Description

I received an alert in my system tray to notify me that 11.10 had been released, so I clicked to open kpackagekit and undertook the dist-upgrade through there. Everything was running smoothly until I got to "Getting new software channels" - the system downloaded 104 packages, then proceeded to stop dead, informing me in a box that "Process exited with code 1".

The upgrade exited, returning me to kpackagekit, where I then discovered I had 1307 updates to process.

Revision history for this message
Thorsteinn A. Malmjursson (lightningstrike35) wrote :
Revision history for this message
Thorsteinn A. Malmjursson (lightningstrike35) wrote :
Revision history for this message
Thorsteinn A. Malmjursson (lightningstrike35) wrote :
Jonathan Riddell (jr)
affects: kpackagekit (Ubuntu) → update-manager (Ubuntu)
Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

Could you please attach your /etc/fstab to this file?

Changed in update-manager (Ubuntu):
status: New → In Progress
importance: Undecided → High
Revision history for this message
Michael Vogt (mvo) wrote :

Fix is commited to bzr, I will upload to -proposed soon.

Changed in update-manager (Ubuntu Oneiric):
status: New → In Progress
importance: Undecided → High
Revision history for this message
Clint Byrum (clint-fewbar) wrote : Please test proposed package

Hello Thorsteinn, or anyone else affected,

Accepted update-manager into oneiric-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in update-manager (Ubuntu Oneiric):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
Thorsteinn A. Malmjursson (lightningstrike35) wrote :

Apologies for the delay, as requested, a copy of my fstab.

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
/dev/sda1 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=1c28f680-1ea3-4f6c-a149-149228791f78 none swap sw 0 0
/dev/sdb1 /media/WORKHORSE ntfs errors=remount-ro 0 1 0 0

Revision history for this message
Gobnuts (gobnuts) wrote :

I got this as well.
Only in German :"Die Distributionsaktualisierung ist mit dem Code "1" beendet worden.", which is basically the same as "Process exited with code 1"

Will attach my main.log and apt.log

Revision history for this message
Gobnuts (gobnuts) wrote :
Revision history for this message
Migrus (migrus123) wrote :

Having the same error message (on Kubuntu).

After the failed upgrade, trying to use the KDE System Settings -> Software Updates fails with:
"ia32-libs: Recommends: ia32-libs-multiarch but it is not installable"
"Breaks: nspluginwrapper (< 1.4.4-0ubuntu2) but 1.2.2-0ubuntu9 is to be installed"

Instead I added oneric-proposed to the /etc/apt/sources.list as mentioned on the EnableProposed page and ran:
apt-get update
apt-get install update-manager-kde

This installs 1:0.152.25, no idea if that has the changes you wanted tested.

Still no luck, same error. Oh, look. apt has filled up my /var partition with old packages (disk full in exception in /var/log/dist-upgrade/main.log). Would be nice if the upgrade checked for available diskspace first as /var must have been almost full when I started.

Anyway, after making room and restarting it is now proceeding past the error. I didn't save my original logfiles so I can't be 100% certain it was the same problem, but for what it is worth it seems to work for me now.

See you on the other side.

Revision history for this message
Dan Hinojosa (dhinojosa) wrote :
Revision history for this message
Dan Hinojosa (dhinojosa) wrote :
Revision history for this message
Michael Vogt (mvo) wrote :

@Thorsteinn: Thanks for your fstab file. With the latest version of the release-upgrader it should be able to cope with your fstab now. Note that it has two additional values in the line: "/dev/sdb1 /media/WORKHORSE ntfs errors=remount-ro 0 1 0 0".

@Gobnuts: Thanks for your "main.log". This bug is a different one from the one reported here, it will only happen if a package gets marked downgrade which is rather unusual. Could you please file a new bug and attach your /etc/apt/preferences file and the files in /etc/apt/preferences.d to it please?

@Migrus: It should have saved the old logs under /var/log/dist-upgrade/$date, if you still have a failed one, that would be useful.

Thanks!
 Michael

Revision history for this message
Gobnuts (gobnuts) wrote :

@Michael Vogt (mvo): Thanks for your hints. I filed a new bug under
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/876379

Michael Vogt (mvo)
Changed in update-manager (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

@Michael, I see one remaining corner case, when the mount point name contains a '#'. In that case the fstab line is truncated and FstabEntry will fail with too few arguments.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package update-manager - 1:0.154

---------------
update-manager (1:0.154) precise; urgency=low

  * lp:~barcc/update-manager/all_changes-wrong-use:
    - Fixed wrong use of self.cache.all_changes[name] in
      UpdateManager.on_treeview_update_cursor_changed
  * data/gtkbuilder/UpdateManager.ui:
    - set default height to 500 (thanks to Sebastien Bacher)
  * DistUpgrade/DistUpgradeController.py:
    - do not crash if apt-btrfs-snapshot fails to run (LP: #873411)
  * UpdateManager/Core/MyCache.py, DistUpgrade/DistUpgradeCache.py:
    - honor dselect request install state when calcuating the upgrade
      thanks to Evan for suggesting this
  * merge fixes from oneiric-proposed
  * DistUpgrade/*
    - update for oneiric->precise upgrades
 -- Michael Vogt <email address hidden> Wed, 19 Oct 2011 16:21:16 +0200

Changed in update-manager (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Mika Väliviita (mika-valiviita-r) wrote :

Is there an easy way to use the updated update-manager on partly broken system (after the failed upgrade attempt)?

Revision history for this message
Matthias Brandt (mattelacchiato) wrote :

My system was "broken", too. I'm just running "do-release-upgrade -p" and it seems to work.

Maybe, i didn't need the "-p" switch. You have to see, what's working for you.

Martin Pitt (pitti)
tags: added: verification-donee
removed: verification-needed
tags: added: verification-done
removed: verification-donee
Revision history for this message
Rolf Leggewie (r0lf) wrote :

oneiric has seen the end of its life and is no longer receiving any updates. Marking the oneiric task for this ticket as "Won't Fix".

Changed in update-manager (Ubuntu Oneiric):
status: Fix Committed → Won't Fix
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.