evdi VS wayvnc

git clone https://github.com/DisplayLink/evdi.git

So I'm currently on Ubuntu 22.10 with Mesa and asahi-edge kernel. You need both to allow using primary GPU as source output. I'm using evdi 1.13.1 with the correction to set the module to the 1.12.0 to run the script displaylink from Synaptics for Ubuntu.

The RPM version never worked for me. It's only useful for getting the services installed. After that clone the repo from https://github.com/DisplayLink/evdi and change to the devel branch. Run make and sudo make install. If you use SecureBoot you also need to sign the resulting evdi.ko with your key. After that restart displaylink.service or reboot and it should work. At least it did for me. I's been a while since I had to use it.

Uninstallation steps complete. darren@pop-os:~/displaylinkfix$ ./displaylink-driver-5.6.1-59.184.run --noexec --keep Creating directory displaylink-driver-5.6.1-59.184 Verifying archive integrity... 100% MD5 checksums are OK. All good. Uncompressing DisplayLink Linux Driver 5.6.1-59.184 100% darren@pop-os:~/displaylinkfix$ cd ./displaylink-driver-5.6.1-59.184 darren@pop-os:~/displaylinkfix/displaylink-driver-5.6.1-59.184$ curl -L https://github.com/DisplayLink/evdi/archive/refs/heads/devel.tar.gz -o evdi.tar.gz % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 80603 0 80603 0 0 179k 0 --:--:-- --:--:-- --:--:-- 179k darren@pop-os:~/displaylinkfix/displaylink-driver-5.6.1-59.184$ nano darren@pop-os:~/displaylinkfix/displaylink-driver-5.6.1-59.184$ nano evdi.tar.gz darren@pop-os:~/displaylinkfix/displaylink-driver-5.6.1-59.184$

I'm afraid this might be a hardware issue, maybe with the cable. I don't have a second cable to swap out unfortunately. A new one won't be here until Saturday. And it seems like a hell of a coincidence for the cable to fail when there's other issues reported within the last few days that seem very similar.

https://github.com/DisplayLink/evdi states

Theres a bug in the 6.2 kernel right now with at least the evdi package (dont know about evdi-git) but can be fixed with a patch. Pr for it is already open but yet to be merged https://github.com/DisplayLink/evdi/pull/401

You can run remote applications with Wayland now: https://access.redhat.com/documentation/en-us/red_hat_enterp...

There is also a VNC server for fullscreen sessions (only supports wlroots compositors for now): https://github.com/any1/wayvnc

There's wayvnc.

It says on their GitHub page that "Gnome, KDE, and Weston are not supported". What does that mean?

I thought this existed in the form of wayvnc but from their README it seems they don't support the popular desktop environments (GNOME, KDE).

Not sure if I would call it hassle free, but wayvnc isn't that hard to set up.

And wayvnc

There is however a fresh issue on the wayvnc github with what looks like your problem. https://github.com/any1/wayvnc/issues/206

On wayvnc git master and sway 1.8 (or git master), you can script things so that a "virtual" display gets created automatically when someone connects to VNC, and removed when they disconnect.

See https://github.com/any1/wayvnc/pull/200/files

The script in the PR does something a bit different, but it's only an example and can be modified to do what I described in the first paragraph.

No - it's not X, it's doesn't share a screen in the way X does.

That said... if this is a shoddy attempt at a "gotcha" style question - Screen sharing and remote desktop are both supported.

Ex - for Gnome:

https://wiki.gnome.org/Projects/Mutter/RemoteDesktop

LibVNCServer for VNC support, FreeRDP for remote desktop protocol.

For KDE:

https://userbase.kde.org/Krfb

Which mostly just works as long as you have Pipewire and xdg-desktop-portal-kde installed (the base plasma-wayland session usually includes them)

This one is a bit less polished - some users still have problems with keyboard input, depending on the distro and other installed packages.

For Sway:

xdg-desktop-portal-wlr works just fine for screen sharing, and you can use https://github.com/any1/wayvnc for VNC access (including having a completely headless machine).

Ah right, looks like the VNC server you're using is xorg only. You can try WayVNC for gaming mode https://github.com/any1/wayvnc .