Summary: | KService rebuild ksycoca5 every several seconds | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kservice | Reporter: | Leslie Zhai <zhaixiang> |
Component: | general | Assignee: | David Faure <faure> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | arojas, bart.polot, g.lassnig, ht990332, kdelibs-bugs, paolo.pedroni, peer.frank, simonandric5, zhaixiang |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kservice/0a719bb93110d125adb0218b3f9bfbe567851ae7 | Version Fixed In: | |
Sentry Crash Report: |
Description
Leslie Zhai
2015-09-16 09:34:17 UTC
Ouch. I'm about to make a 5.14.1 release of KService with this patch added, does it fix your problem? http://www.davidfaure.fr/2015/revert_format_change.diff (for the kservice framework) You wrote v5.4.1, I assume you meant 5.14.0? If the patch doesn't help, can you try moving out the ksycoca5 file; does it then recreate it correctly and stop regenerating it? Hmm, seems to be another issue; I think I see what's happening... KBuildSycoca::checkGlobalHeader -> KSycoca::readSycocaHeader -> KSycocaPrivate::readSycocaHeader -> KSycocaPrivate::checkDatabase -> KSycocaPrivate::checkDirectories -> KSycocaPrivate::buildSycoca, and there we go again..... Git commit 0a719bb93110d125adb0218b3f9bfbe567851ae7 by David Faure. Committed on 16/09/2015 at 21:42. Pushed by dfaure into tag 'v5.14.2'. KBuildSycoca: do not trigger a recreate from readSycocaHeader() (which is itself called from kbuildsycoca) M +1 -1 src/sycoca/ksycoca.cpp http://commits.kde.org/kservice/0a719bb93110d125adb0218b3f9bfbe567851ae7 Hi, I updated from kservice 5.14.0 to 5.14.2 and stuff in ~/.cache/ now keep rebuilding every second. I logged off and cleared ~/.cache and logged back in. It still rebuilds every second. I downgraded to 5.14.0, logged off, cleared ~/.cache and logged back in. It no longer rebuilds every second. Basically 5.14.0 works but 5.14.2 is broken. I don't follow; the bug report was for 5.14.0 in the first place.... If you upgrade again, is the problem still there? Yes, it does. There is bug about it in the distribution I use as well https://bugs.archlinux.org/task/46320 (In reply to David Faure from comment #1) > Ouch. > > I'm about to make a 5.14.1 release of KService with this patch added, does > it fix your problem? > > http://www.davidfaure.fr/2015/revert_format_change.diff > (for the kservice framework) > > You wrote v5.4.1, I assume you meant 5.14.0? Sorry, typo ;P 5.14.0 rpm -q kf5-kservice kf5-kservice-5.14.0-2.x86_64 > > If the patch doesn't help, can you try moving out the ksycoca5 file; does it > then recreate it correctly and stop regenerating it? I git pull from git@git.kde.org:kservice master branch, and I saw your commit ;-) https://quickgit.kde.org/?p=kservice.git&a=commit&h=87e346092d7d50b25ef930bbdb2effe6d9a103e4 I developed a monkey patch for myself yesterday ;P to limit rebuild times when checkTimestamps is not able to work correctly. PS: I installed my Linux box in a future datetime, for example, 2025-09-16, then I experienced such issue - every components of plasma-desktop and workspace freeze~ today I rebuilt the latest git commit, it is OK now ;-) Thank David`s cool job! Regards, Leslie Zhai - a KDE developer is kservice 5.14.2 available to the public ? Is the bug related to setting time, apparently not many are affected? kservice 5.14.3 is available and works (unlike 5.14.2). The bug is not related to setting time. This (or something related) keeps happening in 5.14.3, on Arch, on a user that used kde4 before. On a clean install on a different system it does not happen. Started after (by mistake) changing the "region" setting to "Germany (nds_DE)". It changes the language to some german dialect (niederdeutsch, I guess from the language code). Deleting the .kde4 directory does not help. It comes up for 1 minute after booting and goes away. As soon as I click on the K-menu, comes back again, changes the language of the menu and brings the system to a halt. Changing the "region" setting to "Deutschland (de_DE)" fixes the problem. |