You are not logged in.
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
Offline
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)
Offline
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.
Offline
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
Offline
I don't want to use transmission-qt !
How about transmission-gtk2?
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
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.
bitcoin: 1G62YGRFkMDwhGr5T5YGovfsxLx44eZo7U
Offline
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.
Offline
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.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
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...
Offline
Any luck with editing the settings file? I'd like to use transmission, too. I had to abandon rtorrent.
Offline
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.
Offline
Thanks for the feedback.
Offline
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.
Offline
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.
Offline
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)
bitcoin: 1G62YGRFkMDwhGr5T5YGovfsxLx44eZo7U
Offline
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.
Offline
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
Offline
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.
Offline