https://bugs.kde.org/show_bug.cgi?id=481870
--- Comment #6 from tagwer...@innerjoin.org --- (In reply to Arjen Hiemstra from comment https://bugs.kde.org/show_bug.cgi?id=482082#c7) > Just to collect some extra data, can we the output of `systemd-analyze --user > blame` for those that > can reproduce this bug? While there is something going on with ksplash it'd > be useful to exclude > other things going wrong. That was in the context of the splash screen mak a difference, seems not the case here, the result of "journalctl | grep blue": Mar 01 16:25:56 ... NetworkManager[383]: <info> [1709306756.8001] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-bluetooth.so) Mar 01 16:26:06 ... dbus-daemon[382]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.36' (uid=1000 pid=727 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Mar 01 16:26:31 ... dbus-daemon[382]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Mar 01 16:26:31 ... dbus-daemon[382]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.71' (uid=1000 pid=997 comm="/usr/lib/x86_64-linux-gnu/libexec/kdeconnectd " label="unconfined") Mar 01 16:26:56 ... dbus-daemon[382]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Mar 01 16:26:56 ... kdeconnectd[997]: 2024-03-01T16:26:56 kdeconnect.core: No local bluetooth adapter found and "systemd-analyze --user blame": 1.526s xdg-desktop-portal.service 961ms plasma-kcminit.service 675ms xdg-desktop-portal-gtk.service 319ms plasma-powerdevil.service 188ms plasma-plasmashell.service 184ms pulseaudio.service 181ms plasma-xdg-desktop-portal-kde.service 180ms plasma-polkit-agent.service 144ms plasma-ksmserver.service 134ms plasma-kded6.service 75ms plasma-kactivitymanagerd.service 49ms app-kaccess@autostart.service 47ms app-org.kde.discover.notifier@autostart.service 46ms app-lts_eol@autostart.service 44ms plasma-kwin_wayland.service 43ms app-org.kde.xwaylandvideobridge@autostart.service 43ms plasma-restoresession.service 38ms kde-baloo.service 33ms plasma-kglobalaccel.service 27ms app-geoclue\x2ddemo\x2dagent@autostart.service 19ms plasma-kcminit-phase1.service 15ms session-migration.service 11ms app-org.kde.kdeconnect.daemon@autostart.service 9ms xdg-document-portal.service 7ms dconf.service 7ms xdg-desktop-portal-rewrite-launchers.service 6ms at-spi-dbus-bus.service 4ms app-snap\x2duserd\x2dautostart@autostart.service 3ms xdg-permission-store.service 3ms dbus.socket The "blame" does not look particularly different between systems with the 25 sec bluez timeout and those without. -- You are receiving this mail because: You are watching all bug changes.
