When I start Fragments, Fragments shows this message:
Connection error
Failed to establish a connection with the Transmission service
("transmission error").

Workaround
=========
Click ☰ > Add Remote Connection…
Enter localhost for Name and Host
On the next page, enter "transmission" for the username and password

Thank you,
Jeremy Bícha

Hi,
this is a know bug and upstream said that they won't fix it.
[0]
Maybe we should add a README for our users ?

best,

werdahias

Links:

[0]: https://gitlab.gnome.org/World/Fragments/-/issues/224

Control: forwarded -1 https://gitlab.gnome.org/World/Fragments/-/issues/224

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.

I don't know anything about openRC and I'm surprised you are or were using it.

A solution might require patching transmission.

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.

Thank you,
Jeremy Bícha

Yeah, that would be unfortunate. What also works is stopping
transmission-daemon manually and then launching fragments.
Still using it; I dislike how systemd tries to do *everything*; IMO an
init program should just start the system (and manage services).
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.
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