Bug#1101830: fragments: Connection error

[Matthias Geiger]

On Tue, 01 Apr 2025 16:26, Jeremy Bícha <jeremy.bicha at canonical.com> wrote:
>Control: forwarded -1 https://gitlab.gnome.org/World/Fragments/-/issues/224
>
>On Tue, Apr 1, 2025 at 10:00 AM Matthias Geiger <werdahias at riseup.net> wrote:
>> this is a know bug and upstream said that they won't fix it.
>> [0]
>> Maybe we should add a README for our users ?
>
>A README could help but we should keep this bug open until we figure
>out a better solution. I feel like this bug is a serious bug but
>because there are workarounds, I don't want Fragments to be excluded
>from Trixie because of this issue yet.
>
Yeah, that would be unfortunate. What also works is stopping 
transmission-daemon manually and then launching fragments. 
>I don't know anything about openRC and I'm surprised you are or were 
>using it.
Still using it; I dislike how systemd tries to do *everything*; IMO an 
init program should just start the system (and manage services). 
>A solution might require patching transmission.
>
The relevant code seems to be in src/backend/connection_manager.rs,
but from what I can gather it assumes fragments must start 
transmission-daemon.
>Maybe fragments is able to ship a systemd override for
>transmission-daemon.service so it does the right thing for typical
>Debian users using systemd.
I don't know a lot about systemd units, since I don't use it, but maybe 
a custom unit stopping transmisson-daemon on launch would work ?

best,

werdahias