displaylink-debian
displaylink-debian copied to clipboard
AdnanHodzic
Full Wayland support
It seems that displaylink-debian does not support Wayland, when reading the prerequisites:
“When you are logging into your session you are using X server (X11) and not Wayland.”
However Displaylink should have Wayland support.
When I do: sudo -E ./displaylink-debian.sh --debug on my Librem 5 running PureOS, I get:
Can't open display
My guess is that this is because the phone runs Wayland.
See also this forum topic.
I outcommented this line:
providers="$(xrandr --listproviders)"
the script continues now after this line.
Both on my Librem 5 with PureOS and on my Fedora 37 Wayland only systems xrandr --listproviders gives Can't open display. The command xrandr --listmonitors however gives output like:
Monitors: 1
0: +WAYLAND0 360/65x720/130+0+0 XWAYLAND0
I tried installing displaylink-debian again on my Librem 5. After installation, the login screen does not appear, and the screen stays black. I noticed this in the prerequisites: "When you are logging into your session you are using X server (X11) and not Wayland." Maybe this is the reason why the login screen stayed black after the reboot. Fortunately, I could still login via ssh to remove displaylink-debian. After uninstalling the login screen was there again after a reboot.
+1 on this issue. Debian bookworm comes standard with wayland. Would love to help out and make this work :)
+1 also, all major DE are dropping X11 in the coming year so I could be nice to support wayland
FWIW somewhat surprisingly it actually works for me on Wayland (Debian bookworm) and not X11 (heavily glitchy to the point of being unusable), AMD Ryzen 7000 laptop with integrated graphics, KDE Plasma.
Yeah same for me since evdi update, I only have a black screen on SDDM but the rest is working, I get a lot of CPU usage but this is a DisplayLink driver problem not the implementation of this script
May be I was too quick to consider it fully working, so far the only issue is that after reboot I need to re-plug DL monitor into another USB port, then it's properly detected. Could be worse I guess, glad that it's working in principle.