| Summary: | About this System page: Add more information items as in Netrunner | ||
|---|---|---|---|
| Product: | [Applications] kinfocenter | Reporter: | Gregor Mi <codestruct> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | wishlist | CC: | nate, rainer, sitter |
| Priority: | NOR | ||
| Version First Reported In: | 5.19.90 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Gregor Mi
2018-05-14 08:53:00 UTC
KDE Applications versions: bug 387106 For all other items, there are specific sections in KInfoCenter. Hey, that's pretty nice. +1 from me. Much nicer than having to manually navigate to the individual categories. Being more useful is always good, but all that information is already available in the respective modules :|. Renderer seems useful enough, and there is a separate bug for that. But all the other stuff seems fairly meh at best. In fact, for the online status the information is available by default on the desktop via the systray. The problem in my eyes, is that if we put too much information into the main page it becomes way less valuable and also way harder to look nice. The referenced screenshot for example would have trouble fitting on <1080p so one would have a nice scrollbar :@ Then I thought maybe we should have tabs. But what's the difference between a tab and the actual relevant modules, so that's no good either. I guess, what I am saying is that I'd prefer we have a story for why a given data point is relevant to have on the system info module as opposed to the individual modules. That could be simply that it's useful for showing off to your friend, not just that it is needed for diagnostics. Along a similar line, the GL module does a distinctly bad job of putting the key points in your face, so perhaps the underlying problem with the data is more that it is hard to find in the existing modules? If so, I'd favor seeing that fixed ^^ When writing a bug report, I usually add the version information of KDE Applications and Mesa plus that I'm using Wayland. It would be quite helpful if this information is available by default so that you can just use copy & paste. Operating System: Arch Linux KDE Plasma Version: 5.19.90 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 Kernel Version: 5.8.10-arch1-1 OS Type: 64-bit Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 31.4 GiB of RAM Graphics Processor: AMD Radeon VII Unfortunately the concept of "KDE applications" is controversial and we don't have a single product called "KDE Applications". Technically speaking all of our apps are independent, and while many of them happen to share the same version numbering scheme and release schedule, not all do. So it's safest to use the version number of just the app you're reporting the issue on. Honestly, this is all a crutch. What we actually need is to make our builtin report-bug feature actually useful by extending it with the ability to a) gobble up this generally useful platform metadata (OS, qt version, kf5 version, ...) b) allow apps to extend with their context relevant metadata (debug info dump for kwin, loaded plugins for a gstreamer based video player etc. etc.) Currently it simply dumps you on the bugzilla website, but realistically we can do much better nowadays with bugzilla having a proper API we can interact with. So, I'm fairly -1 on this because the job of kinfocenter is not to bypass shortcomings elsewhere in the stack and by extension it's also not the job of the about-system module to pull in all sorts of largely usless data elsewhere available in info center modules just so they may then get copied into bug reports more easily. |