Bug 419213

Summary:	kded hangs during plasma startup
Product:	[Frameworks and Libraries] frameworks-kded	Reporter:	elman
Component:	general	Assignee:	David Faure <faure>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	daniel, kdelibs-bugs
Priority:	NOR
Version:	5.68.0
Target Milestone:	---
Platform:	Manjaro
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description elman 2020-03-25 09:11:32 UTC

SUMMARY

When starting plasma, kded5 hangs and many things don't work. For example I can't connect to wifi, keyboard shortcuts don't work or startup apps don't start.

Only thing that helps me is killing kded5 process and then restarting plasma:

kill -9 <kded5 process>
kquitapp5 plasmashell && kstart5 plasmashell

This occurs on every boot.

journalctl doesn't say much:

=== BOOT ===
mar 25 09:24:51 hostname kded5[1442]: 
mar 25 09:24:51 hostname kded5[1442]: kscreen.kded: PowerDevil SuspendSession action not available!
mar 25 09:24:52 hostname kded5[1442]: bluedevil: Created
mar 25 09:24:53 hostname kded5[1442]: Installing the delayed initialization callback.
mar 25 09:24:54 hostname kded5[1442]: Failed to load GeolocationProvider: "Cannot load library /usr/lib/qt/plugins/plasma-geolocation-gps.so: (libgps.so.25: cannot open shared object file: No such file or directory)"
mar 25 09:24:54 hostname kded5[1442]: "location"
=== PLASMA RESTART ===
mar 25 09:26:39 hostname kded5[4670]: bluedevil: Created
mar 25 09:26:39 hostname kded5[4670]: org.kde.knotifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP
mar 25 09:26:40 hostname kded5[4670]: Installing the delayed initialization callback.
mar 25 09:26:40 hostname kded5[4670]: Failed to load GeolocationProvider: "Cannot load library /usr/lib/qt/plugins/plasma-geolocation-gps.so: (libgps.so.25: cannot open shared object file: No such file or directory)"
mar 25 09:26:40 hostname kded5[4670]: "location"
=== SERVICES START TO WORK ===
mar 25 09:27:30 hostname kded5[4670]: kcm_touchpad: Using X11 backend
mar 25 09:27:30 hostname kded5[4670]: Delayed initialization.
mar 25 09:27:30 hostname kded5[4670]: Reloading the khotkeys configuration
mar 25 09:27:30 hostname kded5[4670]: Version 2 File!
mar 25 09:27:30 hostname kded5[4670]: true
mar 25 09:27:30 hostname kded5[4670]: Imported file "/usr/share/khotkeys/konsole.khotkeys"
mar 25 09:27:30 hostname kded5[4670]: Imported file "/usr/share/khotkeys/konqueror_gestures_kde321.khotkeys"
mar 25 09:27:30 hostname kded5[4670]: Imported file "/usr/share/khotkeys/defaults.khotkeys"
mar 25 09:27:30 hostname kded5[4670]: Imported file "/usr/share/khotkeys/kde32b1.khotkeys"

STEPS TO REPRODUCE
1. Just start my computer

EXPECTED RESULT
All services should start.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro
KDE Plasma Version: 5.18.3
KDE Frameworks Version: 5.68.0
Qt Version: 5.14.1

ADDITIONAL INFORMATION
Is there anything more I can provide to pinpoint this problem?

Comment 1 elman 2020-04-02 08:06:51 UTC

It seems that latest Manjaro update fixed the problem for me.

https://forum.manjaro.org/t/stable-update-2020-04-01-xfce-calibre-xorg-server-systemd-pamac-haskell-python/133005

However there were no packages directly connected to KDE - no Plasma, no Frameworks, no KDE Apps...

Comment 2 Christoph Feck 2020-04-14 14:09:49 UTC

Thanks for the update; changing status.

Unless there is further information, let's assume it was a problem in a lower level package.

Comment 3 elman 2020-05-07 10:58:46 UTC

This issue just keeps getting back. Sometimes I have no problems for a week and then it returns.

Just today I left my notebook and when I got back after 45 minutes everything was frozen and I was unable wake the computer. Mouse and keyboard didn't respond. So I reset the notebook and on next boot kded hanged again. 

Maybe some configuration file got broken during hard reboot?

Comment 4 elman 2020-05-12 07:34:57 UTC

This issue might be related to proxy setting. I used "Detect proxy configuration automatically". When I switched to "No Proxy" and restarted, plasma started just fine.

My network config is that when I connect directly, I have no proxy. Then I connect to VPN and I use proxy only available within VPN. Could it be that VPN proxy config is saved and when computer is restarted, Plasma tries to use proxy which is not available and therefore hags?

Comment 5 Daniel Albers 2022-08-12 23:38:32 UTC

#449984 is newer, but has more useful debugging info.

*** This bug has been marked as a duplicate of bug 449984 ***