Boot stuck at "Reaching target Graphical Interface"

seth · 2017-10-05 11:50:24

gdm by default runs on wayland - also only the greeter runs in x or wayland, the daemon will likely shut down any existing display server.

The razor device is listed as keyboard and mouse and some xorg configlet must exist to produce the keyboard configuration, check the contents of /etc/X11/xorg.conf.d/*

I'm not sure whether any of those knocks out GDM, but they look suspicious enough (notably given your input trouble in openbox)

custo · 2017-10-05 11:56:56

Ah, I see, so it seems Gnome has generated this config:

Section "InputClass"
    Identifier "system-keyboard"
    MatchIsKeyboard "on"
    Option "XkbLayout" "de,de,us"
    Option "XkbVariant" ",ru,"
EndSection

Prefacing every line with # doesn't resolve the problem.

Last edited by custo (2017-10-05 11:58:10)

custo · 2017-10-05 12:25:25

Ahhhh, my bad. As I mentioned earlier, I had renamed the .xinitrc to .Xinitrc. I thought for some reason the X should be capitalised. In fact, this doesn't seem to be true.

What I thought were a "weird Openbox" was in fact a startx without .xinitrc.

So, actually:
* exec openbox-session looks good
* exec startxfce4 looks good
* exec gnome-session LOOKS GOOD AS WELL (no input problems!)

So I can log into my system. It seems like only GDM is broken?

Last edited by custo (2017-10-05 12:27:02)

seth · 2017-10-05 12:27:19

Did you try https://wiki.archlinux.org/index.php/GD … rg_backend ?

custo · 2017-10-05 12:31:03

Yes but to no avail! It doesn't seem to have any effect.

seth · 2017-10-05 12:32:10

Then the only thing lef is to look up your journal for gdm errors.

custo · 2017-10-05 12:42:42

I found this one:

Oct 05 14:40:12 roshan sudo[1635]:   niklas : TTY=tty6 ; PWD=/home/niklas ; USER=root ; COMMAND=/usr/bin/systemctl start gdm
-- Subject: Unit gdm.service has begun start-up
-- Unit gdm.service has begun starting up.
-- Subject: Unit gdm.service has finished start-up
-- Unit gdm.service has finished starting up.
Oct 05 14:40:12 roshan systemd[1]: Created slice User Slice of gdm.
Oct 05 14:40:12 roshan systemd-logind[335]: New session c3 of user gdm.
-- Subject: A new session c3 has been created for user gdm
-- A new session with the ID c3 has been created for the user gdm.
Oct 05 14:40:12 roshan systemd[1]: Started Session c3 of user gdm.
Oct 05 14:40:12 roshan systemd[1647]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0)
Oct 05 14:40:12 roshan systemd[1648]: pam_unix(systemd-user:session): session closed for user gdm
Oct 05 14:40:12 roshan gdm-launch-environment][1642]: pam_systemd(gdm-launch-environment:session): Failed to create session: Start job for unit user@120.service failed with 'failed'
Oct 05 14:40:12 roshan systemd[1]: Removed slice User Slice of gdm.

Google gives me a thread where people suggest to disable Wayland. But I already have WaylandEnable=false in /etc/gdm/custom.conf. Can I be certain that GDM is respecting this?

custo · 2017-10-05 13:17:17

So as a workaround for now I just disabled GDM and use startx manually.

Should I maybe open a more specific thread in the DE forums now that we have nailed it down to GDM?

Also, TIL that GDM is in charge of handling the /etc/xdg/autostart rather than gnome-shell itself. Thus I have to start pulseaudio manually it seems. Is there a better way to do this without GDM?

Thank you so much, seth, for your patience and continued help. I already learned a lot here. Hopefully someone will have an idea how to fix the GDM problem soon.

Slithery · 2017-10-05 14:15:48

Did you copy the skeleton xinitrc to your user home and edit the exec line, or does your xinitrc only contain the exec line?

If the latter then you're doing it wrong, read...
https://wiki.archlinux.org/index.php/Xinit#xinitrc

custo · 2017-10-06 09:09:41

@ slithery: Yes, of course, that was the issue here!

So I got a satisfactory workaround just not using GDM for the moment.

To fix the GDM problem I've opened a more specific thread in the DE forum.

custo · 2017-10-06 11:28:44

Another noob question regarding my workaround: Now that I don't use GDM, gnome-keyring asks me all the time to provide my password. Yesterday it would accept it, but today after changing the .xinitrc to the default skeleton (as suggested by slithery) and rebooting, it would not accept my password any more. It also shows a notice that my password no longer matches the password I use to log in to my computer.

What happened here? I didn't change the password, and the one I'm trying is certainly correct.

Arch Linux

#26 2017-10-05 11:50:24

Re: Boot stuck at "Reaching target Graphical Interface"

#27 2017-10-05 11:56:56

Re: Boot stuck at "Reaching target Graphical Interface"

#28 2017-10-05 12:25:25

Re: Boot stuck at "Reaching target Graphical Interface"

#29 2017-10-05 12:27:19

Re: Boot stuck at "Reaching target Graphical Interface"

#30 2017-10-05 12:31:03

Re: Boot stuck at "Reaching target Graphical Interface"

#31 2017-10-05 12:32:10

Re: Boot stuck at "Reaching target Graphical Interface"

#32 2017-10-05 12:42:42

Re: Boot stuck at "Reaching target Graphical Interface"

#33 2017-10-05 13:17:17

Re: Boot stuck at "Reaching target Graphical Interface"

#34 2017-10-05 14:15:48

Re: Boot stuck at "Reaching target Graphical Interface"

#35 2017-10-06 09:09:41

Re: Boot stuck at "Reaching target Graphical Interface"

#36 2017-10-06 11:28:44

Re: Boot stuck at "Reaching target Graphical Interface"

Board footer