Replies: 3 comments 1 reply
-
The only system I have that uses Wayland is my Pi4b running the latest PiOS and it works ok there. My desktop and Pi have Python 3.11.2, I haven't tried 3.13.1. The 'WL: error in client communication' must be a clue. I assume you have set your user in the correct groups? I have only seen strange thread messages when I have tried to update a GUI from inside a thread, but QtTinySA doesn't do that. Does the .bin executable work? |
Beta Was this translation helpful? Give feedback.
-
Please let me know if the latest release v1.0.2, built using Github 'runners' works ok. |
Beta Was this translation helpful? Give feedback.
-
I didn't specify the version of numpy, but I currently do use 1.x because that's what is current in Ubuntu 24.04 LTS and Anaconda (and I use the Spyder IDE for writing code). You could try creating a VENV to save changing your main versions. This is one of the reasons why I stay on the LTS version for my main machine. Does the Linux executable run ok? |
Beta Was this translation helpful? Give feedback.
-
Brandie fresh download of QtTinySA from git
$ ./QtTinySA.py
QSocketNotifier: Can only be used with threads started with QThread
Database QtTSAprefs.db found at /home/-name-/.config/QtTinySA
QtTSAprefs.db open: True
QtTinySA v0.11.8
The Wayland connection experienced a fatal error: Protocol error
System Journal shows:
Jan 10 15:25:40 Tardis.-name-.net gnome-shell[5948]: WL: error in client communication (pid 166306)
This worked just a few weeks ago - even with a slightly older version of QtTinyS.
Would appreciate guidance on how to dig further and even how to resolve.
Thanks!
Fedora 41
Python 3.13.1
python3-QtPy-2.4.1
Beta Was this translation helpful? Give feedback.
All reactions