Bug 338107

Summary:	kde config continually corrupting itself
Product:	[I don't know] kde	Reporter:	illumilore <illumilore>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	critical	CC:	ben, cfeck, cherubim.cuber
Priority:	NOR
Version:	4.13.2
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description illumilore 2014-08-07 23:10:00 UTC

After starting up, it will take over 30 seconds after clicking on the start menu in the plasma bar before the menu comes up, if at all, nor will right clicks or attempting to launch applications or anything from the desktop widget. When attempting to launch something using the quick launch, like firefox or dolphin, it will show on the task bar briefly as if loading but it never comes up. Only by deleting the ~/.kde4 folder will it work after reboot, but then it will start happening again later after a reboot.

Reproducible: Always

Comment 1 Christoph Feck 2014-08-08 00:11:22 UTC

> Reproducible: Always

Since when? What did you update? Check /var/log/zypp/history

Comment 2 illumilore 2014-08-08 08:34:05 UTC

Since I installed opensuse 13.1. And it keeps happening through updating kde to the recent release.

I just narrowed it down to the Autostart folder in ~/.kde4 alone. I think a script that launches a program that I tell to autostart starts in the ~/kde4/Autostart folder then eventually puts a log file in the folder it was started from which will cause the problems on the next boot? I am not certain because even though it always happens it seems to be sporadically for creating the log file.

Comment 3 Ben Creasy 2018-02-19 01:16:32 UTC

Over 3 years later, I think this should be downgraded from "Critical", at the very least.

Comment 4 Ben Creasy 2018-02-23 20:35:48 UTC

Targeting KDE 4.13.2 so I'm marking this as unmaintained. Comment if it's still happening with KDE 5.

Comment 5 Nate Graham 2020-09-28 23:45:41 UTC

*** Bug 338947 has been marked as a duplicate of this bug. ***