<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Hard lock when unplugging and reconnecting external USB-C DP display"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103474#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Hard lock when unplugging and reconnecting external USB-C DP display"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103474">bug 103474</a>
from <span class="vcard"><a class="email" href="mailto:daniel.playfair.cal@gmail.com" title="Daniel Playfair Cal <daniel.playfair.cal@gmail.com>"> <span class="fn">Daniel Playfair Cal</span></a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=135137" name="attach_135137" title="Stacktrace of gnome-shell user session crash when disconnecting the display">attachment 135137</a> <a href="attachment.cgi?id=135137&action=edit" title="Stacktrace of gnome-shell user session crash when disconnecting the display">[details]</a></span>
Stacktrace of gnome-shell user session crash when disconnecting the display
It does say "Connection to xwayland lost"
If XWayland can't handle a display being unplugged,then why is it that when I
unplug a display without using this usb-c to displayport adapter my shell
usually doesn't crash? And how can I see why XWayland crashed?
I updated my BIOS and thunderbolt controller firmware to the latest, I'm not
sure if it made any difference.
I tried disabling my display manager, booting into a console, and disconnecting
and reconnecting the screen repeatedly. In that case, everything works fine.
Unfortunately the coredump for the second gnome-shell crash never seems to
complete. When it crashes after reconnecting the displayport adapter, often the
caps lock light flashes on and off repeatedly for a few seconds, then the power
light turns off (but the screen statys on). The image of the display manager
flashed back on the screen, and then turned black. Next I saw the post screen
(power light still off) for a few seconds, then the computer turned off.
My microcode should be up to date - my bootloader is configured as follows:
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
and I have intel-ucode 20170707-1 which is the latest for Arch.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>