You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've had this issue using it on Kali Linux/ awesomeWM
Got keys from plugin meta data ("xcb")
QFactoryLoader::QFactoryLoader() checking directory path "/home/skid/My_Code/ppocrlabel/.venv/bin/platforms" ...
loaded library "/home/skid/My_Code/ppocrlabel/.venv/lib/python3.9/site-packages/cv2/qt/plugins/platforms/libqxcb.so"
QObject::moveToThread: Current thread (0x555556003510) is not the object's thread (0x55555cf35e40).Cannot move to target thread (0x555556003510)qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "/home/skid/My_Code/ppocrlabel/.venv/lib/python3.9/site-packages/cv2/qt/plugins" even though it was found.This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.Available platform plugins are: xcb, linuxfb, minimal, offscreen, vnc, webgl.--------------------------------------C++ Traceback (most recent call last):--------------------------------------No stack trace in paddle, may be caused by external reasons.----------------------Error Message Summary:----------------------FatalError: `Process abort signal` is detected by the operating system. [TimeInfo: *** Aborted at 1731545192 (unix time) try "date -d @1731545192" if you are using GNU date ***] [SignalInfo: *** SIGABRT (@0x3e800015ac9) received by PID 88777 (TID 0x7ffff7ccc740) from PID 88777 ***]zsh: IOT instruction QT_DEBUG_PLUGINS=1 PPOCRLabel
It turned out I was able to solve it doing the following step
rm .venv/lib/python3.9/site-packages/cv2/qt/plugins/platforms/libqxcb.so
# or if in other folder
rm ~/.local/lib/python3.9/site-packages/cv2/qt/plugins/platforms/libqxcb.so
Maybe document this in readme?
The text was updated successfully, but these errors were encountered:
I've had this issue using it on Kali Linux/ awesomeWM
It turned out I was able to solve it doing the following step
Maybe document this in readme?
The text was updated successfully, but these errors were encountered: