Summary: | kwin crashed after unlock screen (2 local sessions) | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Thomas Boerkel <thomas> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | thomas |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.8.5 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Thomas Boerkel
2017-02-28 18:13:47 UTC
I have 2 monitors. The 2nd monitor is attached, but not active in xorg.conf or KDE system settings. If I activate and configure the 2nd monitor as separate X screen (:0.1), then the whole session or the lock screen crashes pretty often. So, for the moment, I only have the kwin crashes, while I am only using the main monitor. I am using the binary Nvidia gfx driver. Do I understand correctly that you switched away from the session to another one? That is unfortunately a well known NVIDIA issue. They purge the memory of the objects we created without telling us (well now they do, but it would need special code on our side and only works with the latest, latest NVIDIA driver.) Yes, I switched the local session with CTRL-ALT-F8 prior to the crash. Usually, I have 2 local users logged in (VT7 and VT8). I am sharing this computer with my wife. I have used this setup for many years without problems with KDE 4. I just finally updated to Plasma 5 (Gentoo). Is there a workaround? I tried to switch to Nouveau, but that is not working fast/stable enough on my hardware. I think that's just another case of the well known "NVIDIA cannot handle VT switches bug". In that case it should be fixed with Plasma 5.10.3 *** This bug has been marked as a duplicate of bug 344326 *** |