Delayed display of wallpaper, desktop icons, conky and task bar

After last update I see a nameable delay of many seconds after login (Plasma Login Manager used). I use KDE Plasma on testing branch with Intel CPU.

Here is the

journalctl log
Nov 01 12:57:49 wollies-pc systemd[963]: Starting Portal service...
Nov 01 12:57:49 wollies-pc systemd[963]: Starting flatpak document portal service...
Nov 01 12:57:49 wollies-pc systemd[963]: Started flatpak document portal service.
Nov 01 12:57:49 wollies-pc /usr/lib/xdg-desktop-portal[1304]: Choosing gtk.portal for org.freedesktop.impl.portal.Lockdown as a last-resort fallback
Nov 01 12:57:49 wollies-pc systemd[963]: Starting Portal service (GTK/GNOME implementation)...
Nov 01 12:57:49 wollies-pc systemd[963]: Started Portal service (GTK/GNOME implementation).
Nov 01 12:57:49 wollies-pc systemd[963]: Starting Xdg Desktop Portal For KDE...
Nov 01 12:57:49 wollies-pc systemd[963]: Started Xdg Desktop Portal For KDE.
Nov 01 12:58:12 wollies-pc ksecretd[976]: Failed to register with host portal QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")
Nov 01 12:58:12 wollies-pc polkit-kde-authentication-agent-1[1111]: Failed to register with host portal QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")
Nov 01 12:58:12 wollies-pc kactivitymanagerd[1098]: Failed to register with host portal QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")
Nov 01 12:58:13 wollies-pc kdeconnectd[1250]: Failed to register with host portal QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")
Nov 01 12:58:14 wollies-pc org_kde_powerdevil[1114]: Failed to register with host portal QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")
Nov 01 12:58:14 wollies-pc xdg-desktop-portal-kde[1380]: Failed to register with host portal QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")
Nov 01 12:58:14 wollies-pc systemd[963]: Started Portal service.
Nov 01 12:58:14 wollies-pc polkit-kde-authentication-agent-1[1111]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Unable to open /proc/1111/root")
Nov 01 12:58:14 wollies-pc ksecretd[976]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
Nov 01 12:58:14 wollies-pc org_kde_powerdevil[1114]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
Nov 01 12:58:14 wollies-pc kdeconnectd[1250]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
Nov 01 12:58:14 wollies-pc xdg-desktop-portal-kde[1380]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
Nov 01 12:58:14 wollies-pc kactivitymanagerd[1098]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.ActivityManager'")
Nov 01 12:58:17 wollies-pc xembedsniproxy[1115]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.xembedsniproxy'")
Nov 01 12:58:17 wollies-pc xembedsniproxy[1115]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.xembedsniproxy'")
Nov 01 12:58:17 wollies-pc gmenudbusmenuproxy[1106]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.gmenudbusmenuproxy'")
Nov 01 12:58:17 wollies-pc gmenudbusmenuproxy[1106]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.gmenudbusmenuproxy'")
Nov 01 12:58:17 wollies-pc kaccess[1107]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
Nov 01 12:58:17 wollies-pc kded6[1034]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
Nov 01 12:58:18 wollies-pc plasmashell[1040]: Failed to register with host portal QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.")
Nov 01 12:58:18 wollies-pc plasmashell[1040]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID")
Nov 01 13:02:47 wollies-pc baloo_file_extractor[2241]: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: App info not found for 'org.kde.baloo'")

Something with with Xdg Desktop Portal seems to be borked on my system.

I tried to completely clean the cache, stopped conky at boot - all to no avail.

$ pacman -Qs xdg-desktop-portal
local/xdg-desktop-portal 1.22.1-2
    Desktop integration portals for sandboxed apps
local/xdg-desktop-portal-gtk 1.15.3-2
    A backend implementation for xdg-desktop-portal using GTK
local/xdg-desktop-portal-kde 6.8.2-1 (plasma)
    A backend implementation for xdg-desktop-portal using Qt/KF5
Relevant inxi output
System: 
  Kernel: 6.18.60-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 16.2.1 
    clocksource: tsc avail: hpet,acpi_pm 
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.18-x86_64 
    root=UUID=802dbc30-0fee-4b5f-bad6-8920905c38b7 rw quiet loglevel=3 
    systemd.show_status=auto rd.udev.log_level=3 apparmor=1 security=apparmor 
    nowatchdog nmi_watchdog=0 x86_energy_perf_policy=performance 
  Desktop: KDE Plasma v: 6.8.2 tk: Qt v: N/A info: frameworks v: 6.31.0 
    wm: kwin_wayland vt: 2 dm: N/A Distro: Manjaro base: Arch Linux

Are there any phantom volume mounts in /etc/fstab that you have forgotten about?

As long as this is still suported:

tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0

then - no.

A lot of failures that might possibly have some relevance:

Maybe baloo is delivering the slow down symptoms;
is there any improvement if you disable it?

Looks like this has raised its ugly head previously:

It probably needs fixing, but I never found a solution other than disabling baloo - which I have done.


I only have it set up in my very small home directory. I’ll give it a try.

Update (after switching it off): Still 23 seconds to wait.

It is supported, because everything in /etc/fstab will be mounted with the listed options, and with all of the default options for the specified filesystem type which have not been overridden by explicitly listed mount options.

For that matter, the defaults mount option isn’t really necessary if there are yet other listed mount options. It is only required if it is the only listed mount option, because then it takes on the role of a placeholder, given that /etc/fstab is a database of records with whitespace-separated fields. :wink:

That all said, it is not necessary to have /tmp explicitly listed in /etc/fstab in Arch-derivative distributions[1], because systemd will itself already set up /tmp as a tmpfs before it parses /etc/fstab.


  1. It is required in (Open)SUSE, because their systemd configuration does not set up /tmp as a tmpfs. ↩︎

Seth (Arch) has their take on the warning messages, here – I can’t yet find any direct reference to slow downs resulting from them – a herring of the red colour, maybe.


Do you get a similar delay when using sddm?

Yes, exactly the same waiting time.

Update: Now back on Plasma Login Manager

Perhaps it is the new norm.

Startup applications might be something to check; and that any custom services are still loading as expected; though, I’d presume you have already ruled those out.


This thread has an unexpected resolution from the OP: :point_down:

It seems that replacing pulseaudio with pipewire fixed the problem also for me. Marking as solved, thanks to everybody for the help!

$ systemd-analyze critical-chain

graphical.target @2.860s 
└─multi-user.target @2.860s 
  └─cups.service @2.822s +37ms
    └─network.target @2.821s 
      └─NetworkManager.service @2.461s +359ms
        └─basic.target @2.460s 
          └─dbus-broker.service @2.434s +26ms
            └─dbus.socket @2.425s +32us
              └─sysinit.target @2.423s 
                └─snapd.apparmor.service @1.734s +688ms
                  └─apparmor.service @315ms +1.401s
                    └─systemd-journald.socket 
                      └─system.slice 
                        └─-.slice

This looks OK. I have switched off all autostart programs to no avail.

Have you cleaned out ~/.cache? (Must be done while logged out of the GUI.)

Yes, done after logging out.

To be honest, I’m a little hesitant about whether I want to try this. Is it possible to reliably undo it?

Just

$ sudo pacman -Syu manjaro-pipewire

to install? How to revert if needed?

Yes, it is.

First check whether you have manjaro-pulse installed. It’s a meta-package. If you don’t have it installed, then installing it might make it easier to go back and forth, because in order to switch, you would uninstall manjaro-pulse and install manjaro-pipewire (with pacman). And going back would then simply be the reverse operation.

For a long time, I myself was loath to switch over, but a while ago — I can’t remember when, but I’m sure it was this year — I made the switch, and I had zero problems doing so.

OK, thanks for the details. I would have thought just installing manjaro-pipewire would be enough. So then, let’s go with:

$ sudo pacman -R manjaro-pulse
$ sudo pacman -Syu manjaro-pipewire

:crossed_fingers:

That replacing pulseaudio with pipewire seemed to resolve their issue might be purely coincidental – but, at least two have made the claim – nothing ventured, nothing gained, as is said.

That’s my understanding. one necessarily conflicts with the other, and pacman offers to replace it.

I have to allow removal of

pulseaudio-zeroconf
pulseaudio

as conflicting packages.

Then: aborted as pulseaudio-bluetooth is still there…
After removal it has been successful.

It installed:

  • manjaro-pipewire
  • alsa-card-profiles
  • libmysofa
  • pipewire-audio
  • gst-plugin-pipewire
  • pipewire-alsa
  • pipewire-pulse

That’s okay, because manjaro-pipewire will pull in the pipewire-native replacements for those things.

No longer needed. :wink:

Thank you both so much, system is fast in operation again. :hugs: