<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - DP ports relabeled" href="https://bugs.freedesktop.org/show_bug.cgi?id=100576#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - DP ports relabeled" href="https://bugs.freedesktop.org/show_bug.cgi?id=100576">bug 100576</a> from <a class="email" href="mailto:pmenzel@molgen.mpg.de" title="Paul Menzel <pmenzel@molgen.mpg.de>"> Paul Menzel</a> <pre>(In reply to Jani Nikula from <a href="show_bug.cgi?id=100576#c6">comment #6</a>) > (In reply to Paul Menzel from <a href="show_bug.cgi?id=100576#c5">comment #5</a>) > > I don’t know that either. But from a user perspective it’d be a good thing, > > that the label next to the port match what `xrandr` shows. > > Now *that* is most certainly not guaranteed. The OEMs can stick whatever > labels to the chassis, and have whatever mechanisms to have them show up > with those labels in Windows. Understood, so I guess, I was just lucky in this case. Please ignore that comment about the label on the device then, as it’s unrelated to the problem at hand. Either way, relabeling is a regression, as it breaks user space, where people might use xrandr scripts to set certain things up, which doesn’t work anymore.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>