FS#65653 - [gdm] Initial Setup mode not starting

Attached to Project: Arch Linux
Opened by Tim Vilgot Mikael Fredenberg (Metztli) - Friday, 28 February 2020, 09:51 GMT
Last edited by Jan Alexander Steffens (heftig) - Thursday, 29 October 2020, 08:49 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

When having this package installed gdm never starts and errors on:
systemd[1]: Started GNOME Display Manager.
gdm-launch-environment][757]: pam_succeed_if(gdm-launch-environment:auth): requirement "user = gdm" not met by user "gnome-initial-setup"

commenting out:
auth required pam_succeed_if.so audit quiet_success user = gdm
account required pam_succeed_if.so audit quiet_success user = gdm
session required pam_succeed_if.so audit quiet_success user = gdm
in file://etc/pam.d/gdm-launch-environment

results in:
systemd[1]: Starting GNOME Display Manager...
gdm[662]: Endast root-användaren kan köra GDM **(only root user can run GDM)**
systemd[1]: gdm.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: gdm.service: Failed with result 'exit-code'.
systemd[1]: Failed to start GNOME Display Manager.
systemd[1]: gdm.service: Scheduled restart job, restart counter is at 1.
systemd[1]: Stopped GNOME Display Manager.
systemd[1]: Starting GNOME Display Manager...
gdm[681]: Endast root-användaren kan köra GDM **(only root user can run GDM)**
systemd[1]: gdm.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: gdm.service: Failed with result 'exit-code'.
systemd[1]: Failed to start GNOME Display Manager.
systemd[1]: gdm.service: Scheduled restart job, restart counter is at 2.
systemd[1]: Stopped GNOME Display Manager.

This package is fundamentally broken and searching upstream bugs results in nothing and this is supposedly also working on Debian (according to a r/archlinux user)
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Thursday, 29 October 2020, 08:49 GMT
Reason for closing:  Fixed
Additional comments about closing:  gdm 3.38.1-3
Comment by mattia (nTia89) - Sunday, 03 May 2020, 07:52 GMT
Is this issue still present?
if yes, can you provide an easy way (steps) to reproduce it?
thanks
Comment by Tim Vilgot Mikael Fredenberg (Metztli) - Monday, 27 July 2020, 09:56 GMT
Still present on 3.36.4-1, same exact logs.

Steps to reproduce:
1. Install Arch Linux
2. Don't create a new user or anything, just install gnome-shell package and gnome-initial-setup package
3. systemctl enable --now gdm.service

(Issue persists through reboot)
Comment by Balló György (City-busz) - Monday, 26 October 2020, 05:51 GMT
When I remove those lines requiring user = gdm from file /etc/pam.d/gdm-launch-environment, the initial setup starts fine for me. So it's definitely a problem with the gdm package.

@heftig: the initial setup mode launches GDM as user "gnome-initial-setup", so you should modify the PAM file to allow this user.
Comment by Jan Alexander Steffens (heftig) - Tuesday, 27 October 2020, 20:32 GMT
Is this fixed in gdm 3.38.1-3 ?
Comment by Balló György (City-busz) - Thursday, 29 October 2020, 08:26 GMT
Yes, it's fixed now. Thanks!

Loading...