I think I got this bug. I upgraded to 16.04 because my update manager proposed that I do so. I first had a message that I should choose between lightdm and gdm3. I chose the default: lightdm. Then systemd failed to install, then (I don't know in what order) systemd-sysv lidpam-systemd gvfs-daemons gvfs gvfs-backends udisk2 nautilus gvfs-fuse policy-kit-1 ubuntu-system-service gnome-settings-daemon colord gnome-control-center gnome-bluetooth pulseaudio indicator-sound unity-control-center
By then, I feared that my installation was lost. I got a zillion more errors. At the end, I got a message that I might have a none-working system. So, instead of restarting, I did what some internet pages suggested: run the following in a terminal (and do what seems logical to do): apt-get -f install apt-get update apt-get upgrade (I think I repeated the series a few times, until no warnings were given anymore and all the work was done) Then I crossed my fingers and restarted,... and got a welcome screen and could login. This, however, was followed by some error messages and a dialogue which led me to this page, ultimately. So, I think my system works (despite all), but I'm not sure. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1560797 Title: apt does not configure Pre-Depends: before depending package Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Fix Released Status in apt source package in Wily: Fix Released Bug description: Happened during upgrade to 16.04, don't know any more details. -- SRU INFORMATION =============== Fix: https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=c75e60eb (applied in Xenial last week) Test case: - Install clean wily amd64 desktop + install libgcrypt20:i386 - change apt sources to xenial, apt-get dist-upgrade - with current apt, upgrade will often fail because systemd expects a configure libgcrypt20, or util-linux expects a configured libudev1 or similar, but these packages aren't configured. - with the fixed apt, the upgrade should run smoothly. Regression potential: Any bug here might potentially break package installation or upgrades completely. That said, the fix is quite obvious and has been in production in xenial for a week. Testing this SRU should include several dist-upgrades as well as some normal package installs in trusty/wily. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 225-1ubuntu9.1 Uname: Linux 4.4.5-040405-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 22 22:56:03 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2013-04-24 (1064 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.7 SourcePackage: systemd Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-03-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1560797/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
