Hi,
I just noticed the symptoms of this on my own system. Does every installation
affected by this bug need manual intervention to undo the automatically-enabled
user unit, or should the fixed package do that itself? If the former, for those
not familiar (myself included), could you suggest
On 2021-12-19 at 14:22:03, Alexandre Viau (alexan...@alexandreviau.net) wrote:
> Ah, it was dh-systemd enabling the user unit by default.
>
> Since the user unit is not the only way to use syncthing, I would say
> that disabling it by default is a better choice.
The other thing is that I'd say
On 2021-12-19 at 13:12:58, Alexandre Viau (av...@debian.org) wrote:
> Can you please show us the output of:
> - $ ls -l /etc/systemd/user/default.target.wants/
I do have Syncthing in there:
lrwxrwxrwx 1 root root 35 Jul 22 2019 dunst.service ->
/usr/lib/systemd/user/dunst.service
lrwxrwxrwx 1
Hello/Salut Francois,
Could it be that you globally enabled the syncthing systemd user unit?
Can you please show us the output of:
- $ ls -l /etc/systemd/user/default.target.wants/
Thanks,
--
Alexandre Viau
av...@debian.org
Package: syncthing
Version: 1.18.0~ds1-1
Severity: normal
I've noticed a couple of odd things in my logs since a recent SyncThing
upgrade.
The first one is that a new SyncThing device I can't identify is now being
advertised from my laptop. The ID I see being advertised is not the one I
use on
5 matches
Mail list logo
