<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Unable to detect monitor modes connected to a TB16 Dell dock"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111507#c24">Comment # 24</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Unable to detect monitor modes connected to a TB16 Dell dock"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111507">bug 111507</a>
from <span class="vcard"><a class="email" href="mailto:lionel.g.landwerlin@linux.intel.com" title="Lionel Landwerlin <lionel.g.landwerlin@linux.intel.com>"> <span class="fn">Lionel Landwerlin</span></a>
</span></b>
<pre>(In reply to Stanislav Lisovskiy from <a href="show_bug.cgi?id=111507#c19">comment #19</a>)
<span class="quote">> (In reply to Lionel Landwerlin from <a href="show_bug.cgi?id=111507#c18">comment #18</a>)
> > Another piece of information that might help to pin the issue, I can boot
> > the system with both monitor (internal/external) showing the same thing and
> > even in GDM, I'm able to log in and see that both monitors are setup and
> > properly configured to show at least a background on the external monitor
> > and the logging screen on the internal monitor.
> >
> > The issue appears after the hand-off from GDM to the gnome-shell session of
> > the user. At no point was the monitor disconnected, so maybe that's nothing
> > to do with hotplug events?
>
> Does the display work in console mode? I mean if you boot with "3" option in
> the kernel command line.</span >
The external monitor works again as soon as switch to a virtual console.
So looks like an application issue?
It's weird that going back to an older kernel I don't run into the issue.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<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>