Thanks Alexandre. About the _ for - names, I didn't see the underscore ones
in the manual. That explains that.
I just read the notes about start_paused. I set it to start_paused as false
because I thought that would fix this behaviour:
I have this behaviour, that after a torrent has downloaded (100%) it
goes into the paused state and doesn't start seeding.
But starting to seed after downloading was the previous default
behaviour (Transmission 3.0).
Now, it isn't. I have to manually resume the torrents for them to seed.
There doesn't seem to be a configuration setting for this. I thought it was
this start_paused.
Thanks, W
On Fri, Sep 5, 2025 at 4:39 PM Alexandre Rossi <[email protected]> wrote:
> Hi,
>
> > * I upgraded to the 4.1.0 version of the transmission-daemon as part
> of an upgrade to trixie.
> > * I used my previous settings.json file and found that entries like:
> start-paused now appear
> > as start_paused. These settings seem to be new to this version of
> transmission-daemon, viz.
> >
> > "preferred_transport": "utp",
> > "proxy_url": "",
> > "sequential_download": false,
> > "start_paused": false,
>
> I see the inconsistency in the naming, but this is documented[1].
>
> [1]
> https://github.com/transmission/transmission/blame/main/docs/Editing-Configuration-Files.md
>
> > * The start_paused setting when set to false for either the
> underscore version of the dash
> > version has no effect.
> > * It isn't clear from the manual what this new setting does, but the
> behaviour is different from
> > the previous version. In this version, when a torrent is complete,
> it pauses.
>
> This is inconsistent with the documentation:
>
> start_paused: Boolean (default = false) Pause the torrents when daemon
> starts.
>
> start-paused (with dash) does not exist.
>
> Please clarify what needs fixing: docs? setting not working? Other?
>
> Alex
>
