Lucid to Precise: debconf prompt about which DM to use during upgrade
Bug #911813 reported by
Jean-Baptiste Lallement
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdm (Ubuntu) |
Fix Released
|
Medium
|
Martin Pitt | ||
Precise |
Fix Released
|
Medium
|
Martin Pitt |
Bug Description
During the upgrade from lucid to precise a debconf prompt is shown to select which DM to use.
DM configuration was unchanged in Lucid.
Same bug was fixed in Oneiric (bug 806559)
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: lightdm 1.0.6-0ubuntu4
ProcVersionSign
Uname: Linux 3.2.0-7-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Wed Jan 4 16:17:24 2012
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1)
ProcEnviron:
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: Upgraded to precise on 2012-01-04 (0 days ago)
To post a comment you must log in.
We currently check this:
if [ -z "$2" -a -n "$RELEASE_ UPGRADE_ IN_PROGRESS" ]; then default- x-display- manager lightdm default- x-display- manager seen true default- x-display- manager || :
db_set shared/
db_fset shared/
else
db_input high shared/
db_go || :
fi
update-manager sets $RELEASE_ UPGRADE_ IN_PROGRESS, so it seems in your upgrade method this wasn't set. Was your upgrade done using apt-get dist-upgrade? In that case we actually expect the prompt.
If it was from do-release-upgrade, it's meant to not show. We shouldn't have a previously installed lightdm in that case, so the -z "$2" part ought to be okay. Do you happen to have full logs from that upgrade still?
Thanks!