r/kdeneon

I've been a happy KDE Neon user since its very first version. Its philosophy was absolutely brilliant: you got a rock-solid, stable Ubuntu LTS base—guaranteed not to blow up during a routine system update—combined with the absolute latest and greatest of the wonderful KDE environment. For a long time, Neon was clearly the golden child of the KDE project.

However, the situation over the last few weeks has been incredibly frustrating, and sadly, this isn't the first time we've experienced these long, unannounced delays between minor releases. Upgrading to Plasma 6.7.0 broke a lot of things, which can happen, but freezing updates for a server migration during such a critical launch feels unacceptable. Leaving us stranded without 6.7.1 and 6.7.2 for over two weeks is a massive logistical failure.

The lack of transparency makes me wonder: Did they not realize this would leave users with broken systems? Or are we witnessing the slow death of the distro due to a lack of interest from the maintainers? It honestly feels like a giant sign telling us to pack our bags and move to another distro.

Leaving the veteran user base in the dark with a buggy system for weeks is not a good look. What are your thoughts? Is it time to switch?

I am on Plasma 6.7.0, but I am not getting 6.7.1 or 6.7.2 updates. I tried either pkcon update and apt full-upgrade.

I ran some updates, got on KDE 6.7, during the install it installed plasmalogin, but I have sddm configured the way I like it so I kept using it when it asked what to use for logging in.

After the upgrade was done, I ran apt autoremove, and it uninstalled sddm, despite it being an actively running service. On reboot it dropped me into tty1. Reinstalling sddm got me back to a working system but how did it determine that sddm was eligible for autoremove?

It's a bass-ackwards antipattern and annoying as hell. Stop it. Stop assuming I'm always using a GUI, stop assuming I need a completely separate application to fire up, take focus away from my terminal, and prompt me to do something we've been trying to train users FOR YEARS to avoid doing - entering sensitive information in a popup outside the intended application. This is dumb and solves nothing.

But it gets better, KDE Neon's stupid env scripts that set it up neglect to detect whether the user is even in a GUI session! So now I have to unset SSH_ASKPASS explicitly so I can ssh from a remote session (jumpbox style) or from a vty. Extra dumb. Purging the ksshaskpass package doesn't remove that env script either !!! What the hell, KDE? Who's responsible for this and how loudly do I need to yell at them to make it stop?

</rant>

user@host:~$ ssh 192.168.0.42
Failed to create wl_display (No such file or directory)
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
qt.qpa.xcb: could not connect to display :1
qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: minimalegl, xcb, eglfs, linuxfb, vnc, offscreen, wayland-brcm, wayland-egl, wayland, vkkhrdisplay, minimal.
Permission denied, please try again.