Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't connect to 3.0.0 daemon on Arch Linux #1325

Open
quexten opened this issue Jul 6, 2020 · 20 comments
Open

Can't connect to 3.0.0 daemon on Arch Linux #1325

quexten opened this issue Jul 6, 2020 · 20 comments

Comments

@quexten
Copy link

quexten commented Jul 6, 2020

  1. Operating system
    Arch Linux
  2. Transmission Daemon
    3.0.0
  3. Transmission Remote GUI
    5.18.0

When I try to connect to a 3.0.0 daemon using transgui 5.18.0 on Linux, I get the error message Duplicate object member: "status". Connecting to a 2.94 daemon works. The same happens when building transgui from source.
On Windows, also using transgui 5.18.0, I can connect to both transmission daemons without any error.

@quexten
Copy link
Author

quexten commented Jul 14, 2020

The official build 5.18.0 from the releases doesn't work on Arch since it is using GTK2 as mentioned in another issue. Building on Ubuntu with for QT5 and using that build on Arch seems to not have the issue. So I'm guessing the error lies somewhere in the dependencies (newer version of FPC?). I can't investigate this much further as I'm not familiar with Pascal.

@quexten quexten changed the title Can't connect to 3.0.0 daemon on Linux Can't connect to 3.0.0 daemon on Arch Linux Jul 14, 2020
@Ku33ma
Copy link

Ku33ma commented Jul 15, 2020

I confirm on Fedora 32.
Builds with gtk2, qt4 and qt5. FPC 3.2.0 [2020/06/21] for x86_64, lazarus-ide 2.0.10

For myself, I decided this edit:
`--- rpc.pas 2020-07-15 21:42:31.810023656 +0300
+++ rpc.pas.new 2020-07-15 21:40:45.556666807 +0300
@@ -394,6 +394,12 @@ begin
sl.Delete(i);
end;

+ if FRpc.RPCVersion > 15 then begin
+ i:=sl.IndexOf('status');
+ if i > 0 then sl.Delete(i);
+ end;
+
+
i:=sl.IndexOf('downloadDir');
if FRpc.RequestFullInfo then begin
if i < 0 then`

Sorry, used Google Translate

@briney83
Copy link

the same on Manjaro 20.0.3 with GDE and transgui-gtk from AUR

@quexten
Copy link
Author

quexten commented Jul 22, 2020

@Ku33ma does that edit have any other side effects? Otherwise I suggest making this into a pull request as this fixes transgui for multiple distros.

@Ku33ma
Copy link

Ku33ma commented Jul 22, 2020

I did not notice any side effects.

Transgui did enter the "status" field twice. One is a direct parameter of FRpc.RequestInfo, the second is taken from ExtraFields.
Transmission 2.94 returned a response with one field, and 3.0 responded with two "status" fields.

@jpmvferreira
Copy link

Same thing running transmission-remote-gui from the AUR

@jpegxguy
Copy link

jpegxguy commented Aug 5, 2020

For those of you on arch, use makepkg with --nobuild, apply the patch in #1329, and then use --noextract

@jpmvferreira
Copy link

jpmvferreira commented Aug 7, 2020

I've tried to apply the patch following your rules and the Archwiki, but i've came across an error (I'm using Manjaro):

An unhandled exception occurred at $0000000000521072:
EAccessViolation: Access violation
  $0000000000521072
  $00000000009ED7E8
  $00000000009F1804
  $00000000009F2A5E

==> ERROR: A failure occurred in package_transgui-gtk().
    Aborting...
                 

Here's all that i did:

$ git clone https://aur.archlinux.org/transgui.git
$ cd transgui
$ makepkg -s --nobuild
# Insert https://patch-diff.githubusercontent.com/raw/transmission-remote-gui/transgui/pull/1329.patch into deduplicate.patch
# Add deduplicate.patch to source in PKGBUILD
$ makepkg -g >> PKGBUILD
# Added patch --strip=1 --input=deduplicate.patch to PKGBUILD in prepare() function
$ makepkg --noextract --install

This error as also been reported in the AUR, but i had installed the package without applying the patch and it worked as expected.

One thing that's missing, is the fact that in the AUR all conflicting packages (such as transgui-gtk and transgui-qt) have the same git clone url, so how do i know which one i'm installing on my system using this process?

@jpegxguy
Copy link

jpegxguy commented Aug 7, 2020

The transgui PKGBUILD creates both the qt and the gtk version, so --install will fail because they conflict with each other. Once you have built the packages, install your prefered version manually with pacman -U

As for the error, I've never seen it. Maybe lazbuild is having problems. Does it happen if you try again with a clean slate? Also you can --skipchecksums in makepkg and skip the makepkg -g >> PKGBUILD step.

@jpmvferreira
Copy link

Thanks for the info, that makes sense. Here's what i did now line by line:

$ git clone https://aur.archlinux.org/transgui.git
$ cd transgui
$ makepkg -s --nobuild
$ wget https://patch-diff.githubusercontent.com/raw/transmission-remote-gui/transgui/pull/1329.patch
# added "1329.patch" to the end of source
# added patch --forward --strip=1 --input="${srcdir}/1329.patch" to the end of the prepare() function
$ makepkg --noextract --skipchecksums

However transgui-gtk returns a build error:

(1008) 1887 lines compiled, 0.3 sec
(1022) 4 hint(s) issued
(1023) 19 note(s) issued
An unhandled exception occurred at $0000000000000000:
EAccessViolation: Access violation
  $0000000000000000
  $00000000009F1804
  $00000000009F2A5E

==> ERROR: A failure occurred in package_transgui-gtk().
    Aborting...

However transgui-qt finishes building, running sudo pacman -U transgui-qt-5.18.0-1-x86_64.pkg.tar.xz still returns after starting the program:

Duplicate object member: "status"

Interestingly, I've literally just deleted the transgui-qt package and ran $ makepkg --noextract --skipchecksums and this time transgui-gtk actually finished building... I don't know what's going on, but both of them still return the same error.

System:
Distro: Manjaro x86_64
Kernel: 4.19.133
DE/WM: i3

@jpegxguy
Copy link

jpegxguy commented Aug 7, 2020

I traced my steps and the gtk build fails in the way you described if you use the git clone command, though I don't know why.
I used yay -G transgui-gtk (or transgui by itself) and then it works.

Here's what I did if you want to do it this way (I didn't want to leave the patching to makepkg because I wanted to see if it failed. The fact that you get the "duplicate object member: status" suggests the patching failed, or maybe it was because of the build error)

yay -G transgui-gtk
cd transgui
makepkg -s --nobuild
wget https://patch-diff.githubusercontent.com/raw/transmission-remote-gui/transgui/pull/1329.patch
cd src/transgui-5.18.0
patch -p1 -i ../../1329.patch
cd ../..
makepkg --noextract
sudo pacman -U <the package you want> 

NOTE: You'll get this output if the patch succeeds:

patching file rpc.pas
Hunk #1 succeeded at 805 (offset -11 lines).

@jpmvferreira
Copy link

Yes that worked, thanks again for the help, didn't had to patch anything before so i wasn't quite sure how to do so. If somebody wants to install this package on an arch based distro at least for me it worked. Should i reference this issue on the AUR page?

@jpegxguy
Copy link

jpegxguy commented Aug 7, 2020

I guess it would be good for the aur maintainer to include the patch in prepare() until it gets merged. This project has not seen commits since May

@jpegxguy
Copy link

jpegxguy commented Aug 7, 2020

Keep in mind that there are multiple packages for this repo. There's transgui and transmission-remote-gui
https://aur.archlinux.org/packages/?K=transgui+OR+transmission-remote-gui

@jpmvferreira
Copy link

According to a user in the transmission-remote-gui the issue applies to all packages, they all have the same version and source so honestly i don't even know what's the diference in between them.

@jpegxguy
Copy link

jpegxguy commented Aug 8, 2020

No difference other than the name

@bluenlive
Copy link
Contributor

Same issue with Synology + Windows 10(x64)

Operating system
Synology DSM
Transmission Daemon
3.00-18
Transmission Remote GUI
5.18.0

Attached images are from Korean-translated GUI.

dupl

dupl2

Before that, connecting to a 2.94 daemon worked perfectly.

@bluenlive
Copy link
Contributor

bluenlive commented Aug 18, 2020

I confirm on Fedora 32.
Builds with gtk2, qt4 and qt5. FPC 3.2.0 [2020/06/21] for x86_64, lazarus-ide 2.0.10

For myself, I decided this edit:
`--- rpc.pas 2020-07-15 21:42:31.810023656 +0300
+++ rpc.pas.new 2020-07-15 21:40:45.556666807 +0300
@@ -394,6 +394,12 @@ begin
sl.Delete(i);
end;

  • if FRpc.RPCVersion > 15 then begin
  • i:=sl.IndexOf('status');
  • if i > 0 then sl.Delete(i);
  • end;

i:=sl.IndexOf('downloadDir');
if FRpc.RequestFullInfo then begin
if i < 0 then`

Sorry, used Google Translate

@Ku33ma This patch works very well with my environment.
Thanks a lot!

Operating system
Synology DSM
Transmission Daemon
3.00-18
Transmission Remote GUI
5.18.0

uqs pushed a commit to freebsd/freebsd-ports that referenced this issue Dec 29, 2020
…e daemon)

PR:		251839
Reported by:	vgreg  at  ya.ru
Obtained from:	transmission-remote-gui/transgui#1325


git-svn-id: svn+ssh://svn.freebsd.org/ports/head@559535 35697150-7ecd-e111-bb59-0022644237b5
uqs pushed a commit to freebsd/freebsd-ports that referenced this issue Dec 29, 2020
Jehops pushed a commit to Jehops/freebsd-ports-legacy that referenced this issue Dec 29, 2020
…e daemon)

PR:		251839
Reported by:	vgreg  at  ya.ru
Obtained from:	transmission-remote-gui/transgui#1325


git-svn-id: svn+ssh://svn.freebsd.org/ports/head@559535 35697150-7ecd-e111-bb59-0022644237b5
vt-alt pushed a commit to altlinux/specs that referenced this issue Mar 25, 2021
- fix error 'Duplicate object member: "status"'
  transmission-remote-gui/transgui#1325
Diesel1017 added a commit to Diesel1017/transgui that referenced this issue Mar 14, 2022
Fix: Duplicate object member: "status"

Thanks for the patch:
transmission-remote-gui#1325
@PeterDaveHello
Copy link
Member

#1329 was merged, please feel free to test it!

@atommaki
Copy link

atommaki commented Dec 23, 2022

I am on Ubuntu 22.04, I used transgui from the Ubuntu repo (5.18.0+dfsg-1build1) and I had the same issue. After compiling latest from the git repo the issue is gone. I hope there will be soon a release and I can use again a released version.

svmhdvn pushed a commit to svmhdvn/freebsd-ports that referenced this issue Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

8 participants