Bug 437381 - Slow login when network is down
Summary: Slow login when network is down
Status: REPORTED
Alias: None
Product: frameworks-kded
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 5.82.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords: efficiency-and-performance
Depends on:
Blocks:
 
Reported: 2021-05-19 22:32 UTC by Björn Lindqvist
Modified: 2025-07-13 18:29 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Björn Lindqvist 2021-05-19 22:32:30 UTC 
There is about a two-minute delay for me from sddm login until KDE shows the desktop if the network is not enabled. The delay seem to be related to "kf.auth". Here are what I think are the relevant lines from the system log:

    maj 20 00:11:58 mydesktop kded5[867]: bluedevil: Bluetooth operational changed false
    maj 20 00:11:58 mydesktop kded5[867]: bluedevil: ObexManager operational changed false
    maj 20 00:11:58 mydesktop dbus-daemon[764]: [session uid=1000 pid=764] Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' requested by ':1.8' (uid=1000 pid=8>
    maj 20 00:11:58 mydesktop systemd[722]: Starting Bluetooth OBEX service...
    maj 20 00:11:58 mydesktop kded5[867]: Known activities: ("4567013d-818c-4a11-aa9d-0960df693090")
    maj 20 00:11:58 mydesktop kded5[867]: kf.bluezqt: PendingCall Error: "Unit dbus-org.bluez.service not found."
    maj 20 00:11:58 mydesktop kded5[867]: Registering ":1.27/StatusNotifierItem" to system tray
    maj 20 00:11:58 mydesktop obexd[1278]: OBEX daemon 5.58
    maj 20 00:11:58 mydesktop dbus-daemon[764]: [session uid=1000 pid=764] Successfully activated service 'org.bluez.obex'
    maj 20 00:11:58 mydesktop systemd[722]: Started Bluetooth OBEX service.
    ...
    maj 20 00:14:01 mydesktop kded5[867]: kf.auth: "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."

The "Did not receive reply" line indicates that it waits for something it shouldn't wait for.