Summary: | Plasma crashes on every startup after last update | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Rafael Linux User <rafael.linux.user> |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | arparamir, bhush94, plasma-bugs, rafael.linux.user |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.2.2 | ||
Target Milestone: | 1.0 | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Rafael Linux User
2015-07-07 18:27:43 UTC
Exactly the same crash on openSUSE Tumbleweed after yesterdey's (2015-07-08) update. Unable to enter the desktop at all after that. I solved the problem reinstalling private Nvidia drivers from console. BUT with pre-Plasma 5 KDE versions, this was not making crash the system, simply the Nvidia controller was not loaded, but KDE did not crash on that situation. Crash is on the driver being missing. Plasma 1 did not use OpenGL. So, this means that every system update (I didn't see a kernel update in this case) Plasma will crash on loading? And what's "Plasma 1"??? I'm using Plasma 5.2.2, that theorically is fully OpenGL accelerated!!! Plasma 5 is fully OpenGL accelerated, which means it doesn't work if someone breaks the graphic drivers. The system re-vitalised after the installation of NVIDIA-346.72 driver. Great Родион ! This issue will be a headache in Plasma 5 if not solved to avoid crashes and let Plasma work with legacy drivers, like KDE 4 does :( It's not that we don't work with legacy drivers, when NVidia is in this state, it supplies us with a driver that looks valid but breaks when you try and use it. Thank you for your comment David. However, KDE 4 implement some fallback in that case so Plasma 5 could do the same to. With KDE 4, in these cases, I had not problem with crashes. I was able to access to Firefox, download the new Nvidia driver, install it from "init 3" level and reboot the system. With Plasma 5, I need to close session or <Ctrl><Alt><[2x]Backspc> and login with other desktop environment to access Firefox and proceed as I said in previous paragraph. So, there should be a solution to this problem. |