SUMMARY Plasma monitor doesn't work correctly. It shows nothing. I suppose the reason is it can't see any sensors - in options I can't choose any sensor (on any preset: net speed, hard disk activity, etc...). Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION
Can I have a screenshot? Also can you include the output of: qdbus org.kde.ksystemstats / qdbus org.kde.kstats /
Created attachment 129159 [details] Widget on desktop.
Created attachment 129160 [details] Sensor details
(In reply to David Edmundson from comment #1) > Can I have a screenshot? > > Also can you include the output of: > > qdbus org.kde.ksystemstats / > qdbus org.kde.kstats / No problem. sorry, it's my first report. First command doesn't work at all. Second command (don't know how to hide smth to spoiler): method QDBusRawType::a{s(sssuuddi)} org.kde.KSysGuardDaemon.allSensors() signal void org.kde.KSysGuardDaemon.newSensorData(QDBusRawType::a(sv sensorData) signal void org.kde.KSysGuardDaemon.sensorAdded(QString sensorId) method QDBusRawType::a(sv) org.kde.KSysGuardDaemon.sensorData(QStringList sensorIds) signal void org.kde.KSysGuardDaemon.sensorMetaDataChanged(QDBusRawType::a{s(sssuuddi metaData) signal void org.kde.KSysGuardDaemon.sensorRemoved(QString sensorId) method QDBusRawType::a{s(sssuuddi)} org.kde.KSysGuardDaemon.sensors(QStringList sensorsIds) method void org.kde.KSysGuardDaemon.subscribe(QStringList sensorIds) method void org.kde.KSysGuardDaemon.unsubscribe(QStringList sensorIds) method QDBusVariant org.freedesktop.DBus.Properties.Get(QString interface_name, QString property_name) method QVariantMap org.freedesktop.DBus.Properties.GetAll(QString interface_name) signal void org.freedesktop.DBus.Properties.PropertiesChanged(QString interface_name, QVariantMap changed_properties, QStringList invalidated_properties) method void org.freedesktop.DBus.Properties.Set(QString interface_name, QString property_name, QDBusVariant value) method QString org.freedesktop.DBus.Introspectable.Introspect() method QString org.freedesktop.DBus.Peer.GetMachineId() method void org.freedesktop.DBus.Peer.Ping()
A bunch of us on the KDE neon users Telegram chat are experiencing this as well after upgrading to Plasma 5.19. I was also able to reproduce the issue in VirtualBox after running KDE neon User Edition with the Plasma 5.19 update. This likely affects all KDE neon User Edition users. Monitoring through System Monitor (KSysGuard) works fine. Here is my kstats output (ksystemstats receives no reply): signal void org.kde.KSysGuardDaemon.newSensorData({D-Bus type "a(sv)"} sensorData) signal void org.kde.KSysGuardDaemon.sensorAdded(QString sensorId) signal void org.kde.KSysGuardDaemon.sensorMetaDataChanged({D-Bus type "a{s(sssuuddi)}"} metaData) signal void org.kde.KSysGuardDaemon.sensorRemoved(QString sensorId) method {D-Bus type "a{s(sssuuddi)}"} org.kde.KSysGuardDaemon.allSensors() method {D-Bus type "a(sv)"} org.kde.KSysGuardDaemon.sensorData(QStringList sensorIds) method {D-Bus type "a{s(sssuuddi)}"} org.kde.KSysGuardDaemon.sensors(QStringList sensorsIds) method void org.kde.KSysGuardDaemon.subscribe(QStringList sensorIds) method void org.kde.KSysGuardDaemon.unsubscribe(QStringList sensorIds) signal void org.freedesktop.DBus.Properties.PropertiesChanged(QString interface_name, QVariantMap changed_properties, QStringList invalidated_properties) method QDBusVariant org.freedesktop.DBus.Properties.Get(QString interface_name, QString property_name) method QVariantMap org.freedesktop.DBus.Properties.GetAll(QString interface_name) method void org.freedesktop.DBus.Properties.Set(QString interface_name, QString property_name, QDBusVariant value) method QString org.freedesktop.DBus.Introspectable.Introspect() method QString org.freedesktop.DBus.Peer.GetMachineId() method void org.freedesktop.DBus.Peer.Ping()
qdbus org.kde.ksystemstats times out for me Error: org.freedesktop.DBus.Error.NoReply Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. qdbus org.kde.kstats only works if ksysguard is openend
I appreciate this is a somewhat unhelpful comment, but I just did an install of a clean Neon Testing ISO and that is working correctly. (as is my local laptop) Will check User Edition.
Got it :( I'm such a clumsy idiot. There was a very last minute file rename. I checked everything worked, but it left the frickin' bus name in the DBus activation file is wrong. I'm sure I checked it, but I probably still had the old files lying about so it still worked.
At this point, I may as well just backport the patches that use matching dbus service name instead of trying to minimise the patch delta. Fix will be out in 5.19.1.
*** Bug 422708 has been marked as a duplicate of this bug. ***
*** Bug 422710 has been marked as a duplicate of this bug. ***
*** Bug 422728 has been marked as a duplicate of this bug. ***
Working on 5.19.1 after reinstalling the widgets.