| 1 |
On Mon, May 22, 2017 at 11:16 AM, Raffaele Belardi |
| 2 |
<raffaele.belardi@××.com> wrote: |
| 3 |
> I'm unable to start the gdm service on a recently installed gnome |
| 4 |
> desktop (~x86): the service continuously fails and restarts with the |
| 5 |
> errors below. If I disable the service and login into a text console, |
| 6 |
> startx works fine but the Gnome session misses some features (e.g. |
| 7 |
> screen lock). I enabled debug logging on gdm but nothing significant |
| 8 |
> appears. |
| 9 |
> |
| 10 |
> Any suggestions? |
| 11 |
> |
| 12 |
> thanks, |
| 13 |
> |
| 14 |
> raffaele |
| 15 |
> |
| 16 |
> |
| 17 |
> systemd[356]: user@××.service: Failed at step PAM spawning |
| 18 |
> /usr/lib/systemd/systemd: Operation not permitted |
| 19 |
> systemd[1]: Failed to start User Manager for UID 32. |
| 20 |
> gdm-launch-environment][310]: pam_systemd(gdm-launch- |
| 21 |
> environment:session): Failed to create session: Start job for unit user |
| 22 |
> @32.service failed with 'failed' |
| 23 |
> systemd[1]: user@××.service: Unit entered failed state. |
| 24 |
> systemd[1]: user@××.service: Failed with result 'protocol'. |
| 25 |
> |
| 26 |
> ... |
| 27 |
> |
| 28 |
> /usr/libexec/gdm-x-session[359]: Activated service |
| 29 |
> 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 |
| 30 |
> exited with stat |
| 31 |
> /usr/libexec/gdm-x-session[359]: Unable to register display with |
| 32 |
> display manager |
| 33 |
> |
| 34 |
> # grep 32 /etc/passwd |
| 35 |
> gdm:x:32:32:GDM:/var/lib/gdm:/bin/false |
| 36 |
> |
| 37 |
> # eselect profile list |
| 38 |
> Available profile symlink targets: |
| 39 |
> [1] default/linux/x86/13.0 |
| 40 |
> [2] default/linux/x86/13.0/selinux |
| 41 |
> [3] default/linux/x86/13.0/desktop |
| 42 |
> [4] default/linux/x86/13.0/desktop/gnome |
| 43 |
> [5] default/linux/x86/13.0/desktop/gnome/systemd * |
| 44 |
> [6] default/linux/x86/13.0/desktop/plasma |
| 45 |
> [7] default/linux/x86/13.0/desktop/plasma/systemd |
| 46 |
> [8] default/linux/x86/13.0/developer |
| 47 |
> [9] default/linux/x86/13.0/systemd |
| 48 |
> [10] hardened/linux/x86 |
| 49 |
> [11] hardened/linux/x86/selinux |
| 50 |
> [12] hardened/linux/musl/x86 |
| 51 |
> [13] default/linux/uclibc/x86 |
| 52 |
> [14] hardened/linux/uclibc/x86 |
| 53 |
> |
| 54 |
|
| 55 |
A Google search found this systemd issue: |
| 56 |
https://github.com/systemd/systemd/issues/4342 |
| 57 |
Quote: |
| 58 |
@poettering I see I left no account modules in the bare-bones PAM |
| 59 |
config. Maybe it is pam_acct_mgmt failing then? |
| 60 |
|
| 61 |
@yuwata what happens if you add account required pam_unix.so ? |
| 62 |
|
| 63 |
@fsateler Thanks. By adding the line, user sessions successfully start |
| 64 |
without the error messages. Do you think the line should be added to |
| 65 |
the minimal PAM file? |
| 66 |
|
| 67 |
See if that helps. |
Archives