| Summary: | plasmashell wants "metadata.desktop" files in slideshow sub-directories for some reason and isn't too shy to mention it 3 times per image | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kpackage | Reporter: | unsuspicious.fakename+kdebugs |
| Component: | default | Assignee: | Marco Martin <notmart> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | alvaro.carroz, bernie, bhush94, bugs.kde.org, hamelg, jjm, johnnyl33, kde, kde, kde, plasma-bugs |
| Priority: | NOR | ||
| Version: | 5.68.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
unsuspicious.fakename+kdebugs
2015-07-12 13:33:05 UTC
They're just debug statements. I don't see the problem? Do you mean, it actually should be looking for metadata.desktop files inside of the slideshow directories every time the picture changes (and check it thrice)? I don't understand, why those desktop files should be located in such user-made directories in the first place, but If that is intended behaviour, I guess the problem would be that debug output for something like that by default goes to the journal. And of course: there does not seem to be a way to stop it. I have disabled all debug output both in kdebugdialog and in kdebugdialog5. Also tried adding QT_LOGGING_RULES="*.debug=false" export QT_LOGGING_RULES ... to my /usr/bin/startkde or setting it in /etc/environment Still, currently, at least 95% of my whole system journal is wallpaper slideshow... that's not what the system journal is for. Well, not exclusively at least. I like to see other stuff there, occasionally, I mean. Disabling debug output want help as is qWarning. And indeed this should be solved, as for every wallpaper change it tries to set package path totally 3 times.. and fails because it is not valid package at all. This doesn't make sense at all. I don't see the wallpaper call setPath more than once but KPackage::Package repeatedly calls into createPackageMetadata, printing a warning each time. Also, the package still returns true for isValid despite not having metadata. Re-assigning to kpackage framework. Quoting from package.cpp: //Minimal packages with no metadata *are* supposed to be possible //so if !metadata().isValid() go ahead" So, either shut up or make those packages invalid. Fix submitted at https://phabricator.kde.org/D4188 The fix was not accepted as is, but the problem persists: # journalctl | grep "No metadata file in the package" | wc -l 38250 The warnings look like this: Jul 02 12:22:14 giskard kscreenlocker_greet[5837]: kf5.kpackage: No metadata file in the package, expected it at: "/home/bernie/Pictures/space/elite-dangerous/ships/" Could this message warning be removed from the code? It does not seem to serve any benefit (my background still works it seems) ? My slideshow wallpaper is setup with a lot of pictures. every time i startup my kde session, the user journal is polluted by thousands lines of irrelevant lines. $ find ~/.pics -type f | wc -l 2061 $ journalctl --user -b | grep -c 'kf.package: No metadata file in the package, expected it at' 6195 Upgrading the plasma framework to 5.76 has fixed the issue :) In just under 9 hours of uptime, I have had roughly quarter million pointless log entries. My desktop background does not change this fast.
```
# journalctl | grep 'No metadata file in the package'|wc -l ; uptime
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal' can see all messages.
Pass -q to turn off this notice.
280251
17:26:20 up 8:45, 1 user, load average: 0.88, 1.30, 1.57
```
I'm on an LTS (Ubutnu 22.04, plasma-workspace package 4:5.24.6-0ubuntu0.1); is there no way this can be back ported ?
|