This is strange and I wasn't sure which component to file this under. When moving or copying files, especially into or within ~/.local/share/applications, Dolphin will usually freeze until ~/.cache is deleted. The freezes occur both when copying/cutting & pasting from Dolphin's context menu, and when using mv or cp from the terminal while Dolphin is open. Kate started randomly freezing around the same time, but this is much more random and I haven't been able to figure out under what circumstances it happens. In both cases, /var/logs/warn shows entries regarding ksycoca's database being corrupted. If left alone, kwin eventually crashes, otherwise deleting ~/.cache sets things back to normal. Other applications generally remain responsive, but new applications can't be opened.
STEPS TO REPRODUCE
1. Move or copy a file via Dolphin's context menu or using mv/cp in the terminal
Dolphin freezes, system performance slows down until eventually kwin crashes. Log shows something like this:
2021-10-27T20:16:51.728325+03:00 no-bueno kstart5: kf.service.sycoca: Couldn't lock "/home/chris/.cache/ksycoca5_en_Jqcej_lUhG54bWkXI2aMdZrI3EA=.lock"
2021-10-27T20:16:51.938125+03:00 no-bueno dolphin: kf.service.sycoca: QThread(0x563b67155050) error detected in factory 0x563b6745d700
2021-10-27T20:16:51.938318+03:00 no-bueno dolphin: kf.service.sycoca: ERROR: KSycoca database corruption!
2021-10-27T20:16:55.527783+03:00 no-bueno dolphin: Could not remove our own lock file "/home/chris/.cache/ksycoca5_en_Jqcej_lUhG54bWkXI2aMdZrI3EA=.lock" maybe permissions changed meanwhile?
2021-10-27T20:16:59.671443+03:00 no-bueno kded5: kf.service.sycoca: QThread(0x55f1a233bcc0) error detected in factory 0x55f1a49046e0
2021-10-27T20:16:59.671646+03:00 no-bueno kded5: kf.service.sycoca: ERROR: KSycoca database corruption!
Normal file moving operations.
Linux/KDE Plasma: OpenSuse Tumbleweed (20211027 snapshot)
(available in About System)
KDE Plasma Version: 5.23.1
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
Can you attach a backtrace of the crash? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
(In reply to Nate Graham from comment #1)
> Can you attach a backtrace of the crash? See
I haven't been able to get a backtrace. I've run Dolphin from gdb and it freezes to the point that I can't open up anything, whereas before I could generally interact with other open applications. It never gets to a crash, though, so gdb doesn't actually take the backtrace. Is there anything else I can send that would be useful, or is there a workaround to get a backtrace from Dolphin, or kwin or anything else that might show something? I can still go into tty so I can access logs, etc. Sorry, I guess it's pretty apparent that I haven't done this before.
Created attachment 143561 [details]
Created attachment 143562 [details]
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.
For more information about our bug triaging procedures please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.
Thank you for helping us make KDE software even better for everyone!
After applying some basic critical thinking, I realized that this problem arises from having several thousand .desktop files in ~/.local/share/applications. Moving these solved everything. Apologies for any time wasted on this.
*** This bug has been marked as a duplicate of bug 358231 ***