Bug 496971

Summary:	plasmashell freezes for ~15 seconds shortly after logging in
Product:	[Plasma] plasmashell	Reporter:	Avraham Hollander <anhollander516>
Component:	generic-performance	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	anhollander516, kdedev
Priority:	NOR
Version First Reported In:	6.2.4
Target Milestone:	1.0
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Avraham Hollander 2024-12-03 03:37:11 UTC

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY
When logging in, plasmashell freezes after few seconds, and then unfreezes and works perfectly fine after 10-15 seconds.

STEPS TO REPRODUCE
2. Log in
3. interact with plasmashell in the next 30 seconds

OBSERVED RESULT
It is responsive for a moment, but then freezes, and then becomes responsive again

EXPECTED RESULT
No freezing

SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux 2.17
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.1
Kernel Version: 6.12.1-20R5-sched-ext (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-10310U CPU @ 1.70GHz
Memory: 7.5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics

ADDITIONAL INFORMATION
I can't reproduce this on my relatively similarly configured desktop. Only on my laptop's installation. The bug survived a world rebuild.

Comment 1 Avraham Hollander 2025-02-19 21:52:22 UTC

Ok so looking at htop there is a strange instance of kded6 and dbus-daemon that don't consume any resident memory. They have an empty  /proc/$PID/cmdline, which makes absolutely no sense. Once they terminate, the system becomes responsive again.

I switched the systemd to systemd, and now using the systemd-based startup, the bug is no longer present. But I wouldn't call it fixed. I'm leaving this open for anyone else who ever has the same problem.

Comment 2 Bug Janitor Service 2025-03-06 03:47:22 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 3 TraceyC 2025-03-06 17:11:29 UTC

Closing for now since there's been no recurrence. so far. If this recurs on your system, feel free to reopen this report.

If anyone still has this issue, please open a new bug report with your current system information. thanks.