Matti Viljanen

As `details.md` says, major version number should be increased when incompatible API changes occur, yet only minor version was increased. This means that v1.12 should have been released as v2.0...

[DisplayLink 5.6.1](https://www.synaptics.com/products/displaylink-graphics/downloads/ubuntu) has been released, and it's compatible with evdi 1.12.0. Source: [changelog](https://www.synaptics.com/sites/default/files/release_notes/2022-08/DisplayLink%20USB%20Graphics%20Software%20for%20Ubuntu5.6.1-Release%20Notes.txt). The [DisplayLink AUR package](https://aur.archlinux.org/packages/displaylink) is still at 5.6 at the time of writing. A self-bumped version works...

@olof-nord Evdi 1.12 doesn't work with displaylink 5.6. The dependencies go like this (using Arch versioning): * `displaylink 5.6-1` `evdi 1.11.0-1` * `displaylink 5.6.1-1` `evdi 1.12.0-1`

You seem to be missing the kernel headers package: `$ sudo apt install linux-headers-generic`

The library has been updated recently; does validation still fail for that number?

There seem to be conflicts that prevent merging. I could _try_ to redo your patch against the current master... @madhums Is this fine with you?

Any news on this? I would like to use `patience` as it suits my project a lot better than `myers`...

It looks like a thing and a half to get Starfish accepted to Jolla Store, because it has to be able to install `systemd` services, has multiple binary files and...

I remember having to handle the uppercase/lowercase UUID strings, too, in my [futile attempt](https://github.com/AsteroidOS/asteroidsyncservice/files/7192828/bluezclient.cpp.txt) to get Bluez 5 support up and running...

I tried it again some time ago, and the behavior doesn't change, if the watch is actually connected or not... So there's still something else going on. That was the...