[SOLVED] Taking a long time to reach the login screen.

Mighty_Pig · 2023-06-08 15:31:57

So to start with I have been having 2 issues for a long time which I have been trying to resolve for a while now without any success. At first the problem was random, sometimes when booting it would never reach the start screen. I just needed to hold the power button to reboot and after a couple of times it would eventually boot normal. Other times it would just boot normally in 1 go. I found out later I was able to switch to tty2. From there I would try to figure out what was wrong. Eventually I tried kwin_x11 --replace. Of course I would get a issue that I wasn't able to start but if I switched back to tty1 I was able to login to my desktop environment. I would get the warning that kwin was unstable and kept crashing unfortunately I tried to search for this issue which I was able to find but nothing that really helped me fix this. Later I just reinstalled kwin, and also plasma-kde. This kind of fixed the issue however booting is now taking a long time. So I did a systemd-analyze blame and I found out that reflector.service took a very long time. So I followed this on the forums and this fixed at least that problem.

However now the output of systemd-analyze is the following:

Startup finished in 20.523s (firmware) + 1.969s (loader) + 2.411s (kernel) + 6.741s (userspace) = 31.645s 
graphical.target reached after 6.741s in userspace.

This would mean the bios (firmware?) takes 20 seconds and after that it should only be the remaining seconds to reach the interface right? However after it has gone through the bios it takes way longer that 20 seconds. It takes somewhere around 1 minute to fully boot.

I honestly don't know whats going wrong. I hope I gave enough information. I'll list my hardware and some software versions which I think are important. If I am forgetting anything please let me know!

Hardware:
Nvidia gtx 3080
AMD ryzen 3800x
MSI b450 gaming pro carbon ac
boot drive is a samsung 970 evo 1tb
I also have another 4tb hdd for /home

Software:
linux 6.3.6.arch1-1
nvidia-dkms 530.41.03-1
kded 5.106.0-1
kwin 5.27.5-2
kwindowsystem 5.106.0-1
plasma-desktop 5.27.5-1
systemd 253.5-1

I also have a dual boot to windows 10.

And here is also the output from journalctl after boot:
http://ix.io/4xLc

The other issue I am having (which I don't think is related but I'll just mention it anyway since I rather give to much information than to little) is that if I try to reboot then it shuts down as it should however then it would get stuck in (I think) the bios. Since I never get the option to select if I want arch or windows. I tried to find a related issue without success.

Any help would be really appreciated and if you need any more information let me know!

Last edited by Mighty_Pig (2023-06-10 08:54:11)

V1del · 2023-06-08 15:38:19

GNOME portal bugs, remove xdg-desktop-portal-gnome (and potentially all of them aside from xdg-desktop-portal-kde)

On further inspection you also have conflicting network services running concurrently. If you want desktop integration, keep NetworkManager but disable systemd-networkd. And make sure iwd is not explicitly enabled, but autostarted by NetworkManager (post

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

and some general weird random stuff that should not be active at the same time generally, like systemd-resolved and Avahi and the like, which instructions did you follow when setting this up.

There's also a teams timeout/crash but I'm suspecting that's due to the portal situation, but maybe try disabling the relevant autostart service for teams as well.

For the occasional failure to reach the login screen you'll want to do: https://wiki.archlinux.org/title/NVIDIA … de_setting -- including the early loading guidance.

Last edited by V1del (2023-06-08 15:51:29)

Mighty_Pig · 2023-06-08 15:56:02

V1del wrote:

GNOME portal bugs, remove xdg-desktop-portal-gnome (and potentially all of them aside from xdg-desktop-portal-kde)
On further inspection you also have conflicting network services running concurrently. If you want desktop integration, keep NetworkManager but disable systemd-networkd. And make sure iwd is not explicitly enabled, but autostarted by NetworkManager (post
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
and some general weird random stuff that should not be active at the same time generally, like systemd-resolved and Avahi and the like, which instructions did you follow when setting this up.
There's also a teams timeout/crash but I'm suspecting that's due to the portal situation, but maybe try disabling the relevant autostart service for teams as well.
For the occasional failure to reach the login screen you'll want to do: https://wiki.archlinux.org/title/NVIDIA … de_setting -- including the early loading guidance.

So I tried to disable the service from Teams which it didn't want me to do. So I just removed it since I don't use it anyways. That fixed the boot time. Now it boots a lot faster. Thank you!

I also disabled the services you suggested and I think that made it a bit faster too.

I used the unofficial Arch Linux GUI installer which I won't be using next time . Probably just gonna do the manual way like I did on my laptop.

But thank you for the help.

I am still having the reboot issue but that might seems more like a hardware issue to me.

Edit: Forgot to add the output of the command:

avahi-daemon.service                     | multi-user.target.wants
avahi-daemon.socket                      | sockets.target.wants
bluetooth.service                        | bluetooth.target.wants
choose-mirror.service                    | multi-user.target.wants
cloud-config.service                     | cloud-init.target.wants
cloud-final.service                      | cloud-init.target.wants
cloud-init-local.service                 | cloud-init.target.wants
cloud-init.service                       | cloud-init.target.wants
cups.path                                | multi-user.target.wants
cups.service                             | printer.target.wants
cups.socket                              | sockets.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.Avahi.service       | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.resolve1.service    | system
dbus-org.freedesktop.timesync1.service   | system
dbus.service                             | system
dbus.service                             | user
default.target                           | system
display-manager.service                  | system
docker.service                           | multi-user.target.wants
getty@tty1.service                       | getty.target.wants
livecd-alsa-unmuter.service              | sound.target.wants
livecd-talk.service                      | multi-user.target.wants
lm_sensors.service                       | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
pacman-init.service                      | multi-user.target.wants
pipewire-media-session.service           | pipewire.service.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
reflector.timer                          | timers.target.wants
remote-fs.target                         | multi-user.target.wants
sshd.service                             | multi-user.target.wants
systemd-resolved.service                 | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
vboxservice.service                      | multi-user.target.wants
xdg-user-dirs-update.service             | default.target.wants

Last edited by Mighty_Pig (2023-06-08 15:57:15)

c00ter · 2023-06-08 17:40:37

Mighty_Pig wrote:

[quote=V1del
I used the unofficial Arch Linux GUI installer which I won't be using next time .

You might want to try the "official" Archinstall routine if you haven't already. It's on every Arch ISO now.

seth · 2023-06-08 19:13:28

jun 08 16:48:54 chromium kernel: Linux version 6.3.6-arch1-1 (linux@archlinux) (gcc (GCC) 13.1.1 20230429, GNU ld (GNU Binutils) 2.40.0) #1 SMP PREEMPT_DYNAMIC Mon, 05 Jun 2023 15:12:57 +0000
jun 08 16:49:00 chromium systemd[1]: Reached target Graphical Interface.
==> jun 08 16:50:32 chromium systemd[1042]: Reached target Current graphical user session.

The main offender is

jun 08 16:49:51 chromium xdg-desktop-por[1084]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.kde: Timeout was reached
jun 08 16:50:16 chromium xdg-desktop-por[1084]: GError set over the top of a previous GError or uninitialized memory.
                                                This indicates a bug in someone's code. You must ensure an error is NULL before it's set.
                                                The overwriting error message was: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gtk: Timeout was reached
jun 08 16:50:16 chromium xdg-desktop-por[1084]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.kde: Timeout was reached
jun 08 16:50:16 chromium xdg-desktop-por[1084]: No skeleton to export
jun 08 16:50:31 chromium systemd[1042]: plasma-kcminit.service: start operation timed out. Terminating.
jun 08 16:50:31 chromium systemd[1042]: xdg-desktop-portal-gtk.service: start operation timed out. Terminating.
jun 08 16:50:31 chromium systemd[1042]: xdg-desktop-portal.service: start operation timed out. Terminating.
jun 08 16:50:31 chromium systemd[1042]: xdg-desktop-portal.service: Failed with result 'timeout'.
jun 08 16:50:31 chromium systemd[1042]: Failed to start Portal service.
jun 08 16:50:31 chromium systemd[1042]: xdg-desktop-portal-gtk.service: Failed with result 'timeout'.
jun 08 16:50:31 chromium systemd[1042]: Failed to start Portal service (GTK/GNOME implementation).
jun 08 16:50:31 chromium systemd[1042]: plasma-kcminit.service: Failed with result 'timeout'.
jun 08 16:50:31 chromium systemd[1042]: Failed to start KDE Config Module Initialization.
jun 08 16:50:31 chromium systemd[1042]: Dependency failed for KDE Configuration Module Initialization (Phase 1).
jun 08 16:50:31 chromium systemd[1042]: plasma-kcminit-phase1.service: Job plasma-kcminit-phase1.service/start failed with result 'dependency'.
jun 08 16:50:31 chromium systemd[1042]: Starting KDE Session Management Server...

and that has nothing to do with the boot.

V1del wrote:

remove xdg-desktop-portal-gnome

Post an updated journal, but

c00ter wrote:

You might want to try the "official" Archinstall routine

This is actually not optional,

I used the unofficial Arch Linux GUI installer which

is not supported here, https://bbs.archlinux.org/misc.php?action=rules

Mighty_Pig · 2023-06-08 19:39:49

Well, the problem wasn't there since I started using the GUI installer so I probably fucked it up myself somehow.

However as I said earlier that it seemed to be gone, I was wrong. After a longer shutdown, I needed to wait a lot longer than just a few seconds again.

I removed all the xdg-desktop-portal-* except the kde one. I also fully removed teams.

Here's the new journalctl

If this won't work I guess I gotta install Arch again.

Since I have all my apps in a differant partition and disk at /home I can keep my data right?

seth · 2023-06-08 19:43:45

jun 08 21:31:59 chromium kernel: Linux version 6.3.6-arch1-1 (linux@archlinux) (gcc (GCC) 13.1.1 20230429, GNU ld (GNU Binutils) 2.40.0) #1 SMP PREEMPT_DYNAMIC Mon, 05 Jun 2023 15:12:57 +0000
jun 08 21:32:07 chromium systemd-logind[605]: New session 1 of user daan.
jun 08 21:32:08 chromium systemd[1]: Reached target Graphical Interface.
=> jun 08 21:33:39 chromium systemd[817]: plasma-kcminit.service: Failed with result 'timeout'.
=> jun 08 21:33:40 chromium systemd[817]: Reached target Current graphical user session.

systemctl --user status plasma-kcminit.service

Edit: I'd start by disabling the autologin and dockerd

Last edited by seth (2023-06-08 19:46:09)

Mighty_Pig · 2023-06-10 08:53:04

seth wrote:

jun 08 21:31:59 chromium kernel: Linux version 6.3.6-arch1-1 (linux@archlinux) (gcc (GCC) 13.1.1 20230429, GNU ld (GNU Binutils) 2.40.0) #1 SMP PREEMPT_DYNAMIC Mon, 05 Jun 2023 15:12:57 +0000
jun 08 21:32:07 chromium systemd-logind[605]: New session 1 of user daan.
jun 08 21:32:08 chromium systemd[1]: Reached target Graphical Interface.
=> jun 08 21:33:39 chromium systemd[817]: plasma-kcminit.service: Failed with result 'timeout'.
=> jun 08 21:33:40 chromium systemd[817]: Reached target Current graphical user session.
systemctl --user status plasma-kcminit.service
Edit: I'd start by disabling the autologin and dockerd

Hey sorry for the late response, I wasn't home to test it fully.

But disabling autologin and dockerd did it! It seems (alteast for now) to be stable and fast with reaching the login screen.
Thank you everyone!

seth · 2023-06-10 12:16:28

See whether you can still auto-login w/o a delay.

Arch Linux

#1 2023-06-08 15:31:57

[SOLVED] Taking a long time to reach the login screen.

#2 2023-06-08 15:38:19

Re: [SOLVED] Taking a long time to reach the login screen.

#3 2023-06-08 15:56:02

Re: [SOLVED] Taking a long time to reach the login screen.

#4 2023-06-08 17:40:37

Re: [SOLVED] Taking a long time to reach the login screen.

#5 2023-06-08 19:13:28

Re: [SOLVED] Taking a long time to reach the login screen.

#6 2023-06-08 19:39:49

Re: [SOLVED] Taking a long time to reach the login screen.

#7 2023-06-08 19:43:45

Re: [SOLVED] Taking a long time to reach the login screen.

#8 2023-06-10 08:53:04

Re: [SOLVED] Taking a long time to reach the login screen.

#9 2023-06-10 12:16:28

Re: [SOLVED] Taking a long time to reach the login screen.

Board footer