Karlchen
That's an interesting topic: How do we detect that a file is still written without trying to write it ourselves?
All files are created in the same folder as the database.
Maybe you can take a look at the examples for nginx and apache (https://docs.gerbera.io/en/stable/run.html#reverse-proxy-setup), but I don't know `Caddy`
1.12.1 had some issues with Samsung devices which are fixed in 2.0. I know that jfrog is not available now to get our current build.
In that case, we should try to circle the issue in 2.0
Can you share the respective log fro. 2.0 Please, keep in mind that there are config changes from 1.12 to 2.0. Best generate the new with `--create-config` and compare.
In the current head the second one disappears if you disable the client flag for SAMSUNG: https://github.com/gerbera/gerbera/blob/8834e9db0c00cc6de6529d40008784f8aad18d97/src/device_description_handler.cc#L155 Is also the non-X_ key causing trouble? My prime suspect is the `DMC10`...
> Yup, tried the 2.1.0. Thanks a bunch! > > I know all too well how it feels as a volunteer, with family & stuff on the side ... ....
How did you trigger the import, because I cannot reproduce it.