-
Notifications
You must be signed in to change notification settings - Fork 179
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
PyQt 5.15 issue with Debian Buster 10.7 [workaround] #71
Comments
Oh that's interesting, as it actually might finally be a solution to many XCB related issues posted! Thanks! I'll forward other users who posted this issue to this one so we can verify! |
Requirements.txt changed to 5.14 |
|
I got this same error on Ubuntu 20.04 and resolved it by running |
This is the solution in debian 10.11 |
sudo ln -s /usr/lib/x86_64-linux-gnu/libxcb-util.so.0 /usr/lib/x86_64-linux-gnu/libxcb-util.so.1 solved my problem ASTRA LINUX |
Issue
Installed Tasmotizer in a virtual environment on Debian Buster 10.7 using the "Option 2" instructions:
When running Tasmotizer on Debian Buster the app fails to start - the output includes the following error:
Setting
export QT_DEBUG_PLUGINS=1
then running Tasmotizer again gives some additional information:Cause
It appears that as of PyQt5 5.15, the Qt plugin
libqxcb.so
is expecting to find the modulelibxcb-util.so.1
eg:/lib/x86_64-linux-gnu/libxcb-util.so.1
However, Debian Buster (version 10.7) only has
libxcb-util.so.0
This change was apparently made in PyQt 5.15.
Possible Solution
One possible solution might be to pin the max requirement for PyQt5 to 5.14.2 though I have not tested this (I opted to make a symbolic link called
libxcb-util.so.1
in the same folder aslibxcb-util.so.0
that pointed tolibxcb-util.so.0
, which seems to work), eg:The text was updated successfully, but these errors were encountered: