transmission-daemon doesn't consider settings.json
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| Transmission |
Fix Released
|
Unknown
|
||
| transmission (Ubuntu) |
Undecided
|
Unassigned |
Bug Description
Binary package hint: transmission-cli
Hi,
I've installed transmission-daemon on my machine in order to control it from remote.
Everything works well but the fact that the settings.json configuration file is not obeyed.
As a startup script, since it is missing from the ubuntu package, I've used the suggested one (http://
In my TRANSMISSION_HOME I've put the settings.json file, which has the following content:
{
"rpc-enabled": 1,
"upload-
"upload-limit": 20,
"peer-port" : 9091,
"rpc-
}
What happens is that the upload rate limit is not obeyed. In particular, Transmission seems to not read the file at all, since in the GUI I see the unlimited setting. When I limit the upload rate using the GUI, it works correctly.
ste@ste-ubuntu:~$ lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10
transmission-cli:
Installed: 1.34-0ubuntu2.2
Candidate: 1.34-0ubuntu2.2
Version table:
*** 1.34-0ubuntu2.2 0
500 http://
100 /var/lib/
1.34-0ubuntu2 0
500 http://
Thanks guys!
Related branches
f3a97 (f3a97) wrote : | #1 |
Charles Kerr (charlesk) wrote : | #2 |
What's happening here is the JSON is malformed (the trailing comma before the "}" isn't allowed), so Transmission is failing to parse the config file, and is falling back on the default values. This is fine, but it should at least tell you what's going on. And error message to this effect has been added for 1.51.
Changed in transmission: | |
status: | Unknown → Fix Released |
Changed in transmission: | |
status: | New → Fix Released |
status: | Fix Released → Fix Committed |
Launchpad Janitor (janitor) wrote : | #3 |
This bug was fixed in the package transmission - 1.51-0ubuntu1
---------------
transmission (1.51-0ubuntu1) jaunty; urgency=low
* New upstream bug fix release (LP: #335404)
- Fixes transmission-daemon doesn't consider settings.json (LP: #322449)
* Removed 01_check_
-- Ken VanDine <email address hidden> Fri, 27 Feb 2009 10:51:53 -0500
Changed in transmission: | |
status: | Fix Committed → Fix Released |
One more note, just to be precise.
The file is actually read, since the authentication settings work correctly (rpc-whitelist).