| Summary: | Help --> About KDE doesn't show information about installed KDE | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] libplasma | Reporter: | Kevin Coonan <kevin.coonan> |
| Component: | libplasma | Assignee: | Marco Martin <notmart> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | attachment-2932-0.html | ||
|
Description
Kevin Coonan
2017-04-02 21:48:53 UTC
Please read bug 351337 comment #9. *** This bug has been marked as a duplicate of bug 351337 *** Created attachment 105135 [details] attachment-2932-0.html Not exactly. I use openSUSE w/ Zypper, so I live in the world of a million repositories. I try, very hard, to use a single repo for all my KDE apps, as past experience has shown that even the exact same version, from different repo (different build/linking???) of a component that differs from the rest can crash plasma. Being able to check and see that I am at lease using the same version of KMail, Konqeror (which I still like better than Dolphin, esp. once all the icon display, text menu display, loss of side bar, screwed up time/date format and all the other KDE4->KDE5/Qt5 regressions are fixed...ahem), KOrganizer, etc. etc. Part of this is my own making, but there are apps in various repos not in the standard build ones that I need, or versions which fix problems or add functionality I need. How hard would it be to show the Qt version, KDE framework version, Plasma version, and application version? It would avoild 95% of my bug reports which come back to me with some snooty email that tells me that I shouldn't mix and match component versions (a consitant versioning, or at least letting users know which versions of the various applications will work together would be fantastic) and to switch some component to the same repo the others came from. openSUSE doesn't do a great job with letting you know this--I think Zypper just trusts whatever the required version of some dependency is based on the documentation developers provide, but is confusing as hell to have some common application listed 5 times and having to dig into the repo, dependency, and versioning info to figure out which version of Akonadi I need. Don't get me wrong, I am not going to go back to one of the RedHat or Debian/Ubuntu flavors, and don't have time for Arch--I really like openSUSE esp. with OBS working and Tumbleweed. YaST and Zypper are awesome, but make it too easy to get into dependency issues that can be subtle and heard to track down if you cannot read the crash reports yourself. Thanks, Kevin Coonan, MD On Thu, Apr 20, 2017 at 6:35 PM Christoph Feck <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=378381 > > Christoph Feck <cfeck@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |RESOLVED > Resolution|--- |DUPLICATE > > --- Comment #1 from Christoph Feck <cfeck@kde.org> --- > Please read bug 351337 comment #9. > > *** This bug has been marked as a duplicate of bug 351337 *** > > -- > You are receiving this mail because: > You reported the bug. The Plasma version is unrelated to the application version. For example, I can use DigiKam 5.5 on Plasma 5.9. Or Dolphin 17.04 on Plasma 4.11. Each of those applications can be compiled against a different Qt or Frameworks version, which is the reason they are listed in the version tab of that application. For Plasma - lacking a Help menu - use KInfoCenter. It has the "About System" version tab. It also shows the Qt and Frameworks version it was compiled with. Again, these are unrelated, so there cannot be a common dialog for all KDE applications. |