Was still having issues, manually added torrents (to the "torrents" config dir) could not be removed via the remote interface. They dissappeared from the list, but reappeared after application restart. Had the same behavior with the latest 3.0 from git.
Gave up and started with a fresh, empty ...
Search found 3 matches
- Mon Jun 08, 2020 8:38 am
- Forum: Support
- Topic: All torrents "Queued for verification" after restarting transmission-daemon
- Replies: 2
- Views: 3743
- Sat Jun 06, 2020 5:22 pm
- Forum: Support
- Topic: All torrents "Queued for verification" after restarting transmission-daemon
- Replies: 2
- Views: 3743
Re: All torrents "Queued for verification" after restarting transmission-daemon
Think I solved it: "group" and "other" had read access for the torrents I added back to the "torrents" config dir. Removed these permissions and it seems fixed now.
- Fri Jun 05, 2020 9:54 pm
- Forum: Support
- Topic: All torrents "Queued for verification" after restarting transmission-daemon
- Replies: 2
- Views: 3743
All torrents "Queued for verification" after restarting transmission-daemon
Hello,
OS: Ubuntu 20.04
Transmission-daemon 2.94 as a systemd service
I migrated my download and config directories from one machine to another, also upgrading transmission to a more recent version (2.94), and made sure the user under which the daemon runs has read/write access to the config and ...
OS: Ubuntu 20.04
Transmission-daemon 2.94 as a systemd service
I migrated my download and config directories from one machine to another, also upgrading transmission to a more recent version (2.94), and made sure the user under which the daemon runs has read/write access to the config and ...