[SOLVED]Startup stalled at graphical target reached. No login screen.

ajt568 · 2018-08-03 14:27:32

I have come to the end of trying to solve this issue and so I am asking for help. I hope it is a simple solution such as a lost file or something?

My problem is that when I start the desktop computer the verbose output stalls at graphical target reached. There is no login screen. I can switch to tty2 using ctrl-f2 and log in using my usual credentials. In the bash terminal I can then start X with ‘xinit gnome-session’. Tty1 is then displayed correctly as the gnome desktop. All is well which suggests the nvidia card is working properly. I can switch to other terminals such as tty3 etc with no problem. I do not understand what is preventing the login screen being displayed. The problem has been with me for a few weeks now so it is not related to the latest update.

I have tried degrading nvidia with no change, I have also degraded Xorg-server etc back to 1.19.6 with no change. I have currently set these packages to the latest version.

Configuration is;
Arch linux x86_64 4.17.11-arch1 updated with pacman on 2 August 2018
Intel core i7
Geforce GTX970
Systemd
LVM

Systemctl —failed shows ‘0 loaded units listed’
Audited.service is masked
Lvm2-activation.service is masked
Openvswitch.service is masked
Plymouth-quit-wait.service is masked
Plymouth-start.service is masked
Create-local.service is masked
Says log.service is masked
These are masked as they had no connections to anything and were dead

Graphical.target is loaded and active
Getty.target is loaded and active
Getty-pre.target is loaded and inactive dead
Gdm.service is loaded active and running

Dmesg shows at 12 seconds gnome-shell[4253]: segfault at 20 ... error 4 in libmutter-2.so.0.0 then at 74 seconds;
Resource sanity check: requesting[mem...], which spans more than PCI Bus 0000:00 etc
Then at 1170 seconds ‘caller _nv001112rm... [nvidia] mapping multiple BARs

Journalctl -b shows nothing serious finishing with ‘Reached target Default’ and ‘startup finished in 34ms’

Xorg.0.log is interesting as it shows all is well up to 46 seconds with ‘NVIDIA(GPU-0):’ and then there is a pause to 595 seconds when events start to remove devices such as power button, keyboard etc. At 654 seconds Unloadmodule: “libinput” is quoted several times and NVIDIA(GPU-0): Deleting GPU-0. Finally finishes with Server terminated successfully (0). Closing log file.

Let me know what information to post to help diagnose the issue.

Thank you

Last edited by ajt568 (2018-08-03 17:08:30)

Trilby · 2018-08-03 14:36:15

What do you think is supposed to show? Have you installed and enabled a display manager? Which one? How have you configured it?

If you don't need a display manager (nobody does if you ask me), and xinit works, you can set up autologin and autostarting of X:
https://wiki.archlinux.org/index.php/Xi … X_at_login

V1del · 2018-08-03 14:52:31

Your journal should contain more than that, you might have to run it with sudo/as root explicitly if your user is not in wheel if you don't read anything amiss there. But as that dmesg line you posted already contains a hint towards an issue that has been discussed ad nauseam have you already seen https://bbs.archlinux.org/viewtopic.php … 9#p1796289 e.g.?

Also for the future, rather than paraphrasings and truncated outputs, it'd be much more helpful to post full logs within code tags: https://wiki.archlinux.org/index.php/Co … s_and_code

@Trilby they do mention that GDM is enabled.

Last edited by V1del (2018-08-03 15:02:14)

ajt568 · 2018-08-03 15:29:14

Hello Trilby.
If my system was working as expected there should be a dark grey login screen where I can enter username and password which then puts me into my gnome session. In fact if I wait for the computer to go to sleep then I get the unlock screen to add my password as expected.

I believe I have installed gdm as the display manager. After a startup and before running the xinit command manually, I checked for the active display manager with the command 'cat /etc/systemd/system/display-manager.service | grep '/usr/bin'. The result of the command was 'ExecStart=usr/bin/gdm' which is what I would expect.

Hello V1del.
If I run journal with sudo I do indeed get a lot more information including a core dump. I will look in detail at the link you provide as that may solve my issue.

Without posting the whole journal I can see 'gdm-launch-environment ][999] pam_systemd(gdm-launch-environment:session): Failed to create session: start job for unit user-120.slice failed with 'canceled'. The computer then begins systemd[1]: Starting User Manager for UID 120....
systemdd[1003]: shows pam_unix(systemd-user:session): session opened for use gdm by (uid=0) followed by a significant number of failures to connect such as
systemd[1003]: failed to connect to API bus: connection refused
ultimately there is an output;
gnome-session-binary[972]: Unrecoverable failure in required component org.gnome.Shell.desktop

Thank you for the link.

ajt568 · 2018-08-03 15:50:00

Hello V1del.
I will indeed post the full logs when I get the hang of this. I believed that the solution would be simple.

The link you included does indeed have the solution.

in the configuration file;
/etc/gdm/custom.conf

is the line '#WaylandEnable=false'
for some reason this is commented out in my file. I don't remember changing this file.
When I uncomment the line and reboot, the log in screen returned as expected.

This post is solved thank you. I will update the original post title as solved.

Thank you

Arch Linux

#1 2018-08-03 14:27:32

[SOLVED]Startup stalled at graphical target reached. No login screen.

#2 2018-08-03 14:36:15

Re: [SOLVED]Startup stalled at graphical target reached. No login screen.

#3 2018-08-03 14:52:31

Re: [SOLVED]Startup stalled at graphical target reached. No login screen.

#4 2018-08-03 15:29:14

Re: [SOLVED]Startup stalled at graphical target reached. No login screen.

#5 2018-08-03 15:50:00

Re: [SOLVED]Startup stalled at graphical target reached. No login screen.

Board footer