-
Notifications
You must be signed in to change notification settings - Fork 343
After 713c166, output disconnection/reconnection doesn't work reliably #2499
Comments
Can you obtain DRM debug logs? See https://github.com/swaywm/wlroots/wiki/DRM-Debugging |
Of course: dmesg: https://paste.ubuntu.com/p/srPqWBh6Jr/ Start sway, wait a few seconds for it to settle, disconnect thunderbolt dock, wait a few seconds for it to settle, reconnect, wait a few seconds for it to settle and log out of sway when it became apparent the displays weren't coming back. |
Another thing to note. If I use just the HDMI display and I connect it straight into the connector on the laptop the issue does not happen. |
I also started having troubles after 713c166 My external monitor is connected over HDMI over USB-C dock. Its highest resolution is 2560x1440. Previously it worked fine but after that commit, I only get 1920x1080 resolution. I followed the suggestion to use |
This reverts commit 713c166. It turns out we do need to force-probe on startup and on hotplug [1]. This is unfortunate, but that's just how the uAPI works. Fixing this would require patching the kernel. [1]: https://lists.freedesktop.org/archives/dri-devel/2020-November/289506.html Closes: swaywm#2499
This reverts commit 713c166. It turns out we do need to force-probe on startup and on hotplug [1]. This is unfortunate, but that's just how the uAPI works. Fixing this would require patching the kernel. [1]: https://lists.freedesktop.org/archives/dri-devel/2020-November/289506.html Closes: #2499
Thank you 👍 |
After updating past 713c166, sway seems to have trouble knowing when outputs have been disconnected or reconnected. I'm attaching a debug log of a sway session where:
get_outputs
still reports all 3 displays connectedsway log: https://paste.ubuntu.com/p/HXMt3c8mVC/
get_outputs: https://paste.ubuntu.com/p/9yQPkrBPsV/
uname -a:
i7-7700HQ & intel graphics hd630
wlroots: 6485fad
sway: sway version 1.5-32b93ef6 (Nov 26 2020, branch 'master')
Rolling back my wlroots version to 154fe86 fixes the issue for me.
The text was updated successfully, but these errors were encountered: