deactivating gdm service breaks grahical authentication
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-system-tools (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Binary package hint: gnome-system-tools
In Xubuntu x64 8.04 with gnome-system-tools 2.22.0 :
In services settings, if I uncheck gdm, some things are broken whereas it is supposed to just "allow users to login locally" :
Of course it deactivate graphical login as one would expect, but also breaks user switching, and graphical authentication.
This is a big problem because graphical authentication is required to unlock services pannel, necessary step to reactivate gdm service.
From this point command line is required to rollback the action.
If you want details, I can do it again but it would be nice to give me first the command line to activate gdm service (I'm not a Debian guy so far, more a RedHat one), since it was a pain to fix the problem last time...
I think this option (deactivating gdm service) should just deactivate graphical login as stated, or at least warn that it will stop other functionnalities, and won't be rollable back graphically.
I reproduced this bug in VirtualBox, using Hardy 8.04. Unfortunately, while Applications -> System -> Services -> Graphical login manager (GDM) ¨Allows users to login graphically¨ gives a definite warning:
Are you sure you want to deactivate gdm?
This may affect your system behavior in
several ways, possibly leading to data loss.
Marking ¨Yes¨ and proceeding completely stops gdm, leaving me with at the screens I would have using Ctl+Alt+F8, the terminal used for data messages. There is no indication of how to get a desktop back. Switching to tty2, I logged in and used 'sudo gdm start' to get the desktop back and could then enter Services again to allow gdm to be used.
I would expect ¨Allows users to login graphically¨ to mean I just can´t login, not that my desktop will immediately shutdown.
I am confirming this bug based on this and the reporters comments. Thanks for reporting this bug.