anyone have any hint on the powermenu issue? no reboot no powerdown working from menu?
I am on Cachy OS, but Plasma 6 powerdown and reboot work fine on Plasma 6 (all I did was add KDE-unstable to pacman.conf).
Others have reported that in this thread. But if i remember correctly they had installed a “startmenu” widget which didn’t work.
@chalex20 Nate Graham over at KDE asks if I can hover my mouse over the extra icon, make a screenshot and then add the screenshot to the bug report. Unfortunately I have removed the extra icon, so I can´t do as he asks. Can you?
No, I deleted it as well…
Thanks for the frighteningly 
fast reply. Will inform Nate.
I added the CPU widget to my panel. Clicking on it does indeed open a pop up.
I then added the memory widget to my panel as well, but clicking that does not open a pop up, but does freeze not only the widget but the entire taskbar. I think I’m seeing a rather high CPU usage but my laptop is still usable.
Edit:
I’m seeing this in the logs:
plasmashell[1013]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:46: TypeError: Cannot read property 'updateRateLimit' of null
plasmashell[1013]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:45: TypeError: Cannot read property 'totalSensors' of null
plasmashell[1013]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:41: TypeError: Cannot read property 'highPrioritySensorIds' of null
plasmashell[1013]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:33: TypeError: Cannot read property 'title' of null
plasmashell[1013]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:46: TypeError: Cannot read property 'updateRateLimit' of null
plasmashell[1013]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:45: TypeError: Cannot read property 'totalSensors' of null
plasmashell[1013]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:41: TypeError: Cannot read property 'highPrioritySensorIds' of null
plasmashell[1013]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:33: TypeError: Cannot read property 'title' of null
plasmashell[1013]: file:///usr/share/ksysguard/sensorfaces/org.kde.ksysguard.piechart/contents/ui/CompactRepresentation.qml:22:1: QML CompactRepresentation: Binding loop detec>
plasmashell[1013]: qt.qpa.wayland.textinput: virtual void QtWaylandClient::QWaylandTextInputv3::zwp_text_input_v3_leave(wl_surface*) Got leave event for surface 0x0 focused su>
plasmashell[1013]: qt.qpa.wayland.textinput: virtual void QtWaylandClient::QWaylandTextInputv3::zwp_text_input_v3_leave(wl_surface*) Got leave event for surface 0x0 focused su>
plasmashell[1013]: qt.qpa.wayland.textinput: virtual void QtWaylandClient::QWaylandTextInputv3::zwp_text_input_v3_leave(wl_surface*) Got leave event for surface 0x0 focused su>
plasmashell[1013]: qt.qpa.wayland.textinput: virtual void QtWaylandClient::QWaylandTextInputv3::zwp_text_input_v3_leave(wl_surface*) Got leave event for surface 0x0 focused su>
Edit 2: Eventually my system stalled, and I had to REISUB.
Will investigate some more later today.
1 Like
it is only what I personally expect - with keeping in mind how other major updates are treated and how big the update from Plasma 5.27 to 6.0 is.
see the response above. I expect it to be weeks this time because it is not just a small feature and mostly bugfix update like the Updates from 5.1 to 5.27 were. It is a major rewrite of the whole DE that happens from 5.27 to 6.0. All depends on the feedback in testing channel once 6.0.0 (or later) hits there. The audience is much bigger there compared to the unstable-audience that tests it now and therefore also the detected bugs are usually bigger due to a broader hardware- and config variety that gets updated.
2 Likes
someone here tried kdesu and have issues? for mew it seems broken.
As i am currently into getting ISO and installer working onto plasma 6 i ask stupid questions here but would be cool to get validation in case …makes my investigation easier
I’ll have a look. Need a minute though.
What’s the symptom you are seeing?
it does only work if i use full path to executable/binary … kdesu alone simply bails out with command not found
Same here: just kdesu gives: command not found.
thanks! validates it is most likely general issue with something on unstable…
it does work with full path…
It’s at least in the same path as on my setup.
Is that directory in $PATH at all? Should it be?
it should be there
but is not …
On Plasma 5:
type -p kdesu
/usr/bin/kdesu
And thank you so much for all your hard work to get us rolling into Plasma 6 as smoothly as possible!
2 Likes
seems to be caused by something else… some path issue it seems simply… or it is simply not added to the path to avoid using it .