Bug 1195485

Proposed as a Blocker for 22-alpha by Fedora user pavlix using the blocker tracking app because:

 The default display manager cannot log the user in. Expert knowledge is needed to get logged in at all.

Pavel, is this still an issue with the latest packages? I'm running a Fedora Workstation 22 system that I installed freshly from the 20150218 nightly compose of Fedora Workstation Live and have updated ever since.

What installation media did you use? What package set did you choose in Anaconda (if not a Live installer)?

(In reply to Stephen Gallagher from comment #2)
> Pavel, is this still an issue with the latest packages? I'm running a Fedora
> Workstation 22 system that I installed freshly from the 20150218 nightly
> compose of Fedora Workstation Live and have updated ever since.

To be honest, I'm not getting it right now but I didn't update any packages, I only changed network configuration and probably nothing else. I might try later.

> What installation media did you use? What package set did you choose in
> Anaconda (if not a Live installer)?

I used PXE boot:

http://dl.fedoraproject.org/pub/fedora/linux/development/22/x86_64/os/images/pxeboot/

I chose Fedora Workstation and didn't do any other changes except reclaiming disk space. Since yesterday, I didn't get any updates using yum.

The issue is back. I don't know what exactly is different in the system between the time when it works and the time when it fails.

One coincidence is that now it fails and I'm not connected to a network. After connecting and restarting gdm.service I can log in.

One other detail is that I'm using a hostname that isn't resolvable, but that's *not* changing between connected and disconnected state. I do not consider a non-resolvable FQDN hostname a valid reason for GUI issues anyway, so I'm mentioning it just in case it somehow affected the situation.

the most important information is missing here: rpm -q gdm

I can't reproduce this with Alpha TC7, either BIOS or (U)EFI baremetal, or VirtualBox. (On a Mac with both AMD Radeon HD 6750M and i915 graphics, I get a lot of flicker at gdm which clears after login, nothing useful is in dmesg or journal. But this would be a different bug.)

Discussed at today's blocker review meeting [1].

This bug was rejected as Alpha Blocker - This bug doesn't seem to be reproducible. If more information comes to the surface, please repropose with steps to reproduce.

http://meetbot.fedoraproject.org/fedora-blocker-review/2015-03-02/

I just downloaded the boot.iso from [0] and I can confirm that in VirtualBox 4.3.22 r98236.

The iso boots but fails to bring up the graphical interface and thus anaconda.


Abis.


[0]
http://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/fedora/linux/development/22/x86_64/os/images/

(In reply to Alexander Bisogiannis from comment #10)
> The iso boots but fails to bring up the graphical interface and thus
> anaconda.

Sounds like bug 1196676.

This issue still happens to me on Fedora 23 and 24. It only fails after being logged in before.

I still run into this bug fairly often.

Steps to reproduce for me:
1. log in into a gnome session (both gnome+x11 and gnome+wayland work).
2. Open gnome-system-monitor. Note the console/tty ("Session" column) values
3. logout
4. through tty, make sure there is at least one process running with with the same session as noted down in step 2.
5. from gdm, try to login again (same user)

What happens:
Login fails, I'm immediately sent back to login screen.

What should happen:
Processes on a specific session should be ended when the session ends.
Even if a process is running at the session, open a new session anyway (previous session might have failed).

Additional info:
Output to syslog:Jun 11 21:22:19 hostname audit[10054]: USER_AUTH pid=10054 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_unix,pam_gnome_keyring acct="username" exe="/usr/libexec/gdm-session-worker" hostname=? addr=? terminal=/dev/tty1 res=success'
Jun 11 21:22:19 hostname audit[10054]: USER_ACCT pid=10054 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="username" exe="/usr/libexec/gdm-session-worker" hostname=? addr=? terminal=/dev/tty1 res=success'
Jun 11 21:22:19 hostname audit[10054]: CRED_ACQ pid=10054 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_unix,pam_gnome_keyring acct="username" exe="/usr/libexec/gdm-session-worker" hostname=? addr=? terminal=/dev/tty1 res=success'
Jun 11 21:22:19 hostname audit[10054]: USER_ROLE_CHANGE pid=10054 uid=0 auid=1000 ses=5 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='pam: default-context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 selected-context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 exe="/usr/libexec/gdm-session-worker" hostname=? addr=? terminal=/dev/tty4 res=success'
Jun 11 21:22:19 hostname audit[1]: USER_AVC pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='Unknown permission start for class system exe="/usr/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?'
Jun 11 21:22:19 hostname audit[1]: USER_AVC pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='Unknown permission start for class system exe="/usr/lib/systemd/systemd" sauid=0 hostname=? addr=? terminal=?'
Jun 11 21:22:19 hostname systemd-logind[821]: New session 5 of user username.
Jun 11 21:22:19 hostname systemd[1]: Started Session 5 of user username.
Jun 11 21:22:19 hostname gdm-password][10054]: pam_unix(gdm-password:session): session opened for user username by (uid=0)
Jun 11 21:22:19 hostname audit[10054]: USER_START pid=10054 uid=0 auid=1000 ses=5 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_selinux,pam_loginuid,pam_selinux,pam_keyinit,pam_namespace,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_gnome_keyring acct="username" exe="/usr/libexec/gdm-session-worker" hostname=? addr=? terminal=/dev/tty4 res=success'
Jun 11 21:22:19 hostname audit[10054]: USER_LOGIN pid=10054 uid=0 auid=1000 ses=5 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='uid=1000 exe="/usr/libexec/gdm-session-worker" hostname=? addr=? terminal=? res=success'

Created attachment 1167022 [details]
an excerpt from syslog covering the steps described in comment #12

I've attached a more detailed log.

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.