Created attachment 120998 [details] ksplashqml crash report SUMMARY When executed from the cli ksplashqml crashes the display. The pc continues working. Networking is available (can ssh to it) and sound (e.g. music) continues playing normally. The displays turn black and the cooling fans go crazy. It is not the first time I encounter this problem but I had not found the source and it seemed to have gone away. It looks like it resurfaced with recent updates. Personally I do not have need to call ksplashqml from the cli but I guess some process does because it also happens arbitrarily. I deduced the problem might be ksplashqml because when I restart the pc it reports* that ksplashqml crashed and when I "Restart Application" the bug occurs again. STEPS TO REPRODUCE 1. Run ksplashqml OBSERVED RESULT - Screens turn black. - Display outputs seem to shut down. - Fans go crazy. + Other running services seem to continue. EXPECTED RESULT - Frankly do not know what ksplashqml is supposed to do, my guess is it shouldn't do what happens. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.1.11-arch1-1-ARCH (available in About System) KDE Plasma Version: 5.16.0 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4
Cannot reproduce. If I run 'ksplashqml' manually from Konsole, I see the black screen for about 20 seconds, then it exits. No errors. I suggest installing it into libexec, because this command is not supposed to be run manually.
*** Bug 410447 has been marked as a duplicate of this bug. ***
*** Bug 410337 has been marked as a duplicate of this bug. ***
Created attachment 123038 [details] crash reported in KDE Neon This is the crash window shown in KDE Neon
This bug is impacting KDE Neon 64-bit as well, at least with respect to today's applied updates. This might have something to do with having nvidia-340 installed. Will test on another KDE Neon machine which has nvidia-340 but not current on updates.
Upgrading this machine from nvidia-340 to nvidia-driver-390 seems to have resolved the problem. People trapped at the 340 driver due to newer drivers not supporting older hardware will see this problem. It appears there is an assumption made about what a driver can/does provide and 340 doesn't provide it. I'm guessing this might have to be kicked up to the QT community.
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
(In reply to Justin Zobel from comment #7) > Thank you for reporting this crash in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the crash with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! This was never fixed. This cannot be confirmed on newer software because the NVidia-340 driver is not supported with latest kernel. Everyone using the 340 driver will have this crash in perpetuity.
Then unfortunately there's probably nothing anyone can do about it outside of NVIDIA. :/