David Girón

If you provide full output of `rpm-ostree status`, it may help to identify this. Also if you have different version, does `rpm-ostree rollback` fix this?

Does it work with `mysoftvol`? LX01 has these 2 different volumes which add up.

Issue is still reproducible with `v8.2.1` : `Expect failure when recreating user with same values` POST `/scim/v2/Users` :x: Status — `201` was not a number equal to `409` 📝 https://developer.okta.com/docs/guides/scim-provisioning-integration-prepare/main/...

Feel free to open a PR with the feature improvement, as long as we can use current free models 👍🏻

@nekromant can you share what firmware version and speaker model are you using to build the image?

Since the reported issue is related to `blue-alsa` not starting, this was already fixed in 00d29c68c7c9234f29ec65f4d8486767fdfa45b4 . The failure is unrelated to the patching itself.

The ethernet NIC seems to be Intel® I219-V Gigabit LAN , can you confirm or get more details? Any errors logged in system `dmesg` or other? Have you run any...

Other than running `autoreconf -fi` and this is a cross-build, I don't think there are more changes. See file here, I will attach a build log later on https://github.com/duhow/xiaoai-patch/blob/0d3ed64706c7bed3ff81a93b1ff6c5b16d0d4428/packages/dropbear/package.mk

> autoconf (GNU Autoconf) 2.69 [configure](https://github.com/user-attachments/files/18123642/configure.txt) [config.log](https://github.com/user-attachments/files/18123649/config.log)

Failure to run is due to `syntax error` (unexpected `:` as is invalid), although I see your point of "should not be processed" as the condition is not met in...