Just as a reference for the Interwebz, I had this problem as well, but eventually discovered that I had a bad (relative) file path in the 'incomplete-dir' configuration key.
It is quite easy to make this happen by fiddling with the transmission-remote command line utility, and passing it bad arguments :-) In my case I used -c instead of -t to specify a particular torrent, and the damage is done:
Just as a reference for the Interwebz, I had this problem as well, but eventually discovered that I had a bad (relative) file path in the 'incomplete-dir' configuration key.
It is quite easy to make this happen by fiddling with the transmission-remote command line utility, and passing it bad arguments :-) In my case I used -c instead of -t to specify a particular torrent, and the damage is done:
Couldn't create "2": Permission denied (utils.c:610) name.here" : Permission denied (fdlimit.c:341) name.here. part": Permission denied (inout.c:122)
Couldn't create "2/torrent.
torrent.name.here tr_fdFileCheckout failed for "2/torrent.
Preumably the CWD is '/' or somewhere else that transmission can't write to, and the error message does not help identify that too much.
I'm not saying that there isn't a real bug for the people up here, I'm just telling you what happened to me and how it just might be PEBCAK :-)