I have been staring at the little red dot on the update icon in my system tray so long that I think I may have burned it into my retina. To upgrade or to not upgrade, that is the question.
I am torn. Neon has been nearly perfect for me over the past 2 years. I can count on one hand the number of times any problem I had that was the fault of Neon and not my own ignorance (or, more often, blinding stupidity - “oooooo what happens when I do this even though I don’t know what I am doing? Ooops. D’oh!”).
But… trying to install Neon Testing has failed miserably 100% of the time over the past two months on my machine… which worries me. A lot.
Still, I am having a hard time resisting the urge to upgrade. Both my ego and superego are slapping my Id with a wet fish, but the Id is sooo strong… “Shiny! I want shiny!”. And, I do actually enjoy fixing things. I mentioned before that having a machine as stable and trouble free as mine has been is actually kinda boring.
Anyway… what happens if I just ignore this update and wait until 6.0.1? Will I still end up having to install the 6.0 stuff which may break things, before the (hopefully mostly fixed if broken before) 6.0.1?
My advice : Do not upgrade yet. Too many things are broken with plasma 6 packaging.
The only problem is if there is an emergency security update. But this should be related to GNU/Linux rather than plasma, so you could update the specific flawed package from CLI.
Yeah. I made the mistake thinking it was going to be great. A lot of the widgets and plugins I used went bye bye because they aren’t supported on Plasma 6. Also, the buttons to shutdown, restart, or logoff don’t work. So, I have to resort to command line to do it.
I’m glad I decided to stop the automatic updates when I did the night before on the other computers people use.
I have the greeter working. But no dice. Still can’t reboot, log off, or shutdown via the GUI. I even manually rebooted to make sure the desktop loaded those service files.
I did it the exact same way to get krunner working again.
Anyway, under the post that you got that from, that fix doesn’t seem to be working.
Nope. I tried using a new user account even before I did this fix. I think there is an issue with the KDE framework or whatever. If you get krunner working, that will be you new best friend in being able to at least reboot or shutdown.
Anyway, if something like this doesn’t work, qdbus org.kde.Shutdown /Shutdown logout, then the buttons will not work either. As you can see, that command specifies the KDE shutdown service. And that will affect any new user profile. From what I can guess. Because anything here /usr/share/dbus-1/services/ affects how the desktop works on a global scale.
All we can do is wait. I am thankful it’s just this issue. At least I can still at least have a desktop that loads and won’t constantly crash on me. And I can still game and do all those general things. Aside from widgets, video backgrounds and Kvantum along with other effects not working, I can say that much.
Anyway, if something like this doesn’t work, qdbus org.kde.Shutdown /Shutdown logout, then the buttons will not work either. As you can see, that command specifies the kde shutdown service.
I’ll just stick to the command line for now and not fuss over it. Krunner just became my new best friend (after applying the fix to make that work).
I just tried the latest version of KDE Neon with Plasma 6 in a virtual machine. None of the session buttons work. So, that proves nothing will fix it right now.
Yeah. I wish I didn’t upgrade. But oh well. At least things are stable so far.