Description of problem: Since upgrade from 2.92-10 to 2.92-11 I cannot connect to the web-gui, nor kan transmission-remote connect to transmission from another computer then localhost. This seems to have to do with how things are written to settings.json. After the update the following vars are always dupes in settings.json except the "withheld" passwords that are always new randomly generated. "rpc-password": "<withheld>", "rpc-password": "<withheld>", "rpc-port": 9091, "rpc-port": 9091, "rpc-url": "/transmission/", "rpc-url": "/transmission/", "rpc-username": "", "rpc-username": "", "rpc-whitelist": "127.0.0.1", "rpc-whitelist": "127.0.0.1", "rpc-whitelist-enabled": true, "rpc-whitelist-enabled": true, If I remove the dupes or change ny of the lines, new dupes are either created, or the lines are over-written. Version-Release number of selected component (if applicable): transmission-2.92-11.fc27 How reproducible: Always How to reproduce: 1. install transmission-2.92-11.fc27 2. edit the whitelist or disable whitelist in settings.json 3. start the daemon 4. try to access the daemon over network 5. verify how the whitelist looks Actual results: my conf (in Expected results) are overwritten on daemon restart with following: "rpc-password": "<withheld>", "rpc-password": "<withheld>", "rpc-port": 9091, "rpc-port": 9091, "rpc-url": "/transmission/", "rpc-url": "/transmission/", "rpc-username": "", "rpc-username": "", "rpc-whitelist": "127.0.0.1", "rpc-whitelist": "127.0.0.1", "rpc-whitelist-enabled": true, "rpc-whitelist-enabled": true, Expected results: "rpc-password": "<withheld>", "rpc-port": 9091, "rpc-url": "/transmission/", "rpc-username": "", "rpc-whitelist": "127.0.0.1,10.88.*.*", "rpc-whitelist-enabled": true, Additional info: Even when I get the rpc-whitelist-enabled to say false, I still get 403 from the daemon, with comments in the web-ui about blocked by missing IP in whitelist.
(In reply to Peter Hjalmarsson from comment #0) Confirmed, as reported here : https://github.com/transmission/transmission/issues/473#event-1430874514 As Mikedld (github transmission maintainer) stated, looks like an earlier version of a patch (which had wrong order of quarks) was applied to this update.
Created attachment 1383775 [details] Patch adapter for 2.92, fetched from the PR Cannot really see if the used patch is an older version or a try to make an own adaption of the upstream patch that did not get so well. However this is the patch posted by lfam in the PR as an adaption to 2.92. Rebuilded with this patch instead, works fine.
Yes, I got the same duplicated lines in setting.json file on my production platform, Fedora 27. Package version is 2.92-11.fc27
CCing pbrobinson as he made the breaking commit.
*** Bug 1536869 has been marked as a duplicate of this bug. ***
*** Bug 1536750 has been marked as a duplicate of this bug. ***
As the transmission testcases had fetched this, please add the following to the spec-file as well. I can verify that the current patch fails at "quark-test", however the patch i posted passes all tests. --- transmission.spec.old 2018-01-22 19:51:34.248092816 +0100 +++ transmission.spec 2018-01-22 19:52:20.430198408 +0100 @@ -121,6 +121,9 @@ make %{?_smp_mflags} popd +%check +make %{?_smp_mflags} check + %install mkdir -p %{buildroot}%{_unitdir} install -m0644 daemon/transmission-daemon.service %{buildroot}%{_unitdir}/
Thank you, update coming.
transmission-2.92-12.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-b166805347
transmission-2.92-12.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-499a02cc9d
transmission-2.92-12.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-c0d5d190b0
transmission-2.92-12.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-c0d5d190b0
transmission-2.92-12.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-b166805347
transmission-2.92-12.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-499a02cc9d
(In reply to Fedora Update System from comment #14) > transmission-2.92-12.fc27 has been pushed to the Fedora 27 testing > repository. If problems still persist, please make note of it in this bug > report. > See https://fedoraproject.org/wiki/QA:Updates_Testing for > instructions on how to install test updates. > You can provide feedback for this update here: > https://bodhi.fedoraproject.org/updates/FEDORA-2018-499a02cc9d Upgraded to 2.92-12.fc27 from testing repo using dnf and the settings.json file is OK, no duplicate lines.
transmission-2.92-12.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
transmission-2.92-12.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.
transmission-2.92-12.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.