Summary: | plasma version missing | ||
---|---|---|---|
Product: | [Applications] kinfocenter | Reporter: | slartibart70 |
Component: | About this System | Assignee: | Plasma Bugs List <plasma-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | nate, ngompa13, rdieter, sitter, terranceb |
Priority: | NOR | ||
Version First Reported In: | 5.22.1 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
URL: | https://bugzilla.redhat.com/ | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Info Centre
F34 Info Centre |
Description
slartibart70
2021-06-17 20:52:13 UTC
(In reply to slartibart70 from comment #0) > The info center does not show the plasma version any more since 5.22, only > the frameworks version. > (in 5.21 we had plasma version, then frameworks version, then QT, ...) I can't seem to reproduce this. Info Centre seems to show me all the same info as before on Arch Linux. Which distribution are you running? Created attachment 139452 [details]
Info Centre
Info Centre as currently shown in Arch Linux on latest Plasma version.
I see the same issue on F34, no Plasma version is shown. Created attachment 139453 [details]
F34 Info Centre
Info Centre as shown in F34
This would appear to be a Fedora-specific issue, perhaps a packaging problem. Please report it to them at https://bugzilla.redhat.com/. Thanks! Where does kinfocenter get the plasma version from? To me, looks like the plasma version is supposed to be (essentially) hard-coded to the kinfocenter version, https://invent.kde.org/plasma/kinfocenter/-/blob/master/Modules/about-distro/src/PlasmaEntry.cpp It does have this wierd code snippet there, // Since Plasma version detection isn't based on a library query it can fail // in weird cases; instead of admitting defeat we simply hide everything :P if (localizedValue().isEmpty()) { return; } I'm guessing we're hitting that "wierd cases" ? ah, source of the issue is really bug #436954 , interested parties can cc: there. *** This bug has been marked as a duplicate of bug 436954 *** |