Bug 413326 - secondary screen goes black after login, mouse still visible
Summary: secondary screen goes black after login, mouse still visible
Status: RESOLVED DUPLICATE of bug 353975
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.17.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-22 18:30 UTC by lesto
Modified: 2022-09-09 06:30 UTC (History)
2 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 lesto 2019-10-22 18:30:58 UTC
SUMMARY
I have a dual monitor setup, since I think version 5.15.0 (sorry i can t be more precise) one stopped working correctly.

It work fine in SDDM, but as soon as i login it became black, and i can see only the mouse; trying to drag a windows there, it will show only the mouse. Turning off and on the monitor fix it, and it start work normally.

This secondary monitor also is in vertical mode.

Before this version it was working 100% of the times

STEPS TO REPRODUCE
1. turn on pc
2. log into sddm

OBSERVED RESULT

the secondary vertical monitor goes black, but the mouse still can be seen; no desktop, icons, widget or windows. Turning the monitor off and on fixes it

EXPECTED RESULT
my normal desktop

SOFTWARE/OS VERSIONS

arch linux, probably the issue is from a couple of month (today is 2019-10-22), on xorg

ADDITIONAL INFORMATION
worked fine for many month.
Using a nVidia card, with proprietary driver.
Comment 1 lesto 2019-10-22 18:52:35 UTC
part of 3 bug report: 413326 413328 413329
Comment 2 lesto 2019-10-24 17:54:02 UTC
fixed by deleting the kscreen folder under ~/.local/share; looks like even if I enable/disable the monitors and change the conf, something broken get carried over.

I think proper fix should be to find the problematic configuration and get rid of it at load time
Comment 3 galder 2022-09-09 06:30:30 UTC

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