I have numerous columns hidden in my X11 session. When I log into a wayland session, all columns are shown.
Cannot reproduce - hidden in X11 columns are not shown in Wayland Plasma: 5.13.2 Apps: 18.04.2 Frameworks: 5.47.0 Qt: 5.11.1 Kernel: 4.18.0-1-MANJARO OS: Netrunner Rolling Video: Intel 4400 Driver: xf86-video-intel 1:2.99.917+831+ge7bfc906-1 Mesa 3D: 18.1.3 Screen: 1600x900 Xorg: 1.20 Wayland: 1.15.0-1 Wayland Protocols: 1.14-1
I am very sorry, as I cannot reproduce it either! It must have been recently fixed, because it had been reproducible not long ago. I am closing the bug.
I just opened ksysguard and the columns that I set to hide are no longer hidden, so I am reopening this. Is it possible that it works in the first wayland session after X, but not in subsequent wayland sessions?
*** Bug 398238 has been marked as a duplicate of this bug. ***
still valid for plasma 5.14 beta on Arch Linux.
Bug persists in plasma 5.15 beta. Steps to reproduce from my bug 398238 marked as duplicate: 1. start x11 session 2. open ksysguard 3. hide some columns (right click the column, click "Hide column xxx") 4. do logout 5. start wayland session 6. open ksysguard 7. restart ksysguard Result: all columns, including the columns hidden in the step 3, are enabled
*** Bug 406244 has been marked as a duplicate of this bug. ***
(In reply to Patrick Silva from comment #6) > Bug persists in plasma 5.15 beta. > > Steps to reproduce from my bug 398238 marked as duplicate: > > 1. start x11 session > 2. open ksysguard > 3. hide some columns (right click the column, click "Hide column xxx") > 4. do logout > 5. start wayland session > 6. open ksysguard > 7. restart ksysguard > Result: all columns, including the columns hidden in the step 3, are enabled humm, I can't reproduce anymore. Operating System: Arch Linux KDE Plasma Version: 5.18.90 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 rc2
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!