[Solved] More than two minutes gap before Plasma appears after login

SanskritFritz · 2022-10-29 21:19:18

This one is going on for months already. I don't know exactly when it started so I can't say from what version.
The problem: after login from LightDM (also tried SDDM) I get only the LightDM wallpaper and the mouse cursor for more than 2 minutes and then Plasma starts normally (with splashscreen and all). Everything seems to work normally then, this is why I waited months before this post, hoping that an upgrade would solve this.
This gap doesn't happen always at every login, but most of the time. There are several users using this box, all have the same problem.
I saved the journal today for my login at exactly 21:43:00 and Plasma appearing at 21:45:12.
http://ix.io/4eq0
There is a clear 2 minutes gap from 21:43:11 to 21:45:11 and I have no idea why. UID 967 is the lightdm user.
I have Nvidia videocard. The same problem occurs with the nvidia driver or with nouveau.
I haven't tried another DE, we all use Plasma on X exclusively. Nor have I tried Wayland.
.xsession-errors is empty, Xorg.0.log shows no errors.
Google was not helpful to me, or I searched wrong.
Please help me solving this.

Last edited by SanskritFritz (2024-10-13 10:35:57)

Zod · 2022-10-29 22:53:41

You have an encrypted filesystem?

Could it be lack of entropy?

seth · 2022-10-30 07:20:51

Exactly 2 minutes is suspicious, though.
Notably if it's consistent.
And what do we get right after the pause?

okt 29 21:45:11 frank-desktop dbus-daemon[133934]: [session uid=1000 pid=133934] Activating via systemd: service name='org.freedesktop.portal.Desktop' unit='xdg-desktop-portal.service' requested by ':1.3' (uid=1000 pid=134039 comm="/usr/bin/kapplymousetheme material_light_cursors 3")
okt 29 21:45:11 frank-desktop systemd[133914]: Starting Portal service...
okt 29 21:45:11 frank-desktop dbus-daemon[133934]: [session uid=1000 pid=133934] Activating via systemd: service name='org.freedesktop.portal.Documents' unit='xdg-document-portal.service' requested by ':1.4' (uid=1000 pid=134042 comm="/usr/lib/xdg-desktop-portal")
okt 29 21:45:11 frank-desktop systemd[133914]: Starting flatpak document portal service...
okt 29 21:45:11 frank-desktop dbus-daemon[133934]: [session uid=1000 pid=133934] Activating via systemd: service name='org.freedesktop.impl.portal.PermissionStore' unit='xdg-permission-store.service' requested by ':1.5' (uid=1000 pid=134046 comm="/usr/lib/xdg-document-portal")

flatschpak… which is known to cause these timeouts.
=> get rid of flatpak and all xdg-portal* packages and see whether the issue remains - you can also try to just mask all related user services, https://bbs.archlinux.org/viewtopic.php … 4#p1954864

SanskritFritz · 2022-10-30 09:01:38

Thank you seth, that was the solution.

SanskritFritz · 2022-10-31 20:20:28

Sorry I was too quick to report and mark this as solved, I did what you proposed, and rebooted and ran into the rare occasion when the timeout didn't occur. But subsequent logins still have the same effect. Most of the time this actually happens even right at the first login after boot.
So please, any more ideas?

Zod, yes, I have full disk encryption but I don't think I need entropy after the disk was unlocked.

Last edited by SanskritFritz (2022-10-31 20:22:32)

seth · 2022-10-31 20:57:20

Pattern: is the gap always exactly two minutes?
What does an updated journal for such gap look like?

SanskritFritz · 2022-10-31 21:51:03

Here is the most recent journal: http://ix.io/4eDv
There is the gap, this time not exactly 2 minutes (22:29:12 - 22:31:15).

seth · 2022-11-01 13:02:45

There's no indication of what's taking up the time - the lightdm runtime dir getstake down and ~2m later the system user daemon reloads (starts)
=>

I haven't tried another DE

See whether you can reproduce the issue w/ eg. an openbox session (so we get at least an idea where to look at…)

SanskritFritz · 2022-11-01 15:24:59

I started experimenting, and here's what I've got so far:
* Anything started from LightDM (Plasma, KDE/Openbox, Openbox standalone) has the 2 mins gap.
* However, stopping LightDM and using startx works well without any gaps. I've tried with several users right after another and no wait was necessary, Plasma got started in an instant even when started simultaneously on different VC's.
So right now I disabled LightDM and use startx as a workaround but still would like to fix the issue. Seemingly LightDM is the culprit but as I mentioned, using SDDM I have the same problem.

seth · 2022-11-01 15:47:38

What do the lightdm and sddm related files in /etc/pam.d/ look like?
Also, on a hunch:

pacman -Qkk pambase

SanskritFritz · 2022-11-01 16:19:16

root@frank-desktop ~# pacman -Qkk pambase                               
pambase: 8 total files, 0 altered files

I haven't changed anything in /etc/pam.d/ (afaik).

seth · 2022-11-01 19:44:09

seth wrote:

What do the lightdm and sddm related files in /etc/pam.d/ look like?

(If you post them, I don't have to download the packages and look

cfr · 2022-11-02 01:25:26

These are the defaults for sddm. (I'm curious, but not curious enough to download lightdm.)

sddm:

#%PAM-1.0

auth            include         system-login
-auth           optional        pam_gnome_keyring.so
-auth   optional  pam_kwallet5.so

account         include         system-login

password        include         system-login
-password       optional        pam_gnome_keyring.so use_authtok

session         optional        pam_keyinit.so force revoke
session         include         system-login
-session                optional        pam_gnome_keyring.so auto_start
-session  optional  pam_kwallet5.so auto_start

sddm-autologin

#%PAM-1.0
auth        required    pam_env.so
auth        required    pam_faillock.so preauth
auth        required    pam_shells.so
auth        required    pam_nologin.so
auth        required    pam_permit.so
-auth       optional    pam_gnome_keyring.so
-auth       optional    pam_kwallet5.so
account     include     system-local-login
password    include     system-local-login
session     include     system-local-login
-session    optional    pam_gnome_keyring.so auto_start
-session    optional    pam_kwallet5.so auto_start

sddm-greeter

#%PAM-1.0

# Load environment from /etc/environment and ~/.pam_environment
auth            required pam_env.so

# Always let the greeter start without authentication
auth            required pam_permit.so

# No action required for account management
account         required pam_permit.so

# Can't change password
password        required pam_deny.so

# Setup session
session         required pam_unix.so
session         optional pam_systemd.so

seth · 2022-11-02 07:35:37

Obviously pam_gnome_keyring.so & pam_kwallet5.so (and given the OP runs KDE likely pam_kwallet5.so), but I'd check whether they're in the lightdm pam.

SanskritFritz · 2022-11-02 12:06:49

/etc/pam.d/lightdm

#%PAM-1.0
auth        include     system-login
-auth       optional    pam_gnome_keyring.so
account     include     system-login
password    include     system-login
session     include     system-login
-session    optional    pam_gnome_keyring.so auto_start

/etc/pam.d/lightdm-autologin

#%PAM-1.0
auth        required    pam_env.so
auth        required    pam_faillock.so preauth
auth        required    pam_shells.so
auth        required    pam_nologin.so
auth        [success=1 default=ignore]  pam_succeed_if.so user ingroup autologin
auth        required    pam_unix.so
auth        required    pam_permit.so
-auth       optional    pam_gnome_keyring.so
account     include     system-local-login
password    include     system-local-login
session     include     system-local-login
-session    optional    pam_gnome_keyring.so auto_start

/etc/pam.d/lightdm-greeter

#%PAM-1.0

# Load environment from /etc/environment and ~/.pam_environment
auth      required pam_env.so

# Always let the greeter start without authentication
auth      required pam_permit.so

# No action required for account management
account   required pam_permit.so

# Can't change password
password  required pam_deny.so

# Setup session
session   required pam_unix.so
session   optional pam_systemd.so

seth · 2022-11-02 12:12:01

Do you have

pacman -Qi gnome-keyring

?

SanskritFritz · 2022-11-02 12:14:14

No, I don't have gnome-keyring installed.

UPDATE: installing gnome-keyring didn't help.

Last edited by SanskritFritz (2022-11-02 17:12:19)

seth · 2022-11-03 12:27:54

Yeah, no - I'd rather have suspected it to be the offender.
If it's not the DM, not PAM, not the DE…
Any suspicious/custom user units, particualiry ones that are X11 dependent?

systemctl --user list-units --type=service --no-legend

SanskritFritz · 2022-11-03 18:30:49

frank@frank-desktop ~> systemctl --user list-units --type=service --no-legend
  app-geoclue\x2ddemo\x2dagent@autostart.service  loaded active running Geoclue Demo agent
  app-kaccess@autostart.service                   loaded active running Accessibility
  app-kupfer@autostart.service                    loaded active running Kupfer
  app-org.kde.kalendarac@autostart.service        loaded active running Calendar Reminders
  app-org.kde.kdeconnect.daemon@autostart.service loaded active running KDE Connect
  app-quasselclient@autostart.service             loaded active running Quassel IRC (Client only)
  app-syncthingtray@autostart.service             loaded active running Syncthing Tray
  app-xscreensaver@autostart.service              loaded active running Xscreensaver
  at-spi-dbus-bus.service                         loaded active running Accessibility services bus
  dbus.service                                    loaded active running D-Bus User Message Bus
  dconf.service                                   loaded active running User preferences database
  gvfs-daemon.service                             loaded active running Virtual filesystem service
  gvfs-udisks2-volume-monitor.service             loaded active running Virtual filesystem service - disk device monitor
  obex.service                                    loaded active running Bluetooth OBEX service
  plasma-gmenudbusmenuproxy.service               loaded active running Proxies GTK DBus menus to a Plasma readable format
  plasma-kactivitymanagerd.service                loaded active running KActivityManager Activity manager Service
  plasma-kded.service                             loaded active running KDE Daemon
  plasma-kglobalaccel.service                     loaded active running KDE Global Shortcuts Server
  plasma-kscreen.service                          loaded active running KScreen
  plasma-ksmserver.service                        loaded active running KDE Session Management Server
  plasma-ksystemstats.service                     loaded active running Track hardware statistics
  plasma-kwin_x11.service                         loaded active running KDE Window Manager
  plasma-plasmashell.service                      loaded active running KDE Plasma Workspace
  plasma-polkit-agent.service                     loaded active running KDE PolicyKit Authentication Agent
  plasma-powerdevil.service                       loaded active running Powerdevil
  plasma-xembedsniproxy.service                   loaded active running Handle legacy xembed system tray icons
  pulseaudio.service                              loaded active running Sound Service
  spotifyd.service                                loaded active running A spotify playing daemon

Woa, I didn't even know what that "Geoclue Demo agent" was...

seth · 2022-11-03 19:55:52

Many of those are probably plasma triggered - since the DE isn't relevant, have a look in an openbox session.
If you don't rely on GTK's a11y stuff, try to globally "export NO_AT_BRIDGE=1" to prevent at-spi-dbus-bus.service (just a hunch)

syncthing might be nasty…

SanskritFritz · 2022-11-04 15:35:19

I write this from a very empty Openbox session (no tray, nothing), after the 2 mins gap:

frank@frank-desktop ~> systemctl --user list-units --type=service --no-legend
● app-syncthingtray@autostart.service loaded failed failed  Syncthing Tray
  at-spi-dbus-bus.service             loaded active running Accessibility services bus
  dbus.service                        loaded active running D-Bus User Message Bus
  dconf.service                       loaded active running User preferences database
  gvfs-daemon.service                 loaded active running Virtual filesystem service
  obex.service                        loaded active running Bluetooth OBEX service
● plasma-kded.service                 loaded failed failed  KDE Daemon
  pulseaudio.service                  loaded active running Sound Service

About Syncthing: it gets started right at boot.

root@frank-desktop ~# systemctl status syncthing@frank
● syncthing@frank.service - Syncthing - Open Source Continuous File Synchronization for frank
     Loaded: loaded (/usr/lib/systemd/system/syncthing@.service; enabled; preset: disabled)
     Active: active (running) since Wed 2022-11-02 18:10:49 CET; 1 day 22h ago

In .bashrc

export NO_AT_BRIDGE=1

didn't help either.

Last edited by SanskritFritz (2022-11-04 15:50:21)

seth · 2022-11-04 16:01:28

In .bashrc

is too late and at-spi-dbus-bus.service probably still running?

SanskritFritz · 2022-11-04 16:37:33

I tried
/etc/envionment

NO_AT_BRIDGE=1

but that didn't help either.

cfr · 2022-11-04 21:17:08

Why are those two services failing?

SanskritFritz · 2022-11-05 08:33:43

cfr wrote:

Why are those two services failing?

Because I started a bare bones Openbox session with no system tray.

Arch Linux

#1 2022-10-29 21:19:18

[Solved] More than two minutes gap before Plasma appears after login

#2 2022-10-29 22:53:41

Re: [Solved] More than two minutes gap before Plasma appears after login

#3 2022-10-30 07:20:51

Re: [Solved] More than two minutes gap before Plasma appears after login

#4 2022-10-30 09:01:38

Re: [Solved] More than two minutes gap before Plasma appears after login

#5 2022-10-31 20:20:28

Re: [Solved] More than two minutes gap before Plasma appears after login

#6 2022-10-31 20:57:20

Re: [Solved] More than two minutes gap before Plasma appears after login

#7 2022-10-31 21:51:03

Re: [Solved] More than two minutes gap before Plasma appears after login

#8 2022-11-01 13:02:45

Re: [Solved] More than two minutes gap before Plasma appears after login

#9 2022-11-01 15:24:59

Re: [Solved] More than two minutes gap before Plasma appears after login

#10 2022-11-01 15:47:38

Re: [Solved] More than two minutes gap before Plasma appears after login

#11 2022-11-01 16:19:16

Re: [Solved] More than two minutes gap before Plasma appears after login

#12 2022-11-01 19:44:09

Re: [Solved] More than two minutes gap before Plasma appears after login

#13 2022-11-02 01:25:26

Re: [Solved] More than two minutes gap before Plasma appears after login

#14 2022-11-02 07:35:37

Re: [Solved] More than two minutes gap before Plasma appears after login

#15 2022-11-02 12:06:49

Re: [Solved] More than two minutes gap before Plasma appears after login

#16 2022-11-02 12:12:01

Re: [Solved] More than two minutes gap before Plasma appears after login

#17 2022-11-02 12:14:14

Re: [Solved] More than two minutes gap before Plasma appears after login

#18 2022-11-03 12:27:54

Re: [Solved] More than two minutes gap before Plasma appears after login

#19 2022-11-03 18:30:49

Re: [Solved] More than two minutes gap before Plasma appears after login

#20 2022-11-03 19:55:52

Re: [Solved] More than two minutes gap before Plasma appears after login

#21 2022-11-04 15:35:19

Re: [Solved] More than two minutes gap before Plasma appears after login

#22 2022-11-04 16:01:28

Re: [Solved] More than two minutes gap before Plasma appears after login

#23 2022-11-04 16:37:33

Re: [Solved] More than two minutes gap before Plasma appears after login

#24 2022-11-04 21:17:08

Re: [Solved] More than two minutes gap before Plasma appears after login

#25 2022-11-05 08:33:43

Re: [Solved] More than two minutes gap before Plasma appears after login

Board footer