|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #61017] GUI doesn't work anymore, even though CLI works fine |
Date: | Wed, 11 Aug 2021 04:25:03 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.131 Safari/537.36 Edg/92.0.902.67 |
Follow-up Comment #25, bug #61017 (project octave): I'm not sure whether I read the backtraces correctly (I only have a very limited understanding of Qt). But it looks like you are experiencing a dead-lock while initializing the QApplication object. Thread 1 (the GUI thread afaict) seems to be waiting for some other thread. But I'm not sure for which thread it is waiting. All other threads seem to be in a waiting state, too. Maybe some Qt expert can make more out of this. Maybe this is something that has been fixed in the meantime (although Qt5.15 no longer receives any open updates from upstream unfortunately). Could you check if you see the same error with one of the nightly builds from octave.space? You can download those from here: https://buildbot.octave.space/#/download It would probably be most interesting to see if the octave-mxe-default-w64 build is working for you (once it has finished compiling). _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?61017> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |