| Summary: | All KSysguard windows return 'mainwindow#1' as window role. | ||
|---|---|---|---|
| Product: | [Unmaintained] ksysguard | Reporter: | info |
| Component: | ksysguard | Assignee: | KSysGuard Developers <ksysguard-bugs> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | CC: | plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.18.4 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
> Other KDE applications I have tried do not appear to do this.
I see the same with KWrite, so I doubt it is related to KSysGuard. Maybe you only tested applications where launching it again actually only notifies the existing process instead of running a separate instance.
ksysguard is no longer maintained, in Plasma 6 there is the Plasma system monitor for this task. If your issue still happens with the Plasma 6 replacement, please re-open and we can move this bug to the new product, thanks! |
SUMMARY When launching two instances of Ksysguard both are labelled as 'mainwindow#1' and it is not possible to apply separate KWin rules to each. STEPS TO REPRODUCE 1. Launch Ksysguard twice. 2. Detect window properties for each with the KWin configuration tool. 3. Try to set separate placement rules for each. OBSERVED RESULT KWin treats them both as the same window and applies the same rules to each. Other KDE applications I have tried do not appear to do this. EXPECTED RESULT Kwin correctly detects the window role ('mainwindow#1', 'mainwindow#2' and so forth) and can apply placement rules separately. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.18.4 / KDE Neon (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION