<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - DP MST problems with xrandr while re-docking" href="https://bugs.freedesktop.org/show_bug.cgi?id=80355#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - DP MST problems with xrandr while re-docking" href="https://bugs.freedesktop.org/show_bug.cgi?id=80355">bug 80355</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>(In reply to <a href="show_bug.cgi?id=80355#c0">comment #0</a>) > And when I re-dock, I see the first xrandr output, but the monitors > don't light up. I am not able to use xrandr to set a mode for them, > i.e. this fails: > > $ xrandr --output DP3 --mode 1920x1080 > > xrandr: cannot find mode 1920x1080 > > As a result of this gnome-settings-daemon seems to crash. > > I noticed that this does not happen if I dock the notebook after booting > it un-docked. The xrandr output is different if I boot up un-docked; it > does not have DP3, DP4, DP5, but they show up when I dock it. The > problem surfaces if I un-dock and then re-dock. > > I guess the problem happens when the outputs DP3, DP4, DP5 are not > removed in xrandr when the notebook is un-docked. They are not meant to be as Clients blow up if RandR outputs disappear. What is odd is the DP names, they should have the topology information in them for MST devices (so that the names are stable across dock events). What exactly does xrandr say after you plug the dock back in? If you recompile the ddx with --enable-debug=full that will provide some more information about the output reattachment.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>