Does anyone else have a black screen after entering credentials after the latest update? Just updated my system (KDENEON User Edition) and it rendered it COMPLETELY UNUSABLE under Wayland. Black (with some blinking) screen when entering in Wayland session.
KWin version: 6.2.4
Qt compile version: 6.8.1
XCB compile version: 1.15
OpenGL version string: 3.1.0 NVIDIA 565.57.01
OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
Driver version: 565.57.1
OpenGL version: 3.1
GLSL version: 1.40
X server version: 1.21.1
Linux kernel version: 6.8
I can confirm. Running KDE Neon, I am not able to run a Wayland session at all. it falls back to the sddm login screen.
Had to switch back to a X-Session or stick to the console.
My system:
Operating System: KDE neon 6.2
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.1
Kernel Version: 6.8.0-50-generic (64-bit)
Graphics Platform: X11
Processors: 16 Ć AMD Ryzen 7 7840HS w/ Radeon 780M Graphics
Memory: 54,7 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Framework
Product Name: Laptop 16 (AMD Ryzen 7040 Series)
System Version: AG
Seems there are other things broken. maybe Iāll dig a little if I find time today (work calls).
Update: Even power saving is not active anymore. FANās are running all the time. So there are more things broken in this release.
Well sort of the same problem.
I have 2 installations of neon (on separate disks).
The main one was installed a fair while ago and updated religiously. It started out at 6.1(I think) with the previous version of Ubuntu and was updated now at Operating System: KDE neon 6.2
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.1
Kernel Version: 6.8.0-50-generic (64-bit)
Graphics Platform: X11
Processors: 16 Ć AMD Ryzen 7 5700X 8-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4060/PCIe/SSE2
Manufacturer: ASUS
The second instance is my ātestā bed where i donāt care whether I break it. It is updated when I use it.
It updated today (12/12/24)
I went to use Wayland and it was horrible.
I booted into x11 and it was fine.
I updated the video driver (which is problematic for Nvidia) rebooted and Wayland works fine.
Booted to my main system with Wayland and it was truly horrible. Not to worry, boot to X11 which works fine, tried to update the driver but it was already at latest, so no difference.
So I have a system that only works with X11. Somewhere along the upgrade path I assume something was changed/missed.
This is the first line of the OpenGL in the āAbout this system: Graphicsā
MESA-LOADER: failed to open simpledrm: /usr/lib/dri/simpledrm_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/x86_64-linux-gnu/dri:$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
MESA-LOADER: failed to open simpledrm: /usr/lib/dri/simpledrm_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/x86_64-linux-gnu/dri:$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
Somewhere in the upgrades a path was altered or some such.
I know only enough about linux to get myself in trouble, so perhaps this might be a pointer for someone who knows what is going on.
We are at 24.0.9-0ubuntu0.3 and amd-drives at 24.2.0.60203-2044426.24.04 in KDE Neon.
Tried latest mesa drivers and ubuntu drivers (bleeding edge), no change still bounces me back to the sddm login page.
Thanks - this worked for me after purging the Nvidia drivers, rebooting into the GUI with Nouveau, installing nvidia driver 560 (for some reason 555 is no longer available on Ubuntu Graphics ppa) and creating the .conf file etc. Stable!
Setting fbdev=1 makes the LUKS screen for entering the disk decryption Password no longer accepting keyboard input. So I cannot decrypt my home partition during boot process.
Operating System: KDE neon 6.2
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.1
Kernel Version: 6.8.0-50-generic (64-bit)
Graphics Platform: X11
Processors: 12 Ć AMD Ryzen 5 5600X 6-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2
Manufacturer: BIOSTAR Group
Product Name: B550T-SILVER
I wonder if itās normal that KDENEON User Edition users can at any moment receive an update that will make their system completely unusable? Does now no one really do even the most basic testing of updates? Why, after such a serious failure was discovered, affecting so many people, why no developer reacts to it? Or I miss something? Probably one needs to make a proper bug reportā¦
It is worth highlighting again to emphasize the following.
The āUserā edition is for enthusiast KDE users who expect a bit more polish. Please note that the focus of the āUserā edition is still KDE software only. There is no thorough review of the complete software stack to guarantee a rock solid day-to-day experience.
Take what you want from this but this implies there is no thorough QA process involved. As an end user you are are still considered a BETA user; thus expect bugs.
Looking through this thread this specific issue is due to a problem with NVIDIA or a Mesa update which screwed things up.
Just upgraded my second KDENEON User Edition system with the latest updates, the result is the same - a black screen (in Wayland). I also confirm setting fbdev=1 resolves the problem. Thanks goes to @prasadmurthy
Yes, the catch with Neon is that itās trying to be bleeding-edge on KDE community-developed components to deliver those quickly to users, while constantly retrofitting those on top of a ālong term supportā operating system base (Ubuntu LTS) that is designed to use static versions of packages for years-on-end.
Thatās one of the factors driving interest in development of KDE Linux, trying to fulfill both the āKDE stuff delivered to you straight from the sourceā promise, while using an operating system base that aligns better with that mission.
Being a BETA user I expect bugs. I do not expect the whole system to become completely unusable seemingly in regular intervals of every 2 months or so.
To be a beta user one needs to be able to use the darn thing to some degree. Regularly breaking the system due to the apparent āphilosophyā reasoning makes it barely an ALPHA software.
There was a great enthusiasm for Neon for years. I personally reported and helped fix many issues over the years.
But now I think I will start to look to put my effort elsewhere. Having to hack my laptop back to life every 2 months because of complete lack of the BASIC TESTING effort is just a bit too much.
yea, exactly the same thoughts and feelings hereā¦ I started to use KDE Neon on a promise that it is reasonably latest KDE ideal for daily usage, it was once written in the download page, but after an epyc fail with P6 update, they decided nothing better than just rename it to enthusiasts segment and to add bunch of lame excuses in their FAQ to justify their lack of the most basic testing. This is kind of logic when instead of addressing the problem you call the problem to be not a problem is never a good way to go. Just my opinion. And yea what kind of beta testing we can talk about if your system is completely broken, or your ābeta-testersā become so upset so they decided to switch to another distribution?
The way I solved this was just to do a sudo apt remove nvidia-driver-550 and fallback to the integrated AMD Radeon graphics in my laptop. So I just assumed it was an NVidia/Wayland issue and not a KDE neon issue. But interesting to hear others getting it to work again, thanks!