After upgrade 12.04 -> 14.04 there was no display manager (kdm or lightdm)

Bug #1264887 reported by Nils Kassube
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Fix Released
High
Harald Sitter
Trusty
Fix Released
High
Harald Sitter

Bug Description

This Kubuntu machine had KDM installed before the upgrade from 12.04 to 14.04. After the upgrade there was no display manager left, i.e. kdm was no longer installed and it wasn't replaced by lightdm like it happened on another machine with a fresh Kubuntu 12.04 system.

The upgrade should either keep KDM or replace it by lightdm, but it should not leave the system in a state without display manager.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-release-upgrader-core 1:0.209
ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
Uname: Linux 3.12.0-7-generic x86_64
ApportVersion: 2.12.7-0ubuntu3
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Sun Dec 29 22:35:03 2013
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to trusty on 2013-12-29 (0 days ago)
VarLogDistupgradeTermlog:

Related branches

Revision history for this message
Nils Kassube (kassube) wrote :
Paul White (paulw2u)
tags: added: kubuntu
Revision history for this message
Nils Kassube (kassube) wrote :

Additional info: The KDE packages of the 12.04 system were from the kubuntu-backports-ppa.

Revision history for this message
Harald Sitter (apachelogger) wrote :

kubuntu-desktop was not installed.

Revision history for this message
Harald Sitter (apachelogger) wrote :

Well, random guess of the day: lightdm was not installed during the upgrade because kubuntu-desktop was not present (thus no dependency tie to lightm) and kdm was removed in the post-upgrade cleanup either because there were no dependency chains to in anymore or there is special magic that marked kdm for removal (probably latter I am guessing).

Revision history for this message
Harald Sitter (apachelogger) wrote :

Other random comment: I was under the impression that update-manager will try to figure out which desktop package to force into the installation in case none is installed, so technically this should not have happend... however there is no indication of any such business in the logs... this probably needs to be reproduced in an equal environment.

Changed in ubuntu-release-upgrader (Ubuntu):
milestone: none → ubuntu-14.04-alpha-2
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Nils Kassube (kassube) wrote :

Indeed I don't have kubuntu-desktop installed because I removed one (or more) of it's dependencies a long time ago. I think this is not uncommon, though. At the end of the upgrade I didn't let upgrade-manager clean up unused packages, therefore the reason for the removal of kdm seems to be something else.

For this upgrade test I made a copy of my main system to an extra partition and therefore I can try the upgrade again to verify if a possible fix works.

Revision history for this message
Harald Sitter (apachelogger) wrote :

Oh, that is handy xD

Just to be sure though, you did not get any query asking you whether *-desktop should be installed?

Revision history for this message
Nils Kassube (kassube) wrote :

No, there was no such question.

Revision history for this message
Brian Murray (brian-murray) wrote :

From the logs we can see the following:

2013-12-29 11:16:30,144 DEBUG need_server_mode(): can not find a desktop meta package or key deps, running in server mode
2013-12-29 11:16:30,144 DEBUG checkViewDepends()

Revision history for this message
Brian Murray (brian-murray) wrote :

Looking at the ubuntu-release-upgrader code we see the following:

        for key in metapkgs:
            # if it is installed we are done
            if key in self and self[key].is_installed:
                logging.debug("need_server_mode(): run in 'desktop' mode, (because of pkg '%s')" % key)
                return False
            # if it is not installed, but its key depends are installed
            # we are done too (we auto-select the package later)
            deps_found = True
            for pkg in self.config.getlist(key, "KeyDependencies"):
                deps_found &= pkg in self and self[pkg].is_installed

KeyDependencies for kubuntu-desktop are:

[kubuntu-desktop]
KeyDependencies=kdm, kubuntu-artwork

Are there some other packages that should be added?

Revision history for this message
Nils Kassube (kassube) wrote :

Obviously the keydependencies have not been found even though kdm was installed. Or is it required to find both (all) keydependencies? Then the explanation would be that kubuntu-artwork seems not to be available from the kubuntu-backports-ppa and therefore wasn't installed.

Would it help if I send a list of the installed packages from before the upgrade?

I made some more experiments. I used the default installation of Kubuntu 12.04 and then upgraded to the kubuntu-backports-ppa. Then I upgraded to 14.04 and the result was that lightdm was installed, no matter if kubuntu-desktop was installed or not.

Then I removed the other packages which were not installed on the system which produced the bug in question. The result of the upgrade to 14.04 was that kdm was removed and lightdm was not installed. I had a closer look at the packages and found that ubuntu-minimal and ubuntu-standard were not installed, so I repeated the experiment with these packages included, but the result stayed the same (no display manager).

Revision history for this message
Brian Murray (brian-murray) wrote :

While you had kdm installed it was installed from a ppa.

kdm 4:4.11.3-0ubuntu0.1~ubuntu12.04~ppa1 0

I'd image this figures into the calculation.

Revision history for this message
Harald Sitter (apachelogger) wrote :

Two things:

1. if both are required then that has been broken for a long time because there has not been a kubuntu-artwork package for at least 5 years
2. if PPAness does affect the calculation, then I guess that needs to change to some degree since we pretty much support our own PPAs :S

Assuming 1. doesn't apply, enhancing the keydeps with some actual kubuntu stuff would help sufficiently though:
kubuntu-settings-desktop, kubuntu-notification-helper, kubuntu-debug-installer, kubuntu-web-shortcuts

Those do not get updates via PPAs and at the end of the day I suppose those are the most reliable indicators of a kubuntu installation.

Changed in ubuntu-release-upgrader (Ubuntu Trusty):
assignee: nobody → Harald Sitter (apachelogger)
Revision history for this message
Harald Sitter (apachelogger) wrote :

Fix committed to bzr. Using:
- plasma-desktop & kubuntu-settings-desktop
- plasma-netbook & kubuntu-settings-netbook

Changed in ubuntu-release-upgrader (Ubuntu Trusty):
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntu-release-upgrader - 1:0.210

---------------
ubuntu-release-upgrader (1:0.210) trusty; urgency=low

  [ Brian Murray ]
  * data/DistUpgrade.cfg.precise: change kernel removals to 3.2.0
  * source_ubuntu-release-upgrader.py: collect dmesg info when reporting
    upgrade failures
  * Utilize new downloaded event from update-manager thereby speeding up usage
    of MetaReleaseCore. Thanks to Anders Kaseorg for the patch.
  * Don't build depend on scrollkeeper thanks to Jeremy Bicha for the patch.

  [ Harald Sitter ]
  * data/DistUpgrade.cfg.precise: change kubuntu-desktop key dependencies to
    plasma-desktop, kubuntu-default-settings (previous ones did not exist or
    were simply bad key dependencies) LP: #1264887
    + Same for kubuntu-netbook using plasma-netbook,
       kubuntu-netbook-default-settings.
  * data/DistUpgrade.cfg: change kubuntu-desktop key dependencies to
    plasma-desktop, kubuntu-settings-desktop
    + Same for kubuntu-netbook using plasma-netbook, kubuntu-settings-netbook
 -- Brian Murray <email address hidden> Thu, 23 Jan 2014 16:14:37 -0800

Changed in ubuntu-release-upgrader (Ubuntu Trusty):
status: Fix Committed → Fix Released
Revision history for this message
Nils Kassube (kassube) wrote :

Today I repeated the upgrade on the test-partition and I can confirm that the bug is fixed. Thanks for taking care of the issue.

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.