Bug 429196 - kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated message makes system lags.
Summary: kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated ...
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.20.4
Platform: Mageia RPMs Linux
: NOR minor
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-16 14:00 UTC by Aurélien Oudelet (auroud85_fr)
Modified: 2021-03-09 15:42 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
aoudelet: X11+


Attachments
plasmashell starting console output (19.15 KB, text/plain)
2020-11-16 14:00 UTC, Aurélien Oudelet (auroud85_fr)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aurélien Oudelet (auroud85_fr) 2020-11-16 14:00:55 UTC
Created attachment 133381 [details]
plasmashell starting console output

plasmashell starts with too many warning-level debug outputs.

Most notable since Plasma 5.20.x series is:
kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated
kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated
kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated
kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated

which is triggered each time the mouse pointer hovers Icon and items in taskbar panel, like Shortcut to Application pinned in panel, even in icon-only-taskmanager.

This introduces lags in overall impression.
Added a text file when you trigger "plasmashell --replace &" in a Terminal (Konsole).

As you can see below, my system is particular fast but as I use a classical old-like hard-drive (and not a SSD) to my /var partition, I can listen write access each time my mouse is moved in Plasmashell. That's not a good solution in the long term.

I could set this environment variable in /etc/environment:
QT_LOGGING_RULES='*=false'

But this not a satisfactory situation.

SOFTWARE/OS VERSIONS
Operating System: Mageia 8
KDE Plasma Version: 5.20.3
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1
Kernel Version: 5.9.8-desktop-1.mga8
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz
Memory: 15.6 Gio of RAM
Graphics Processor: GeForce GTX 1660 Ti/PCIe/SSE2
Comment 1 Aurélien Oudelet (auroud85_fr) 2020-12-28 09:45:35 UTC
In facts, removing KDE/Plasma related contents inside ~/.cache, ~/.config, ~/.kde
resolve the issue here.
I really don't know where exactly as I used great means...

Leaving this opened, as long as our Mageia users don't have migrated from Mageia 7 (Plasma 5.15) to Mageia 8 (Plasma 5.20.4).
Comment 2 Nate Graham 2021-03-09 15:42:31 UTC
Ah yes, this was fixed in a recent KF version, IIRC. You can keep tracking the issue particular to your distro in a Mageia-specific bug tracker.