Hello
After the recent KDE update, I wanted to try the new system monitor application, but seems it requires a particular cgroup set up.
Has anyone got plasma-systemmonitor working?
Code:
plasma-systemmonitor
file:///usr/lib64/qt5/qml/org/kde/ksysguard/page/EditablePage.qml?page=overview.page:15:1: QML EditablePage: Binding loop detected for property "heightForContent"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth"
QIODevice::read (QFile, "/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/cgroup.procs"): device not open
terminate called after throwing an instance of 'std::filesystem::__cxx11::filesystem_error'
what(): filesystem error: directory iterator cannot open directory: No such file or directory [/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service]
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = plasma-systemmonitor path = /usr/bin pid = 7695
KCrash: Arguments: /usr/bin/plasma-systemmonitor
KCrash: Attempting to start /usr/lib64/drkonqi
[1] + 7695 suspended (signal) plasma-systemmonitor
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 24 and type 'Read', disabling...
[1] + 7695 exit 253 plasma-systemmonitor
