transmission-remote-gui / transgui

🧲 A feature rich cross platform Transmission BitTorrent client. Faster and has more functionality than the built-in web GUI.
GNU General Public License v2.0
3.2k stars 274 forks source link

Error: Duplicate object member: "status" #1350

Open myxomatosis opened 3 years ago

myxomatosis commented 3 years ago

For bug report, please provide version info of:

  1. Operating system: 5.8.11-1-MANJARO
  2. Transmission Daemon: transmission-daemon 3.00 (bb6b5a062e)
  3. Transmission Remote GUI: 5.18.0 Build 17f71e6 FPC 3.2.0 Lazarus 2.0.10.0

When trying to connect to the daemon I get the following error:

Error: Duplicate object member: "status"

I have no issues connecting to the daemon through the web browser.

A-Petrov-atweb commented 3 years ago

under

petrov@petrov:~ % uname -a
FreeBSD petrov 12.2-RELEASE FreeBSD 12.2-RELEASE r366954 GENERIC  amd64

same here after upgrade fpc & Lazarus ports

Screens with versions of an applications ![screen](https://user-images.githubusercontent.com/75357646/100917909-d83f0d80-34e8-11eb-8fe2-48fd05af9916.png) ![screen2](https://user-images.githubusercontent.com/75357646/100917913-d8d7a400-34e8-11eb-8fd2-f2afe13340bb.png)
A-Petrov-atweb commented 3 years ago

Seems issue needs to be merged with #1325 as duplicate due to sloooow motion development

oddmean commented 2 years ago

I've caught the same error on

johnwmail commented 2 years ago

I meet it on Debian also, any idea how to fix it?

rejeanc commented 2 years ago

Same here : Debian GNU/Linux 10 (buster) transmission 3.00

emk2203 commented 2 years ago

Same error here. transgui 5.18.0, Fpc 3.2.2, Lazarus 2.0.12.0, on Ubuntu 22.04. Connecting to a Transmission 3.00 daemon.When I connect to the same Transmission 3.00 daemon on an Arch system with transgui 5.18.0, Fpc 3.2.2 and Lazarus 2.0.12.0, everything works. transgui from AUR.

Jimbolino commented 2 years ago

Same issue after upgrading client and server to ubuntu 22.04

thisisnotmyrealname commented 2 years ago

same with upgrading my desktop to 22.04, server has been on transmission 3.xx from the transmissionbt launchpad repo.

The package transgui-test provided in the snap store works.

username227 commented 2 years ago

same with upgrading my desktop to 22.04, server has been on transmission 3.xx from the transmissionbt launchpad repo.

The package transgui-test provided in the snap store works.

Does this mean that transgui will likely not work anymore after Linux Mint 21 comes out (which is based on 22.04)? Thanks for the snap store lead.

mikabytes commented 2 years ago

Bumping this thread.

Seems no activity going on to fix this? Anyone?

emk2203 commented 2 years ago

I left a comment in the launchpad bug tracker.

The bug is fixed in the upcoming Kinetic (22.10) release with version 5.18.0+dfsg-3.

Download it manually and install in Jammy (22.04) with dpkg if needed.

terxw commented 1 year ago

Even with version 5.18.0+dfsg-3 on Linux Mint 21/Ubuntu 22.04 I still got Duplicate object member: "status" error.

username227 commented 1 year ago

This did work for me on jammy (Mint 21). Not sure how, since it still says 5.18.0, but I'm grateful. Thanks!

tmortagne commented 1 year ago

Download it manually and install in Jammy (22.04) with dpkg if needed.

Works fine on Ubuntu 22.04.

xiota commented 1 year ago

Any reason this commit isn't merged with master?

IanBlakeley commented 1 year ago

Functioning with TLS1.3 seems also fixed in this patch

mikabytes commented 1 year ago

I can confirm v5.18 fixes this error. Tested on Ubuntu 22.04

Download it with the link provided by emk2203 and install it using:

sudo dpkg -i transgui_5.18.0+dfsg-3_amd64.deb
TrueOsiris commented 1 year ago

Same issue on ubuntu 22.04 desktop with apt installed transgui. Snap installed trangui-test gives those ssl issues.

Download it manually and install in Jammy (22.04) with dpkg if needed.

Works fine on Ubuntu 22.04.

not for me. Still the same error.

Limych commented 1 year ago

@TrueOsiris I had the same problem. Solution above from @mikabytes helped me.

boris-pangea commented 1 year ago

Solution from @mikabytes helped me too. Linux Mint 21.

DDriggs00 commented 1 year ago

Just a confirmation that as of April 2023, the Linux Mint repo version still has the problematic version, although manually installing the latest deb fixes the problem.

fir3-1ce commented 1 year ago

i just had this problem with the apt version but installing the dpkg fixed it

ski007 commented 5 months ago

thanks for the update :-)