Transmission does not keep its configuration after restart

yweb · 2013-04-26 11:42:31

Hi everyone,

I have a problem coming up with gnome's last upgrade.

Since Gnome 3.8 then, transmission 2.77 will not keep its configuration. I've already tried to erase the ~/.config/transmission folder in order to start transmission with a "clean" configuration but its not working.

Does anyone have the same problem ? And more importantly, does anyone have a solution yet ?

Thanks

drcouzelis · 2013-04-26 13:23:49

Please see: https://bbs.archlinux.org/viewtopic.php?id=162145

There are other threads, too, but one of them has a strange title that I don't rememeber...

Last edited by drcouzelis (2013-04-26 13:24:29)

yweb · 2013-04-26 17:14:11

thanks drcouzelis

I read the post https://bbs.archlinux.org/viewtopic.php?id=162145

I don't want to use transmission-qt !

I think we need to stay tuned and patient until there is an upstream solution.

nathan0n5ire · 2013-04-26 18:28:15

The problem is with the value in file/folder choosers in the settings dialog. If you don't edit each one of them (even the grey'd out ones), each time you open the settings window, then they will have wierd values that contain random characters, which will cause troubles when transmission wants to parse its settings.json file

WorMzy · 2013-04-26 18:30:40

yweb wrote:

I don't want to use transmission-qt !

How about transmission-gtk2?

jrussell · 2013-04-26 18:48:00

If you change transmission settings in the config file with transmission running, the settings will get overridden when transmission shuts down.
To change settings from the config file, first stop transmission, then edit settings file, then restart transmission.

drcouzelis · 2013-04-26 19:35:23

WorMzy wrote:

How about transmission-gtk2?

I used this "solution" for a few months. Unfortunately it's a few versions old (GTK2 is no longer supported by the Transmission developers) and it started behaving a little wonky, so I've been trying other solutions. Right now I bounce back and forth between transmission-gtk and transmission-qt, which is super easy to do thanks to how "modular" the Transmission user interface is.

I really don't think the API for GTK2 and GTK3 are that different, and I've been toying with the idea of patching Transmission to use GTK2... But I think I already have enough programming projects that aren't getting done.

WorMzy · 2013-04-26 20:07:42

Ah, didn't know that. I've been using a combination of transmission-daemon + transmission-remote-gui (which is gtk2) and transmission-remote-cli (in extra). It works for me.

yweb · 2013-04-26 20:48:43

jrussell wrote:

If you change transmission settings in the config file with transmission running, the settings will get overridden when transmission shuts down.
To change settings from the config file, first stop transmission, then edit settings file, then restart transmission.

Thanks I'll try...

siriusb · 2013-05-17 13:09:30

Any luck with editing the settings file? I'd like to use transmission, too. I had to abandon rtorrent.

yweb · 2013-05-17 14:54:56

I stopped trying to edit configuration and I started to use deluge instead of transmission.

I tested many approaches in order that transmission keeps its configuration and none of them is working.

Transmission do not keeps the configuration after restart and I had also problems with accents in letter for download path. I could simply not determine a download path with accentuated letters

Deluge is GTK made and provide almost the same features like encryption, blocklist and so and I have no problem with its configuration under gnome 3.8.

siriusb · 2013-05-17 15:00:46

Thanks for the feedback.

hellknight · 2013-06-03 20:08:41

I also had the same problem. The solution is quite simple actually, the settings file had an incorrect value for "incomplete-dir" (wrong encoding or something like that). I just had to update that value and voila, everything works fine.

chord · 2013-06-03 21:21:34

Common solution for configs rewriting prevent :

 chattr +i <your-config-file-name>

It blocks any changes on locked file.
If you need to rewrite/edit file, just unlock it with chattr -i, write changes and lock it again.

jrussell · 2013-06-03 22:08:05

chord wrote:

Common solution for configs rewriting prevent :
 chattr +i <your-config-file-name> 
It blocks any changes on locked file.
If you need to rewrite/edit file, just unlock it with chattr -i, write changes and lock it again.

I don't think that's a good idea, there is probably a valid reason a config file is being overwritten, your solution would disable the actual application from changing its own config file...

I had a similar problem with the transmission daemon,
Basically this is what I have deducted:

Start transmission
It reads config file
Stop transmission
It re-writes the config file with what it first read when it started plus applying changes you may have made via a GUI.

Basically as I said earlier, if you edit transmissions config file while it is running with vim or nano or whatever, those changes will be over written when transmission stops.

The solution is to either change settings from the GUI, or make sure there is no transmission running, then edit the config file and save it. Everything should then work so long as you haven't made a syntax error when editing the config file.

Last edited by jrussell (2013-06-03 22:15:35)

psychedelicious · 2013-06-03 22:55:55

hellknight wrote:

I also had the same problem. The solution is quite simple actually, the settings file had an incorrect value for "incomplete-dir" (wrong encoding or something like that). I just had to update that value and voila, everything works fine.

I had wrong encodings too. I fixed this but Transmission still doesn't save settings.

psychedelicious · 2013-06-03 23:08:38

When I do file -bi on setting.json I get this:

application/octet-stream; charset=binary

When I do it on my Fedora installation running 2.77 as well I get this:

text/plain; charset=us-ascii

siriusb · 2013-06-04 14:32:38

Actually, I went through the transmission bug reports earlier and turned out that this issue is related to GTK file chooser and a commit (not directly) resolved the problem. It'll be in v2.8.

Arch Linux

#1 2013-04-26 11:42:31

Transmission does not keep its configuration after restart

#2 2013-04-26 13:23:49

Re: Transmission does not keep its configuration after restart

#3 2013-04-26 17:14:11

Re: Transmission does not keep its configuration after restart

#4 2013-04-26 18:28:15

Re: Transmission does not keep its configuration after restart

#5 2013-04-26 18:30:40

Re: Transmission does not keep its configuration after restart

#6 2013-04-26 18:48:00

Re: Transmission does not keep its configuration after restart

#7 2013-04-26 19:35:23

Re: Transmission does not keep its configuration after restart

#8 2013-04-26 20:07:42

Re: Transmission does not keep its configuration after restart

#9 2013-04-26 20:48:43

Re: Transmission does not keep its configuration after restart

#10 2013-05-17 13:09:30

Re: Transmission does not keep its configuration after restart

#11 2013-05-17 14:54:56

Re: Transmission does not keep its configuration after restart

#12 2013-05-17 15:00:46

Re: Transmission does not keep its configuration after restart

#13 2013-06-03 20:08:41

Re: Transmission does not keep its configuration after restart

#14 2013-06-03 21:21:34

Re: Transmission does not keep its configuration after restart

#15 2013-06-03 22:08:05

Re: Transmission does not keep its configuration after restart

#16 2013-06-03 22:55:55

Re: Transmission does not keep its configuration after restart

#17 2013-06-03 23:08:38

Re: Transmission does not keep its configuration after restart

#18 2013-06-04 14:32:38

Re: Transmission does not keep its configuration after restart

Board footer