Bug 464414 - Monitor Desktops disappear and are not interactive
Summary: Monitor Desktops disappear and are not interactive
Status: RESOLVED DUPLICATE of bug 353975
Alias: None
Product: neon
Classification: KDE Neon
Component: general (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR major
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-17 16:19 UTC by Chris
Modified: 2023-01-17 21:57 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris 2023-01-17 16:19:12 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Install KDE Neon
2. Login
3. Allow the screen to lock
4. Come back after 15-20 minutes and enter password to unlock


OBSERVED RESULT
5. At least one monitor goes black, while the other one resembles a desktop you set up for yourself, but is often missing widgets or other components.. toolbars often times on wrong desktop, or missing altogether.  Sometimes both monitors are black and non-interactive... sometimes both are there, but reversed (rarely, but has happened)
6.  This seems to happen any time the screen locker is engaged for probably 10-15 minutes or more.  On short-duration locks, this does not usually occur.

EXPECTED RESULT
I expect to unlock my screen locker, and see my desktops as I have configured them.  They should work as any other normal desktop.  

Instead, every time this happens, it costs me 20 minutes to reset my monitors, my task bars and my widgets (which I use heavily, mostly 'folder view' for quick access to numerous applications and remote sessions).

SOFTWARE/OS VERSIONS
Windows: N/A
macOS:  N/A
Linux/KDE Plasma:  22.04
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Graphics: Quadro RTX 5000/PCIe/SSE2
Product Name: Precision Tower 7810
Graphics Platform: X11

ADDITIONAL INFORMATION
Recently, I've been having issues with my Desktop Monitor configuration too stating: "An output has been removed. Settings have been reloaded."  It will flash this for 2 seconds, then switch to "An output has been added. Settings have been reloaded."  It would loop like that indefinitely.  The monitor would show, and disappear in the drop down every 2 seconds or so.  After obliterating my unix profile, this has finally stopped, but the other problems persist.

This has been going on since the last major KDE Neon release (22.04).  I have tried wiping all my plasma and KDE settings.   I've worked from a completely pristine profile.  I've tried wiping my nvidia settings. I have tried changing monitor settings, I have swapped out different monitors -- I even swapped out different graphics cards.   I Swapped Display port cables with known good ones. I have played with every driver available for my nvidia quadro card.  Every time the same result.  I thought that I had this numerous times now, but every time I go away from my  desk for more than 20 minutes, I'm proven wrong.  Normally I have probably 2 dozen sessions, applications and terminals open across 4 different desktops. Rebooting is the only thing that comes close to a "cure"... but even then, the desktops are usually a mess: they are reversed, they have no (or the wrong) panels, the widgets are missing, etc. etc.  I tried disabling kscreen2, but that just made both screens go black, and become unrecoverable.  I don't see anything in my X logs, or anything weird in my dmesg... I'm at a loss. I've spent countless hours trying to debug this.  I even tested this with a KDE Neon install disk -- same thing happens.

More information here: https://forum.kde.org/viewtopic.php?f=66&t=176035

I understand this is probably a bug... but is there at least a work-around I can use for this?  It is killing my productivity...

Thank you.
Comment 1 Nate Graham 2023-01-17 21:57:19 UTC
It should be finally fixed in Plasma 5.,27, thankfully!

*** This bug has been marked as a duplicate of bug 353975 ***