FedoraForum.org - Fedora Support Forums and Community
Results 1 to 13 of 13
  1. #1
    Join Date
    Sep 2016
    Location
    Ohio, US
    Posts
    19
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    gdm login screen stopped appearing, graphical login not possible

    I have a fresh installation of Fedora 24 (Workstation) which was working great but now I can never get the gdm login screen to appear, so it is not possible to login graphically.

    I am using the stock open-source fedora drivers. I can boot from the Live media and everything still works fine. Also after booting, I can ssh in to the system just fine; everything seems to work except for never getting a graphical login screen.

    When this first happened I was logged in and was idle long enough for the Gnome screen lock to kick in. When I came back I was unable to type anything into the password dialog box; though the mouse pointer would move. Now, even after many reboots, I can not even get a login screen to appear. If I boot graphically it gets to the point where the fedora "f" blue circle logo appears in the center of the screen and then nothing --- no animation, no mouse movement and no keys work, not even Esc or control-alt-F keys. If I boot non-graphically (remove rhgb from boot command) it will get stuck on start job is running for Wait for plymouth.

    I can not find any error messages (journalctl, dmesg, or in Xorg.0.log). The systemd status for gdb.service says gdm is active and running, and there are no error messages output. If I restart gdm.service the screen just goes completely blank.

    What further information can I gather, and is there any way to get gdm to output additional debugging information? Some further details follow below. Thanks for any help!

    # systemctl status gdm.service
    ● gdm.service - GNOME Display Manager
    Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: enabled)
    Active: active (running) since Mon 2016-09-05 00:38:04 EDT; 42min ago
    Main PID: 1846 (gdm)
    Tasks: 6 (limit: 512)
    CGroup: /system.slice/gdm.service
    ├─1846 /usr/sbin/gdm
    └─1853 gdm-session-worker [pam/gdm-launch-environment]

    Sep 05 00:38:04 jasper.meranda.us systemd[1]: Starting GNOME Display Manager...
    Sep 05 00:38:04 jasper.meranda.us systemd[1]: Started GNOME Display Manager.

    System info:

    This is a desktop system (no hibernation)
    Radeon RX 470 video card (Sapphire).
    Using Fedora drivers, NOT the AMD proprieratary drivers.
    The video card has multiple outputs, but only one monitor is connected.
    Monitor is a ultra-widescreen 3440 x 1440

    I have tried both of the latest kernels (4.7.2-201.fc24.x86_64.img) and (4.6.7-300.fc24.x86_64.img) with no difference.

  2. #2
    Join Date
    Oct 2011
    Posts
    1,917
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: gdm login screen stopped appearing, graphical login not possible

    Try to disable Wayland for GDM. Edit/create /etc/gdm/custom.conf and uncomment #WaylandEnable=false so that it reads something like:
    Code:
    [daemon]
    # Uncoment the line below to force the login screen to use Xorg
    WaylandEnable=false
    Another thing you can try, log in from a terminal as a normal user and try to run gnome directly using X. Press Ctrl+Alt+F3, login and use command startx.

  3. #3
    Join Date
    Sep 2016
    Location
    Ohio, US
    Posts
    19
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: gdm login screen stopped appearing, graphical login not possible

    Yes, logging into a different virtual "text" terminal and then running "startx" works for one user!

    I will try the configuration change you suggested next.

    Thanks

  4. #4
    Join Date
    Sep 2016
    Location
    Ohio, US
    Posts
    19
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: gdm login screen stopped appearing, graphical login not possible

    Now that I know where the gdm config file is, I first tried to turn on gdm debugging and rebooting. Now when it hangs, I can see more information from systemctl.... Does this hint and what I should do next to diagnose this?

    (I will disable Wayland next, though I hope that doesn't have to be a long term solution)

    # systemctl status gdm.service | cat
    ● gdm.service - GNOME Display Manager
    Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: enabled)
    Active: active (running) since Mon 2016-09-05 02:52:10 EDT; 3min 15s ago
    Main PID: 1509 (gdm)
    Tasks: 6 (limit: 512)
    CGroup: /system.slice/gdm.service
    ├─1509 /usr/sbin/gdm
    └─1563 gdm-session-worker [pam/gdm-launch-environment]

    Sep 05 02:52:10 jasper.meranda.us gdm-launch-environment][1563]: GdmSessionWorker: Set PAM environment variable: 'PATH=/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin'
    Sep 05 02:52:10 jasper.meranda.us gdm-launch-environment][1563]: GdmSessionWorker: state ACCREDITED
    Sep 05 02:52:10 jasper.meranda.us gdm[1509]: GdmSession: type wayland, program? yes, seat seat0
    Sep 05 02:52:10 jasper.meranda.us gdm-launch-environment][1563]: GdmSessionWorker: session display mode set to new-vt
    Sep 05 02:52:10 jasper.meranda.us gdm-launch-environment][1563]: GdmSessionWorker: Set PAM environment variable: 'XDG_SESSION_TYPE=wayland'
    Sep 05 02:52:10 jasper.meranda.us gdm-launch-environment][1563]: GdmSessionWorker: attempting to change state to ACCOUNT_DETAILS_SAVED
    Sep 05 02:52:10 jasper.meranda.us gdm-launch-environment][1563]: GdmSessionWorker: user gdm, not fully loaded yet, will save account details later
    Sep 05 02:52:10 jasper.meranda.us gdm-launch-environment][1563]: AccountsService: ActUserManager: trying to track new user with username gdm
    Sep 05 02:52:10 jasper.meranda.us gdm-launch-environment][1563]: AccountsService: ActUserManager: finding user 'gdm' state 1
    Sep 05 02:52:10 jasper.meranda.us gdm-launch-environment][1563]: AccountsService: ActUserManager: waiting for user manager to load before finding user 'gdm'

  5. #5
    Join Date
    Sep 2016
    Location
    Ohio, US
    Posts
    19
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: gdm login screen stopped appearing, graphical login not possible

    Unfortunately disabling Wayland does not appear to have worked. It again hangs before showing the login screen, with the boot text saying "A start job is running for Wait for Plymouth Boot Screen to Quit" indefinitely. The output of "systemctl status gdm.service" is identical to the above, except the session type is (null) and XDG_SESSION_TYPE=x11

    Is there anything else I can do to get more information that may help?

    Thanks again

  6. #6
    Join Date
    Aug 2005
    Posts
    718
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: gdm login screen stopped appearing, graphical login not possible

    You might get more information using:
    Code:
    # journalctl -b _COMM=gdm > /home/userdir/messages
    # chown user:user /home/userdir/messages
    with user and userdir set appropriately.
    systemctl only shows the last 10 relevant messages from the journal.
    I tried it with debugging on, but I could not find much in common with your output.

  7. #7
    Join Date
    Oct 2011
    Posts
    1,917
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: gdm login screen stopped appearing, graphical login not possible

    I am not sure what to do next. You can provide what kldixon recommended or better yet, full boot log "journalctl -b" to pastebin or similar. Maybe some other service that GDM is dependent on is stalling. Well good news is that it seems it is not a driver issue.

  8. #8
    Join Date
    Sep 2016
    Location
    Ohio, US
    Posts
    19
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: gdm login screen stopped appearing, graphical login not possible

    I still can not get gdm to display a login screen, either with Wayland or X11. But a gnome session can be started directly by invoking "startx". I've read through the Gnome GDM help page at https://help.gnome.org/admin/gdm/3.20/ but did not find much that was useful here.

    From the logs it looks to me like gdm is possibly waiting on the "user manager", whatever that is, though it certainly could be something else.

    I also tried to disable the gdm user list feature, but that doesn't help.

    Code:
    # gsettings get org.gnome.login-screen disable-user-list
    false
    # gsettings set org.gnome.login-screen disable-user-list true
    # gsettings get org.gnome.login-screen disable-user-list
    true
    Some more detailed information:

    Code:
    # cat /proc/version 
    Linux version 4.7.2-201.fc24.x86_64 (mockbuild@bkernel01.phx2.fedoraproject.org) (gcc version 6.1.1 20160621 (Red Hat 6.1.1-3) (GCC) ) #1 SMP Fri Aug 26 15:58:40 UTC 2016
    
    # rpm -qi gdm.x86_64 | head
    Name        : gdm
    Epoch       : 1
    Version     : 3.20.1
    Release     : 3.fc24
    Architecture: x86_64
    Install Date: Fri 02 Sep 2016 06:31:34 PM EDT
    Group       : User Interface/X
    Size        : 2149104
    License     : GPLv2+
    Signature   : RSA/SHA256, Wed 29 Jun 2016 05:34:07 AM EDT, Key ID 73bde98381b46521
    
    # rpm -V gdm
    S.5....T.  c /etc/gdm/custom.conf    -- Disabled Wayland and enabled debug
    .M....G..    /var/log/gdm            -- ? directory is empty
    
    # ls -ldZ /var/log/gdm
    drwx--x--x. 2 root gdm system_u:object_r:xserver_log_t:s0 4096 Jun 28 12:56 /var/log/gdm
    
    # lspci | grep -i radeon
    01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] (rev cf)
    Below are all the boot logs related to gdm, the gdm-launch-environment subprocess, and the graphics card hardware detection. For the later you can see that the card has 5 display outputs, but only the first (DisplayPort connector 0) has a monitor attached.



    I've also attached the complete boot log file which has everything.

    Thanks again for any help or ideas to gather more diagnostic information!
    Attached Files Attached Files

  9. #9
    Join Date
    Sep 2016
    Location
    Ohio, US
    Posts
    19
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: gdm login screen stopped appearing, graphical login not possible

    I found it!

    The thing which was causing this was I had two user accounts listed in /etc/passwd that had the same uid. In particular I had both a "gitolite3" user (uid 984) that is created by the gitolite3 package. But had also created an identical user with the username "git", so that repository references could be simplified to just "git@...".

    Removing the second user from /etc/passwd and rebooting allows gdm to work normally.

    The duplicate uid entry in /etc/passwd was causing the accounts-daemon, from the accountsservice package, which itself is part of the FreeDesktop.org suite rather than Gnome, to lock up.

    Code:
    # systemctl status accounts-daemon.service
    ● accounts-daemon.service - Accounts Service
       Loaded: loaded (/usr/lib/systemd/system/accounts-daemon.service; enabled; vendor preset: enabled)
       Active: active (running) since Mon 2016-09-05 14:56:10 EDT; 5h 8min ago
     Main PID: 1457 (accounts-daemon)
        Tasks: 3 (limit: 512)
       CGroup: /system.slice/accounts-daemon.service
               └─1457 /usr/libexec/accounts-daemon
    
    Sep 05 14:56:10 xxxx systemd[1]: Starting Accounts Service...
    Sep 05 14:56:10 xxxx accounts-daemon[1457]: ** (accounts-daemon:1457): CRITICAL **: error exporting user object: An object is already exported for the interface org.freedesktop.Accounts.User at /org/freedesktop/Accounts/User984
    Sep 05 14:56:10 xxxx accounts-daemon[1457]: started daemon version 0.6.40
    Sep 05 14:56:10 xxxx systemd[1]: Started Accounts Service.
    Notice the CRITICAL error being logged, yet neither systemctl nor gdm seem to realize anything is wrong.

    Also with further investigation it seems that Fedora treats all users with a uid < 1000 as system users; yet Gnome only considers uids < 500 as system users. So when it finds a user with a uid of 984 it thinks it is a normal user account that can be logged into, rather than hiding it.

    I don't know if this is actually a bug, though I tend to think it is as it should be possible to have alias usernames. And I don't know if this is a bug in the FreeDesktop code, or if it was introduced as a Fedora-specific patch, etc. Likewise it seems gdm should be more helpful here too, other than just hanging indefinitely.
    Last edited by dmeranda; 6th September 2016 at 01:26 AM. Reason: gramatical typos

  10. #10
    Join Date
    Sep 2016
    Location
    Ohio, US
    Posts
    19
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: gdm login screen stopped appearing, graphical login not possible

    I'm going to mark this thread as solved, though I still feel like there is a bug here someplace and the workaround is limiting. Questions...

    • Does gdm (Gnome) and Fedora have different ideas of the minimum uid that separates normal users from system users (500 vs 1000)?
    • Should a duplicate uid in the passwd be allowed? Especially for system users.
    • Should a duplicate uid cause a more visible error than just a log message? It certainly should not cause gdm to silently hang without any obvious cause being made known.

    But if there is a bug, where should it be reported?

  11. #11
    Join Date
    Jun 2016
    Location
    USE
    Posts
    3
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: gdm login screen stopped appearing, graphical login not possible

    Quote Originally Posted by dmeranda
    I have a fresh installation of Fedora 24 (Workstation) which was working great ..........

    I am using the stock open-source fedora drivers.
    .
    .
    .
    System info:

    This is a desktop system (no hibernation)
    Radeon RX 470 video card (Sapphire).
    Using Fedora drivers, NOT the AMD proprieratary drivers.
    The video card has multiple outputs, but only one monitor is connected.
    Monitor is a ultra-widescreen 3440 x 1440

    I have tried both of the latest kernels (4.7.2-201.fc24.x86_64.img) and (4.6.7-300.fc24.x86_64.img) with no difference.
    1) Are you saying that AMD RX 4x0 graphics cards are working with vanilla Open Source drivers in Fedora24 ?
    As in working :
    2) accelerated desktop windows and desktop window animations ?
    3) accelerated web browsers : 2D & 3D CSS animations, and WebGL ?

  12. #12
    Join Date
    Sep 2016
    Location
    Ohio, US
    Posts
    19
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: gdm login screen stopped appearing, graphical login not possible

    Yes, a vanilla Fedora 24 using the standard open source drivers has been working flawlessly so far with a Radeon RX 470 card (Sapphire Nitro+ 8GB). All Gnome screen animations are fine, web browser CSS rendering/animations work, and even a 2D game (Factorio) with all graphics options turned up works fine. I have not tried anything particularly stressful like OpenGL 3D games, etc.


    This particular bug turned out to have nothing to do with the video card or graphics driver, but rather is a bug in the gbm login screen concerning how it obtains the list of non-system users apparently so it can present a list of user choices on the login screen.

    1. gdm considers all users with a uid > 500 to be normal users; yet Fedora makes this distinction at 1000; so there are some system users (like for the gitolite3 package) that gdm considers normal users.

    2. gdm will hang if it finds multiple accounts listed in /etc/passwd that have the same uid; and which it considers to be non-system users.

  13. #13
    Join Date
    Jun 2016
    Location
    USE
    Posts
    3
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: gdm login screen stopped appearing, graphical login not possible

    Thanks for responding.
    I won't need any gaming support. Only what I listed at 2) and 3). So excellent news.


    EDIT: Ah forget what I wrote below! I just realised that Blender is OK with OpenGl 3.2. All clear.
    But, I forgot about Blender. So do you happen to know which versions of mesa and llvm were used?
    I read that mesa 12.0.x + llvm 3.8.1 support up to OpenGL 4.1.
    And that Mesa 12.1.x +llvm 3.9 support up to OpenGL 4.5.
    Last edited by Dokter Bibber; 22nd September 2016 at 01:33 PM.

Similar Threads

  1. Login screen not appearing
    By omalley576 in forum Using Fedora
    Replies: 14
    Last Post: 8th June 2009, 03:19 PM
  2. Graphical Login screen goes blank
    By shreedara in forum Installation, Upgrades and Live Media
    Replies: 6
    Last Post: 8th September 2006, 01:34 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •