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
joinmarket-qt.py: TypeError: 'Shiboken.ObjectType' object is not iterable #1031
Comments
Just confirmed: |
Just to note that tested on aarch64 and it works but need to use the system-side packages for PySide2 and PyQt5 as pip doesn't have those on arm: |
Is this a delta from 0.9.1, or some earlier version? |
Previously I've been using 0.8.3. So it's a jump 0.8.3 -> 0.9.2. |
Just tried 0.9.0, downloaded it, installed and run exactly same steps as in the first post, but in 0.9.0 folder. Problem can be reproduced. So maybe it's a bug in 0.9.0, not present in 0.8.3.
|
The bug is in PySide2, see here. This is a QT dependency, which explains why you encountered the bug only when trying GUI. There are two possible solutions:
|
@PulpCattel Thanks for your reply. Downgrading Debian Bullseye to Python 3.7 is not possible, that would destroy the system. I already have PySide >5.14 in Debian Bullseye. $ dpkg -l | grep pyside This pyside2, isn't is embedded in JoinMarket, as other python packages,which are being downloaded during install? It relies on my system pyside2? |
Pyside2 requiremens for JM-QT is |
You should be able to install Python 3.7 and then create a virtualenv that uses Python 3.7, though installing a new version of PySide seems surely easier.
Check the version inside the virtualenv (
I can reproduce the bug in a clean Debian Bullseye image, |
Why fail then? What should I do to not fail Qt building? |
(jmvenv) pip install PySide2==5.1x.x if you want a specific version. (jmvenv) pip install "PySide2>=5.14" |
Thanks, that worked! Any chance "PySide2>=5.14" version can be incorporated with JM? Looks like default version install.sh script have downloaded to virtualenv is bugged. As @PulpCattel has also reproduced. |
Sounds like a good idea to me, will look into that. |
If I recall correctly, one of a couple of reasons I didn't bother to build binaries for Qt for Linux (I actually used to do this, in 2016), was that disappointingly even a 'static' build ends up having dynamic dependencies that made it fail to work on some, even common, distros. The other reason was a lack of demand for it. Now there is an automated Windows build only, see #641 for how it's built with Wine. Why do I mention that here? Because it's proved a continuous pain point to get the dependencies in the Qt app not to bork in this way. Apart from #1031 there was #737 and #865 and #913 as resolution to them (and earlier #739), and #815 (which was closed but unresolved?), about macOS, and then #702 about ARM, and #687. I'll stop here :) I would ideally like an AppImage type workflow to actually work; especially if it could avoid any possibility of a dynamic dependency screwing things up (which I think AppImage should do?). Problem was, last time I checked about a year ago, I didn't find a simple packaging solution for AppImage that could work for us? The windows stuff shown above in #641 works with pyinstaller (and btw is not simple at all! but some of that is Windows). |
On Debian 11 amd64 I got:
To fix needed to edit the
Then:
|
New update, new problem. Downloaded 0.9.4 to separate folder
Try again:
|
Hi all,
I encountered reproducible error which prevents joinmarket-qt.py from running.
I use Debian 11 Bullseye on AMD64, fully updated.
My steps to reproduce:
wget https://github.com/JoinMarket-Org/joinmarket-clientserver/archive/refs/tags/v0.9.2.tar.gz
tar xzvf v0.9.2.tar.gz
cd joinmarket-clientserver-0.9.2/
./install.sh (selected YES for Qt deps)
That churned for a few minutes. Among other things, I seen in the output:
source jmvenv/bin/activate
python scripts/joinmarket-qt.py
The text was updated successfully, but these errors were encountered: