https://bugs.kde.org/show_bug.cgi?id=414803

            Bug ID: 414803
           Summary: Losing/corrupted multi-monitor configuration with TB
                    3.0 dock
           Product: plasmashell
           Version: 5.16.5
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Severity: grave
          Priority: NOR
         Component: Multi-screen support
          Assignee: aleix...@kde.org
          Reporter: arca...@ivanov.biz
                CC: plasma-b...@kde.org
  Target Milestone: 1.0

I'm on a laptop (Dell Precision 5540, Intel + NVidia w/Optimus) that plugs into
Dell WD19TB dock that is hooked up to 2x4k monitors. I am plagued by constant
failures to configure/restore monitor configuration. 

The topology is usually in a form of DP2(4K@60Hz) + DP1-1(4K@60Hz) + eDP1
(1080P@60Hz). 


The scenario usually goes like this:

1. Laptop is plugged into the TB dock. Displays are adjusted to desired
configuration.
2. Laptop is unplugged, used with eDP1.
3. Laptop is plugged back into the TB dock. 

After #3 there are the following scenarios:

a. Configuration and layout restores.
b. Configuration and layout restores, but one of the monitors fails to turn on,
the framebuffer seems to indicate that it is turned on properly but monitor
shows up as not enabled and checking enable and clicking apply does nothing.
c. Both external monitors fail to turn on, enabling them in Displays fails
completely: Enable boxes are cleared after apply, there isn't even an attempt
to enable them, framebuffer is seemingly adjusted as if they were enabled (but
sometimes not).


I'm sick and tired of this to the point I'm willing to debug and fix this
myself (looks like timings etc and improper xrandr commands issued).

Can someone please advise me which modules I need to look at and how to enable
debug logging for monitor configuration?

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 31
(available in About System)
KDE Plasma Version: 5.16.5 
KDE Frameworks Version: 5.64.0
Qt Version: 5.12.5

Possibly related to 365213

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to