Transmission

Run `transmission-remote -si` to get session information which will contain "Configuration directory:" line in "CONFIG" section; that's where Transmission stores all its information about your torrents and their progress, and where your configuration file (settings.json) is located. If you're using ...

The easiest is probably to use https://packages.ubuntu.com/ to find the particular package and view the list of its files, e.g. https://packages.ubuntu.com/focal/amd64/transmission-daemon/filelist. Other options could be googled as well, e.g. https://superuser.com/questions/82923/how-to-list-files-o...

To the OP, if you still have this issue consider redirecting the transmission-remote output to a file as well, e.g.

Read my comment (and maybe the whole thread) on GitHub for pointers: https://github.com/transmission/transmi ... -472212932

Transmission is using cURL library to make HTTP requests to trackers. As long as that library is built with SSL support (and potentially against an SSL library that supports a particular SSL/TLS version in use by the tracker), Transmission itself supports SSL.

Two reasons you should not rely on torrent filenames: 1. Files stored in "torrent" and "resume" subdirectories are best managed by Transmission and should not generally be touched by a human. In particular, .torrent and .resume files are stored for Transmission's internal use and could be considered...

I'd suggest starting from the top. You may not have done the cloning correctly.

The report is incomplete. It says that "crashed thread: 1" but then only includes "thread 0" which seems to operate normally. Include as much as you can, I'm not sure if the report could be that big that the forum won't allow you to paste it all. Also, please wrap it in "code" tags.

Take a look at https://github.com/transmission/transmission-release-scripts/blob/master/build-source.sh for the steps that should be enough (those are for Debian). Note that on some Linux distributions (and yours is one of those) you need to install additional packages in order to do any development...

I cannot give you the exact command, that's why the tool accepts parameters so that you pass values that are specific to your system and use-case. The examples on GitHub should be more than enough. Something you could try (and I'm not making any guarantees here): # Let BtMigrate guess the path where...

Depending on the distribution and build configuration, default path to settings.json may vary. You don't need to place the file at a specific location and wonder why it doesn't work; instead, when running the daemon pass it the -g/--config-dir option to set the directory containing the file explicit...

I'm sorry but there's no UI for this tool. You need to start a terminal emulator (try searching for "Command Prompt" or "PowerShell" in your Start menu) and then execute the commands as they are presented in the readme by the first link (there're full command examples there, just use "BtMigrate.exe"...

1. If you need a tool, consider something like https://github.com/mikedld/bt-migrate (grab pre-built binary from the latest build on Actions tab, e.g. https://github.com/mikedld/bt-migrate/actions/runs/51752466). If the number of torrents is small, another option would be to just manually add .torre...

It may depend on what you're using as `<torrentid>` there. When you're using something that's not "all", "active", real ID (like the one from the first column of `transmission-remote -l` output) or a range of IDs, or real hash, Transmission doesn't treat this as an error if it can't find the torrent...

Transmission neved had the functionality of unpacking archives built in. You're probably using a torrent completion script to achieve that, and thus need to either dig into it yourself or contact its author for assistance.