Bug 486891 - The state of the Process Table is not persistent
Summary: The state of the Process Table is not persistent
Status: REPORTED
Alias: None
Product: plasma-systemmonitor
Classification: Applications
Component: general (other bugs)
Version First Reported In: 6.0.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-11 15:18 UTC by popov895
Modified: 2025-05-27 02:40 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description popov895 2024-05-11 15:18:27 UTC
SUMMARY

On the custom page, the Process Table doesn't properly save/restore its state.

STEPS TO REPRODUCE

1. Add new page
2. Add Process Table
3. Change visible columns/sort columns/column order
4. Restart application

OBSERVED RESULT

The changes were not saved/restored.

EXPECTED RESULT

The changes were saved/restored.

SOFTWARE/OS VERSIONS

Operating System: openSUSE Tumbleweed 20240509
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Graphics Platform: X11
Comment 1 popov895 2024-05-14 11:24:22 UTC
If you manually change the settings of the Process Table in the corresponding *.page file, the changes are applied. It turns out that the changes are simply not written to the corresponding *.page file.
Comment 2 John Kizer 2025-05-10 05:12:51 UTC
Hi - following those steps on my Fedora KDE 42 device results in the column state being correctly restored the next time the application is started. Could you please verify if this issue is still occurring on Plasma 6.3.5? Thanks!
Comment 3 Bug Janitor Service 2025-05-25 03:48:21 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Fabian 2025-05-25 09:50:43 UTC
Still happens for me in 6.3.5 if I simply click "OK" in the popup and then close and restart the program. But I click "OK", maybe also change sort and widths, then click "Edit page" and save without making any changes, then it also persists my column changes, including reordering, sorting and width.
Comment 5 John Kizer 2025-05-25 16:35:01 UTC
Interesting - if I:

* Click on the Processes page
* Right click on the column headers and choose Configure Columns
* Change either the visibility or ordering of a column
* Click OK
* Exit System Monitor and restart
* Click on the Processes page again

The changes seem to be kept - is there anything different in the steps that you're following, maybe?

If those are all the same steps, are you able to check if that same thing happens under a freshly-created user account?

Thanks!
Comment 6 Fabian 2025-05-25 20:44:15 UTC
I have a custom page as my only one. Right clicking the column headers does nothing, I use the three dots button of the page. Do you mean creating a new user on the system? That sounds a bit overkill and I don't want to do that.
Comment 7 John Kizer 2025-05-25 23:11:19 UTC
That's odd - if you right-click on the column headers, you don't get a context menu with "Hide" and "Configure Columns" options?
Comment 8 Fabian 2025-05-26 00:02:25 UTC
Oh, now I do. Either it didn't do that before or I overlooked it, because it opens all the way on the right, even if I click on a left column. But yes, still happens the same if I follow your exact steps, apart from "Click on the Processes page", because the process table is already visible when I open the program.
Comment 9 John Kizer 2025-05-26 02:39:55 UTC
Hmm - do any messages show up in the terminal if you run plasma-systemmonitor from there to start it?
Comment 10 Fabian 2025-05-26 15:37:06 UTC
In a lot of situations, I get this, sometimes multiple times:
file:///usr/share/ksysguard/sensorfaces/org.kde.ksysguard.processtable/contents/ui/FullRepresentation.qml:308:5: QML ColumnConfigurationDialog: Binding loop detected for property "y":
qrc:/qt/qml/org/kde/kirigami/dialogs/Dialog.qml:302:5

When switching an entry from "hidden" to "text only", I got this:
qt.qml.context: qrc:/qt/qml/org/kde/ksysguard/table/ColumnConfigurationDialog.qml:174:25 Parameter "index" is not declared. Injection of parameters into signal handlers is deprecated. Use JavaScript functions with formal parameters instead.

At one point also this, but not when I just tried to reproduce it:
qt.core.qabstractitemmodel.checkindex: Index QModelIndex(-1,-1,0x0,QObject(0x0)) is not valid (expected valid)
kf.i18n: 1 instead of 2 arguments to message "Process ID %1, owned..." supplied before conversion

When closing:
QProcess: Destroyed while process ("/usr/lib/ksysguard/ksgrd_network_helper") is still running.
org.kde.ksysguard.plugin.network: Helper process terminated abnormally: ""

When clicking "edit page":
qml: heightMode balanced
qml: heightMode balanced
qml: heightMode balanced
qrc:/qt/qml/org/kde/ksysguard/page/ColumnControl.qml:140:13: Unable to assign [undefined] to bool
qrc:/qt/qml/org/kde/ksysguard/page/ColumnControl.qml:140:13: Unable to assign [undefined] to bool
qrc:/qt/qml/org/kde/ksysguard/page/ColumnControl.qml:140:13: Unable to assign [undefined] to bool
Comment 11 John Kizer 2025-05-27 02:40:17 UTC
Thanks! I'm not sure if it'll be helpful in this case, but for what it's worth, I'm not seeing these lines in the terminal when I do the same:

qt.core.qabstractitemmodel.checkindex: Index QModelIndex(-1,-1,0x0,QObject(0x0)) is not valid (expected valid)
qrc:/qt/qml/org/kde/ksysguard/page/ColumnControl.qml:140:13: Unable to assign [undefined] to bool

The ColumnControl one at least sounds possibly related?