removing gdm results in dm chooser question even when only 1 dm is left
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdm (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When removing gdm package on quantal, the dm chooser question is always presented, even when there is only one dm remaining on the system. This seems to be caused by an issue in the debconf gdm.prerm script.
I made a little test script and discovered the following, although I am not actually sure why the "|| true" is interfering with the unregister. Test case #2 below returns the correct result. I do note this does not appear to happen on precise which uses the commands as per the #1 test case. fwiw lightdm uses #2 also.
1. running (this is what is currently in the prerm script):
db_unregister shared/
db_get shared/
returns:
debconf (developer): <-- UNREGISTER shared/
debconf (developer): --> 0
db_get shared/
debconf (developer): <-- GET shared/
debconf (developer): --> 0 lightdm
2. running (this produces the correct output):
db_unregister shared/
db_get shared/
returns:
debconf (developer): <-- starting
debconf (developer): <-- UNREGISTER shared/
debconf (developer): --> 0
There is also a second issue in the `gdm.prerm` script, lightdm no longer has a 'daemon_name' key, so the following command will fail with status 10, if someone trys to configure lightdm from the dm chooser when removing gdm.
db_get "$RET"/daemon_name
This will only cause be a problem when the user has > 1 dm remaining on the system after uninstalling gdm. Although it does currently always trigger an error message due to the chooser bug.