Arch Linux User Repository

I think the pinned comment still holds. Recently I did updated my Arch again, and when using cinnamon or mate desktops, I can make it work with the comment from sickcodes on 2020-10-15 23:26 on the AUR evdi page (i.e. removes the udev rules.d file + disable displaylink service, then reboot, then start the displaylink service. I then have a flickering mouse pointer which is quite distracting.

When using Gnome Desktop, I don't need to do any of that.

Downloading xorg-server-git or downgrading xorg-server didn't do anything for me - xorg still crashes whenever I try to start with cinnamon or mate.

Revision: 1) downgrading xorg-server even further (to 1.19.6+13+gd0d1a694f-2) did resolve the xorg crashing issue; i previously only downgraded to 1.20.4. I now have the most up-to-date evdi and displaylink installed and I run it on the (current) LTS kernel. 2) The reason why GDM started is because it doesn't use Xorg-server, but Wayland (I didn't know that yet...)

Does the pinned comment still hold?

Is Displaylink still not compatible with evdi-1.8?

evdi-git now is at v1.8.0.r7

If the constrain still hold, I guess we need really need the evdi-1.7 package...

Bug report for xorg-xserver above 1.20.8-3 submitted : https://gitlab.freedesktop.org/xorg/xserver/-/issues/1088

Depends on what your error messages say? The folks at xorg (=freedesktop) probably will be more helpful with debugging. You can also post a link here to he bugreport once you have created it.

I can consistently repeat the breakages. In fact I have a local script to automatically revert all Xorg packages back to 1.20.8-3 versions because of this.

Whe you say upstream, do you mean 'displaylink' upstream or 'xorg' ?

@kaipee2 as I wrote in August and September: That is not generally true. I can not reproduce this on my system and others report success too. That said, if you find the reason, why Xorg > 1.20.8-3 does not work for you and several other (but not all!) users, please let us and upstream know. You can also report the problem without a solution. Please provide crashlogs then.

@dummys the latest versions of displaylink+evdi do not work with Xorg packages above version 1.20.8-3

yes you are right. I had a md5sum binary in /usr/local/bin, after removing it I can install the package. Still to understand what is bringing the xorg crash, but no time for now.

Looks like your md5sum command is broken.

Here is what it should look like:

% export LC_ALL=C
% which md5sum
/usr/bin/md5sum
% pacman -Qo /usr/bin/md5sum
/usr/bin/md5sum is owned by coreutils 8.32-1
% md5sum --version
md5sum (GNU coreutils) 8.32
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Ulrich Drepper, Scott Miller, and David Madore.
%

When trying to install this package, after installing evdi-1.7.0 I get the following error:

Verifying archive integrity... 100% Error in MD5 checksums: print mode: md5sum <file> <file check mode: md5sum -c <checksum is different from 7ba0e635b6284f0651177ec1e63381d0 ==> ERROR: A failure occurred in package(). Aborting... error making: displaylink

I'm trying to debug, but I think it's their .run install scrit which is broken... It seems that they are using md5sum like this cat "binary_data" | md5sum, which is not working at all if I test. The only way I'm able to do this is with "md5" command...

Found more, after extracting it from ubuntu vm, I copied everything like PKG does. The driver is working, but when I connect displaylink, I can switch to the screen, whitout problem, but when restarting lightdm, no more screen, and huge crash in the journalctl. I tried connecting usb before boot, same problem. I tried switching back to the laptop screen before restarting lightdm, same problem. My kernel version is: 5.8.14-arch1-1