#731882 gdm3: requires root password for reboot

Package:
gdm3
Source:
gdm3
Description:
GNOME Display Manager
Submitter:
Steven Post
Date:
2013-12-28 23:09:04 UTC
Severity:
normal
#731882#5
Date:
2013-12-10 20:13:30 UTC
From:
To:
Dear Maintainer,

As suggested by Andreas Cadhalpun in #731686, I open a new bug for this.
When trying to reboot from the login screen, the root password is asked. After
giving the correct password, the system reboots normally (only if systemd is
used as pid 1).

This seems to be a regression from 3.4 (now 3.8).

Best regards,
Steven

#731882#10
Date:
2013-12-10 21:13:37 UTC
From:
To:
Le Tue, 10 Dec 2013 21:13:30 +0100,
Steven Post <redalert.commander@gmail.com> a écrit :

Hi,

Could you please try something, in /etc/pam.d/ delete the
gdm-launch-environment symlink and then create a file with the same
name with the following content:

#%PAM-1.0
auth    requisite       pam_nologin.so
auth    required        pam_permit.so
@include common-account
session required        pam_limits.so
session required        pam_env.so readenv=1
session required        pam_env.so readenv=1 envfile=/etc/default/locale
@include common-session
@include common-password


Then try to reboot the machine and then try if it's still happening

Cheers

Laurent Bigonville

#731882#15
Date:
2013-12-11 20:27:43 UTC
From:
To:
It still happens after changing that file in /etc/pam.d and then
rebooting, no change whatsoever in behaviour that I can tell. I did
notice that the password prompt is only displayed when previously logged
in (Gnome session).

No password prompt:
1) (re)boot starts gdm3
2) restart from login screen

Password prompt is shown:
1) (re)boot starts gdm3
2) log into Gnome
3) logout
4) restart from login screen

Perhaps the session doesn't close completely? I remember from (pre-)3.4
that a logged in user shutting down the machine also got the password
prompt when another session (such as a root terminal session) was still
open. If so, maybe this bug needs to re-assigned to a more appropriate
package, but I don't know which.

Best regards,
Steven

#731882#20
Date:
2013-12-11 21:24:25 UTC
From:
To:
Le Wed, 11 Dec 2013 21:27:43 +0100,
Steven Post <redalert.commander@gmail.com> a écrit :

The fact that you cannot reboot the machine if somebody else is logged
in without root confirmation is a feature.

Could you please post here the output of ck-list-sessions and the
output of loginctl please.

Cheers

Laurent Bigonville

#731882#25
Date:
2013-12-11 22:06:12 UTC
From:
To:
On Wed, 2013-12-11 at 22:24 +0100, Laurent Bigonville wrote:
[...]

And rightly so.
1) from within session: ck-list-sessions >> filename
2) still same session: loginctl >> filename
3) 2 times: echo "-----" >> filename
4) logout
5) switch to tty1 (Alt+Ctrl+F1) and log in as regular user
6) ck-list-sessions >> filename
7) loginctl >> filename

I should have added a separator mark between all commands, but the
output seems readable nonetheless. Please correct me if I interpret this
wrong. ck-list-sessions first lists a single session, as does loginctl
(last line before the "-----"). After logging out and entering tty1,
ck-list-sessions shows 2 sessions (1 for gdm and 1 for me on the
console). But loginctl shows 3 lines, it still has that session with id
2 from before logging out of gnome. So it seems I was right about the
gnome session not terminating completely.

Best regards,
Steven

#731882#30
Date:
2013-12-28 20:47:21 UTC
From:
To:
Hi,

Bug#732623 might be related to Bug#731882, as it seems gdm also has too
many running sessions after logout, so perhaps this is a bug in logind?
Or it just might be implemented wrong in both gdm3 and lightdm.

Best regards,
Andreas

#731882#35
Date:
2013-12-28 23:07:30 UTC
From:
To:
Perhaps. Concerning Bug#731882, I could also see that the root password
is sometimes required. See Bug#729576:

  Sometimes I'm asked to enter the root password, but this has no effect.

(the "no effect" is because systemd isn't pid 1 in my case).