Arch Linux User Repository

@halfur, The reason linux-headers and linux-lts-headers are both optional dependencies of dkms is because you can have either one installed, or even a third-party linux-*-headers package. Making it a dependency of this package would force people that are using other kernels to install a package they don't need. This is the way that all dkms packages, such as nvidia-dkms, handle this. I'll make them optional dependencies in the next release.

"linux-headers" should be added to the dependencies, it's only an optional dependency of dkms, but is required for installing this package after building.

I just released a new package version that should fix the issues installing this package with AUR Helpers. @ryanvade what kernel are you using?

I can't seem to build evdi. Oct 05 10:33:36 ryanvade-arch modprobe[7339]: modprobe: FATAL: Module evdi not found. DKMS is not building the module.

@Hideaki, I think you try to ask this question in this ticket https://github.com/aurapm/aura/issues/351 I'm not a aura expert, but they are (or should be..)

I haven't tested AURA, only manual builds and yaourt. What does AURA do differently? It looks like its failing to extract displaylink's .run package during the build section. Should I move that to the package section?

For those using AURA run aura with the -x statement, so for example aura -Ax displaylink This has to do with some unusual statemens in the package() part. More info here https://github.com/aurapm/aura/issues/351

@kloetzl, it seems aura is not working with the displaylink package.. In general Accourding to this forum http://displaylink.org/forum/showthread.php?t=64043&page=2 the display-manager.service should be started before the displaylink service. In my case display-manager serivce is provided by lightdm. This service is running, but i still get the same error. If i run sudo /usr/lib/displaylink/DisplayLinkManager terminate called after throwing an instance of 'dl::sys::Failure' what(): Hive format not recognised

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.