I’m using a KDE Neon, and just made the 6.3 update. It has been catastrophic on my computer.
I am wondering if X11 is still supported for KDE 6.3!
With my usual session (I kept a copy of plasma-org.kde.plasma.desktop-appletsrc and ksmserverrc) the plasma session is totally broken:
kwin has some trouble. It crashes at startup, relaunch, but the windows’ content (Firefox, Thunderbird for instance) remains dark (nothing displayed inside).
plasma is partly broken, backgrounds are not shown on both screen (my laptop screen, has no plasma at all: no left click on it)
I tried to restart kwin DISPLAY=:0 nohup kwin --replace &, it doesn’t solve any issue (but I’m not surprised since kwin crashed and relaunch at plasma startup)
I tried to restart plasma (same way) and it is worse, nothing works anymore (desktop icons not clickable anymore, and KDE menu empty of any application)
I also tried to disconnect delete plasma-org.kde.plasma.desktop-appletsrc and ksmserverrc and tried to reconnect with several fresh starts. Once plasma started some apps (Firefox, Thunderbird, other non KDE apps) are doing the same thing (black windows content, crashed, & co).
With Wayland there is not such problems during my tests, but of course no session restore (Wayland IS NOT ready for my desktop).
Does someone know how I can restore my good old session with my plasma config (plasma-org.kde.plasma.desktop-appletsrc), and my windows properly opened (ksmserverrc)?
For me also a lot of problems with X11 on 6.3. I have to restart plasma after every login and sometimes in between. It is impossible to work with this way. Hopefully there will be a solution soon!
Also for me.
actually I’m using Wayland for long time, yesterday, after latest updating, PC was blocked at start page (login) and doesn’t recognize password.
I had to switch to X11, to work, but now Plasma doesn’t recognize the 2nd monitor.
Catastrophic, I agree …
Agree with all the above. Updated (KDE Neon) to 6.3. It’s a train wreck. X11 does not start normal desktop functions. And logging in to Wayland has anomalies… shortcut icons are showing up in miniature. And probably lots of other bugs.
I love and appreciate what the developers do with KDE, which has often been a great desktop. But why do a big update if so much is busted right out the gate?
Seems to be a feature of Neon, I gave up on it after the train wreck install of the 5.27.11, I think it was, left the machine unusable. Other distros that updated it had zero problems.
For me, after updating to Plasma 6.3 on Arch Linux, TigerVNC server is no longer work correctly - connecting to the X11 session results in Kwin crash and wrong virtual display size… And every display resize event also cause Kwin crash. Tested on new Arch Linux machine - result is the same. On old machine (1 week ago) with KDE 6.2 everything works fine
Yep, X11/Nvidia is badly broken for me too. I have tried various drivers and common fixes to no avail. Other parts of the update are problematic too:
KWin crashes on every login, and the “recovered” desktop is corrupted - glitching from blurry to sharp to blurry to sharp like it has a sync problem rendering it unusable (X11).
Upon first reboot, the renderer switched itself to software mode (Wayland).
The secondary display is showing black and is not interactive but the mouse does go over it. (X11)
KWin is still misreporting GPU labels to sensors. (X11 and Wayland)
Drag and drop from apps to other apps or the desktop is broken (Wayland).
Some apps, like XnView are now misbehaving (X11 and Wayland)
Mime types got set to completely wrong handlers and manually set default apps are no longer default.
Wayland seems OK, and at lease does not crash Kwin… but it has its own host of issues that make it unusable with Nvidia, the primary of which is broken display color calibration, a completely unusable NVCP for hardware parameter control, and constant window management glitches like apps not remembering their sizes or positions.
Are the rumors true that KDE/Neon have totally abandoned X11 and do not even test for compatibility anymore? If so, it means this may never be fixed and I wont be able to use Plasma anymore as Wayland is unusable for me.
At this point, I am hoping Timeshift can restore me back to 6.2 successfully. I will then see if I can get the new 6.11 Kernel installed without the Plasma update until such time as Plasma gets fixed or I move to another distro as sadly its looking like Neon may be becoming a no-go for me.
I think KDE devs need to keep in mind that the type of Linux user hanging onto X11 due to the fact that Wayland is still in a state of perpetual beta, is the type of user that has ‘User Feedback’ set to ‘Disabled’.
There’s every possibility those Wayland numbers provided by User Feedback are totally skewed when Wayland still struggles with basic functionality that’s been under X11 for a considerable number of years now.
For @Beurt : just to check, what steps are you following when you mentioned that you “disconnected” and “reconnected” those two rc files? Do the broken display issues occur if you create a new user profile?
On the other general comments being brought up on this thread: let’s please keep this Help topic focused on helping the topic creator with the situation they’re facing.
If folks are finding that their system configurations aren’t well-represented among those used by existing developers and testers - therefore leading to more issues impacting them - then I think the most helpful thing as users would be testing upcoming versions of KDE software, and ensuring that high-quality bug reports are filed for the issues that you encounter.
erase plasma-org.kde.plasma.desktop-appletsrc and/or (depending on the tests) ksmserverrc
reconnect to plasma through sddm
I tested various situations.
My old files ( plasma-org.kde.plasma.desktop-appletsrc and ksmserverrc) break plasma and kwin, and my session is never properly restored.
Each one of the old file, alone, is breaking the session
The session is not working very well without both my old files deleted (fresh new files created by plasma/kwin). And the new session windows are not properly restored after leaving the session (rebooting for instance).
cf. OP
I am sorry, I am contributing elsewhere, but I cannot afford testing the beta of Plasma. But, I feel that I currently am, against my will (I’d rather stay with 6.2, than dealing with this broken 6.3).
If the devs cannot maintain proper x11 support (I can understand that, a day is only 24h), they should say it.
In my usage sessions are crucial. I rather leave KDE, than leaving sessions save/restore system when I reboot/disconnect. This is why I, personally, cannot greenlight Wayland.
Yes, just raw Arch - updated package via pacman. Then I use snapshots to rollback packages and confirm it was broken previously. I didn’t try Neon, so I don’t know how the package system works there - you probably need to just wait a little bit for this new version to be available
Same here, had to reinstall a fresh KDE Neon User after upgrading to Plasma 6.3 – but X11 is still unusable on a fresh install ! Kwin crashes constantly, fills up the journal with errors.
Operating System: KDE neon 6.2
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2
Kernel Version: 6.11.0-17-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i7 CPU M 620 @ 2.67GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics
Manufacturer: LENOVO
Product Name: 7459CT0
System Version: ThinkPad X201
From my experience with KDE Neon, it’s a hit or miss. I started to understand that it’s not a true distro, as expressed by KDE devs, but more of an installation to test the latest KDE features. Once I fully understood that, I kept Neon in a sandbox to do just that and since, moved to Fedora KDE Spin, which offers the latest KDE features days or a couple of weeks after released.
My issue with Neon was primarily with Nvidia support at installation and constant breaks at upgrades and conflicting packages.
It’s been a lot more enjoyable on Fedora; bleeding-edge. For a more LTS support env, Kubuntu was something I tried but I really like living on the edge with stability and found that Fedora offered that for me.
Not the answer you’re looking for but maybe me sharing my experience could shed some light on the fact that Neon isn’t a primetime distro because, well, it isn’t stamped as one by the devs.
Here’s to hoping that KDE Linux offers better stability than Neon
I have been looking forward to the kernel update to 6.11 so was just going to see if I could live with Wayland until such time as X11 got sorted out, but, after less than 10 minutes of actual use, apps started to experience screen freezes and crashes, and the usual wayland glitches started to show their ugly heads (flashing screen when mousing over, sync glitches and so on).
I used Timeshift to restore me back to 6.2 and Kernel 6.8. While I have had to use timeshift to fix my own mistakes, this is the first time I have had to do it because Plasma was so broken is was unusable after an update. This is very concerning.
My machine is set up to automatically report crashes and I do have all the debugging symbols installed, so the devs do have detailed crash reports.
Is this on Neon? I’m on the latest kernel on Fedora 41 KDE Spin and have not experienced those issues. I’ll admit that Nvidia isn’t the best experience but it’s sooo much better than what it used to be on Wayland
And every display resize event also cause Kwin crash. Tested on new Arch Linux machine - result is the same. On old machine (1 week ago) with KDE 6.2 everything works fine