Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt for Python
  4. FatalError: `Process abort signal` is detected by the operating system.
Forum Updated to NodeBB v4.3 + New Features

FatalError: `Process abort signal` is detected by the operating system.

Scheduled Pinned Locked Moved Unsolved Qt for Python
3 Posts 3 Posters 875 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T Offline
    T Offline
    Tonyy
    wrote on last edited by
    #1

    Hi everyone:

    I encountered a problem that caused my PyQt5 program to fail to execute
    The error message is as follows:

    Got keys from plugin meta data ("xcb")
    QFactoryLoader::QFactoryLoader() checking directory path "/home/yuying/anaconda3/envs/Qt_test/bin/platforms" ...
    loaded library "/home/yuying/anaconda3/envs/Qt_test/lib/python3.9/site-packages/cv2/qt/plugins/platforms/libqxcb.so"
    QObject::moveToThread: Current thread (0x5618ebdf8430) is not the object's thread (0x5618f44d5730).
    Cannot move to target thread (0x5618ebdf8430)

    qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "/home/yuying/anaconda3/envs/Qt_test/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, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, 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 1707292496 (unix time) try "date -d @1707292496" if you are using GNU date ***]
    [SignalInfo: *** SIGABRT (@0x3e800059abf) received by PID 367295 (TID 0x7f758910a740) from PID 367295 ***]

    jsulmJ 1 Reply Last reply
    0
    • F Offline
      F Offline
      friedemannkleint
      wrote on last edited by friedemannkleint
      #2

      It could be something like https://bugreports.qt.io/browse/QTBUG-112185 (Qt 6), or some other incompatibility of PyQt5 on that distribution. I would recommend updating to PySide6/PyQt6 first thing, Qt 5 is quite old.

      To diagnose, run

      ldd /home/yuying/anaconda3/envs/Qt_test/lib/python3.9/site-packages/cv2/qt/plugins/platforms/libqxcb.so

      and check for missing dependencies.

      1 Reply Last reply
      1
      • T Tonyy

        Hi everyone:

        I encountered a problem that caused my PyQt5 program to fail to execute
        The error message is as follows:

        Got keys from plugin meta data ("xcb")
        QFactoryLoader::QFactoryLoader() checking directory path "/home/yuying/anaconda3/envs/Qt_test/bin/platforms" ...
        loaded library "/home/yuying/anaconda3/envs/Qt_test/lib/python3.9/site-packages/cv2/qt/plugins/platforms/libqxcb.so"
        QObject::moveToThread: Current thread (0x5618ebdf8430) is not the object's thread (0x5618f44d5730).
        Cannot move to target thread (0x5618ebdf8430)

        qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "/home/yuying/anaconda3/envs/Qt_test/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, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, 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 1707292496 (unix time) try "date -d @1707292496" if you are using GNU date ***]
        [SignalInfo: *** SIGABRT (@0x3e800059abf) received by PID 367295 (TID 0x7f758910a740) from PID 367295 ***]

        jsulmJ Offline
        jsulmJ Offline
        jsulm
        Lifetime Qt Champion
        wrote on last edited by
        #3

        @Tonyy See https://doc.qt.io/qt-6/debug.html how to debug plug-in issues (hint: set QT_DEBUG_PLUGINS before running your app and check its output).

        https://forum.qt.io/topic/113070/qt-code-of-conduct

        1 Reply Last reply
        2

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved