Arch Linux User Repository

Hi, Tried to install this package, but I'm encountering the following error. Apparently the script doesn't like my gnome-terminal. % sudo aura -A displaylink aura >>= Determining dependencies... aura >>= AUR Packages: displaylink aura >>= Continue? [Y/n] aura >>= Building `displaylink`... aura >>= Well, building `displaylink` failed. aura >>= Dumping makepkg output in 3.. 2.. 1.. ==> Making package: displaylink 1.0.138-2 (Sat Sep 19 16:24:30 CEST 2015) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Downloading DisplayLink-Ubuntu-1.0.138.zip... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 5751k 100 5751k 0 0 710k 0 0:00:08 0:00:08 --:--:-- 990k -> Found 99-displaylink.rules -> Found displaylink.service -> Found displaylink-sleep.sh ==> Validating source files with md5sums... DisplayLink-Ubuntu-1.0.138.zip ... Passed 99-displaylink.rules ... Passed displaylink.service ... Passed displaylink-sleep.sh ... Passed ==> Extracting sources... -> Extracting DisplayLink-Ubuntu-1.0.138.zip with bsdtar ==> Starting build()... ./displaylink-driver-1.0.138.run: line 400: exec: -t: invalid option exec: usage: exec [-cl] [-a name] [command [arguments ...]] [redirection ...] ==> ERROR: A failure occurred in build(). Aborting...

@Hideaki: Installed the new version no problem. However, the "DisplayLinkManager" still keep crashing with the same message: * displaylink.service - DisplayLink Manager Service Loaded: loaded (/usr/lib/systemd/system/displaylink.service; enabled; vendor preset: disabled) Active: activating (auto-restart) (Result: core-dump) since Wed 2015-09-16 19:23:18 AST; 2s ago Process: 2057 ExecStart=/usr/lib/displaylink/DisplayLinkManager (code=dumped, signal=ABRT) Process: 2055 ExecStartPre=/sbin/modprobe evdi (code=exited, status=0/SUCCESS) Main PID: 2057 (code=dumped, signal=ABRT) Sep 16 19:23:18 GatewayPC-Office systemd[1]: Stopped DisplayLink Manager Service. Sep 16 19:23:18 GatewayPC-Office systemd[1]: Starting DisplayLink Manager Service... Sep 16 19:23:18 GatewayPC-Office systemd[1]: Started DisplayLink Manager Service. Sep 16 19:23:18 GatewayPC-Office systemd[1]: displaylink.service: Main process exited, code=dumped, status=6/ABRT Sep 16 19:23:18 GatewayPC-Office systemd[1]: displaylink.service: Unit entered failed state. Sep 16 19:23:18 GatewayPC-Office systemd[1]: displaylink.service: Failed with result 'core-dump'. Sep 16 19:23:18 GatewayPC-Office DisplayLinkManager[2057]: terminate called after throwing an instance of 'dl::sys::Failure' Sep 16 19:23:18 GatewayPC-Office DisplayLinkManager[2057]: what(): Hive format not recognised Sep 16 19:23:18 GatewayPC-Office systemd-coredump[2059]: Process 2057 (DisplayLinkMana) of user 0 dumped core.

mmm can be a aura Issue. If i download the snapshot, run makepkg an install it with pacman the installation works. But i'm still getting the same issue as solo9300

Hi, I'm getting this error during build $ sudo aura -A displaylink aura >>= Determining dependencies... aura >>= AUR Packages: displaylink aura >>= Continue? [Y/n] y aura >>= Building `displaylink`... aura >>= Well, building `displaylink` failed. aura >>= Dumping makepkg output in 3.. 2.. 1.. ==> Making package: displaylink 1.0.138-2 (Wed Sep 16 13:59:56 CEST 2015) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Downloading DisplayLink-Ubuntu-1.0.138.zip... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 5751k 100 5751k 0 0 2687k 0 0:00:02 0:00:02 --:--:-- 2688k -> Found 99-displaylink.rules -> Found displaylink.service -> Found displaylink-sleep.sh ==> Validating source files with md5sums... DisplayLink-Ubuntu-1.0.138.zip ... Passed 99-displaylink.rules ... Passed displaylink.service ... Passed displaylink-sleep.sh ... Passed ==> Extracting sources... -> Extracting DisplayLink-Ubuntu-1.0.138.zip with bsdtar ==> Starting build()... ==> Entering fakeroot environment... ==> Starting package()... /var/cache/pacman/pkg/displaylink347/displaylink/PKGBUILD: line 27: cd: displaylink-1.0.138: Not a directory ==> ERROR: A failure occurred in package(). Aborting... aura >>= Would you like to continue anyway? [Y/n] n aura >>= Building failed. -- i've also build it manually but then i get the same error als solo9300

@solo9300: I just pushed a new version from upstream that fixes many issues. Could you please test it and report back?

Hello, for some reason I could not get the displaylink to work. the "DisplayLinkManager" keep crashing. linux and linux-headers is installed # uname -r 3.14.51-1-ARCH # xrandr --listproviders Providers: number : 1 Provider 0: id: 0x54 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 2 outputs: 3 associated providers: 0 name:radeon # systemctl status displaylink.service * displaylink.service - DisplayLink Manager Service Loaded: loaded (/usr/lib/systemd/system/displaylink.service; enabled; vendor preset: disabled) Active: activating (auto-restart) (Result: core-dump) since Sat 2015-09-12 21:47:36 AST; 2s ago Process: 3470 ExecStart=/usr/lib/displaylink/DisplayLinkManager (code=dumped, signal=ABRT) Process: 3467 ExecStartPre=/sbin/modprobe evdi (code=exited, status=0/SUCCESS) Main PID: 3470 (code=dumped, signal=ABRT) Sep 12 21:47:36 GatewayPC-Office systemd[1]: Stopped DisplayLink Manager Service. Sep 12 21:47:36 GatewayPC-Office systemd[1]: Starting DisplayLink Manager Service... Sep 12 21:47:36 GatewayPC-Office systemd[1]: Started DisplayLink Manager Service. Sep 12 21:47:36 GatewayPC-Office systemd[1]: displaylink.service: Main process exited, code=dumped, status=6/ABRT Sep 12 21:47:36 GatewayPC-Office systemd[1]: displaylink.service: Unit entered failed state. Sep 12 21:47:36 GatewayPC-Office systemd[1]: displaylink.service: Failed with result 'core-dump'. Sep 12 21:47:36 GatewayPC-Office DisplayLinkManager[3470]: terminate called after throwing an instance of 'dl::sys::Failure' Sep 12 21:47:36 GatewayPC-Office DisplayLinkManager[3470]: what(): Hive format not recognised Sep 12 21:47:36 GatewayPC-Office systemd-coredump[3471]: Process 3470 (DisplayLinkMana) of user 0 dumped core. any help would be greatly appreciated.

@ainola - Thanks for the input! I've submitted an updated package with that fixed as well as some other changes. @yah00ka - The udev issue should be fixed on this new package version.

Thanks for all your work! This is a friendly reminder that double quotes should be used with variables that contain spaces (such as $srcdir) in order to prevent word-splitting: http://mywiki.wooledge.org/WordSplitting Also, you don't have to have the extraneous functions like "makedepends=()" as they serve no purpose. But that's not really important.

Found it, I needed to install the xf86-video-intel driver before xrandr --setprovideroutputsource would work. Thanks for the help!

No that's not it. xrandr --listproviders does actually show me the providers but xrandr --listproviders --verbose does not show me the dvi ports they should provide starting/restarting the systemd daemon does not help... this is what xrandr shows me: # xrandr --listproviders Providers: number : 3 Provider 0: id: 0x45 cap: 0x2, Sink Output crtcs: 3 outputs: 3 associated providers: 0 name:modesetting Provider 1: id: 0x137 cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting Provider 2: id: 0x10b cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting # xrandr --setprovideroutputsource 1 0 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 35 (RRSetProviderOutputSource) Value in failed request: 0x45 Serial number of failed request: 17 Current serial number in output stream: 18 log files for both my monitors are created under /var/log/displaylink/, though the content are not human readable. I see the udev file makes mention of the plugdev group that does not exist on my machine though...