FS#68634 - [agordejo] python error

Attached to Project: Community Packages
Opened by Waldo122 (user824303582) - Sunday, 15 November 2020, 17:38 GMT
Last edited by David Runge (dvzrv) - Friday, 15 January 2021, 17:49 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To David Runge (dvzrv)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
When trying to start agordejo, this is the error I get.

Here's the complete log.
[code]
[nsmd] ../src/nsmd.cpp:2439 main(): Using OSC port 42867
[nsmd] ../src/nsmd.cpp:2494 main(): Session root is: ~/NSM Sessions
[nsmd] ../src/Endpoint.cpp:205 init(): Creating OSC server
NSM_URL=osc.udp://localhost:42867/
[nsmd] ../src/nsmd.cpp:2286 announce_gui(): A GUI announced to us from the URL osc.udp://127.0.0.1:43942/
[nsmd] ../src/nsmd.cpp:2309 announce_gui(): Informing GUI that no session is running by sending two empty strings
[nsmd] ../src/nsmd.cpp:2338 announce_gui(): Registration with GUI complete

[nsmd] ../src/nsmd.cpp:1712 osc_list(): Listing sessions
[nsmd] ../src/nsmd.cpp:1712 osc_list(): Listing sessions
[nsmd] ../src/nsmd.cpp:1712 osc_list(): Listing sessions
[nsmd] ../src/nsmd.cpp:1712 osc_list(): Listing sessions
qt.qpa.xcb: QXcbConnection: XCB error: 5 (BadAtom), sequence: 596, resource id: 0, major code: 20 (GetProperty), minor code: 0
ERROR:engine.start:Caught crash in execpthook. Trying too execute atexit anyway
Traceback (most recent call last):
File "/usr/bin/qtgui/waitdialog.py", line 47, in run
File "/usr/bin/qtgui/waitdialog.py", line 66, in wrap
File "/usr/bin/engine/api.py", line 216, in buildSystemPrograms
File "/usr/bin/engine/findprograms.py", line 195, in build
File "/usr/bin/engine/findprograms.py", line 229, in _build
TypeError: 'str' object does not support item assignment
QBasicTimer::stop: Failed. Possibly trying to stop from a different thread
QBasicTimer::stop: Failed. Possibly trying to stop from a different thread
QBasicTimer::stop: Failed. Possibly trying to stop from a different thread
QObject::killTimer: Timers cannot be stopped from another thread
QObject::~QObject: Timers cannot be stopped from another thread
QObject::killTimer: Timers cannot be stopped from another thread
QObject::~QObject: Timers cannot be stopped from another thread

(process:59041): GLib-CRITICAL **: 20:52:04.113: g_main_context_pop_thread_default: assertion 'g_queue_peek_head (stack) == context' failed
QObject::killTimer: Timers cannot be stopped from another thread
QObject::~QObject: Timers cannot be stopped from another thread
Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt.
You must not let any exception whatsoever propagate through Qt code.
If that is not possible, in Qt 5 you must at least reimplement
QCoreApplication::notify() and catch all exceptions there.

QObject::~QObject: Timers cannot be stopped from another thread
[/code]

A pyqt issue probably.

Additional info:
* package version(s) : 0.1.1-1

Additional info:
I'm not sure if this is even the package's issue. The 'str' error suggested a python error. Anyways, I'll try asking in the laborejo forums if it's not an issue with the package.
This task depends upon

Closed by  David Runge (dvzrv)
Friday, 15 January 2021, 17:49 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed latest with 0.2.1-1
Comment by loqs (loqs) - Sunday, 15 November 2020, 19:48 GMT
What is the output of:
pacman -Qo /usr/bin/qtgui/waitdialog.py
Comment by Waldo122 (user824303582) - Monday, 16 November 2020, 10:35 GMT
@loqs, no package owns it. No such file.
Are you sure you meant /usr/bin and not something else?
Comment by Waldo122 (user824303582) - Monday, 16 November 2020, 12:04 GMT Comment by David Runge (dvzrv) - Thursday, 24 December 2020, 18:10 GMT
Upstream is experiencing issues because of nuitka (and its partial incompatibility with py39).
I'm afraid there's not much we can do about that at this point in time.

FWIW: I am not seeing your crash, but I see other crashes (probably related to wayland).
Comment by Waldo122 (user824303582) - Sunday, 03 January 2021, 08:01 GMT
Yes, there was a fix recently upstream and I wasn't keeping track of the bug report.

Loading...