Elias Probst

This bug isn't very clear about whether to add support for Ogg Vorbis for the source files or for the output files. Care to elaborate (although I'd love to see...

Any data I could provide from Android (does it maintain a local SQLite DB?) of the App in this erroneous state that could help debug this further?

> And that's the possible fix I'm thinking of: throw away current shares from local DB, add the constraint and let the sync recover the truth from server to local...

This seems to be a bug of pyinotify: https://github.com/seb-m/pyinotify/issues/192 The [original project](https://github.com/seb-m/pyinotify) seems to be [unmaintained since ~2015](https://github.com/seb-m/pyinotify/commits/master) and while there's a [little better maintained fork](https://github.com/dsoprea/PyInotify/commits/master) of PyInotify available, [pypi...

Same happens for me when adding a regular worker - seems to be a general issue with adding workers.

It looks to me like this is mostly a problem of not checking, whether the currently active context matches the one being deleted.

It might be easier to rebase everything onto Ubuntu 18.04 (which should be done at some point anyways) instead of trying to get such an old Kernel working…

Seeing the same issue on Gentoo, using version 1.10.1. By default, Gerbera/libupnp binds to this local interface: ``` 8: bridge0: mtu 1500 qdisc noqueue state UP group default qlen 1000...

Problem still exists in Nextcloud 3.0.2.1 and Deck 1.6.1

Result of `nixpkgs-review pr 190558` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review) 3 packages built: imapsync perl534Packages.EncodeIMAPUTF7 perl536Packages.EncodeIMAPUTF7