-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Changing between Light and Dark themes in GNOME causes Mixxx to hang #11464
Comments
Which version of Mixxx is affected? Are other skins affected as well? |
Can you run Mixxx under GDB, brake via Ctrl+C in the console and create a backtrace? |
I'm using 2.3.4; LateNite PaleMoon skin. About the two icons... it might just be a bug. For some reason, I thought it was GNOME's fault, or the extension. Should I start a separate bug report for that? |
Confirmed. Fans are spinning up. Maybe an endless loop in Qt 5 code? Unlikely, that this gets fixed (soon). I have interrupted Mixxx in the debugger and get the following stack trace.
|
Another one for comparison, slightly different:
|
100% CPU, likely caused by the main UI thread getting caught in an endless loop. |
Both backtracks contain:
There is not much Mixxx code in the stack ... Now we need to find out at which level the repetition cycles. Please do the following:
|
Btw: I cannot reproduce it on Ubuntu Focal using the Gnome based Ubuntu desktop. |
I can reproduce this crash on Arch, Gnome 47.1, Wayland & Mixxx 2.4.1 installed from Flathub. What crashes:
When changing the system theme, console output is
If you remove the Wayland permission in Flatseal with |
Does mixxx.log contain something suspicious? Maybe you can create a backtrace using gdb? This issue contains some hints how to use gdb with flatpack: #13720 |
The complete mixxx.log file: https://pastebin.com/raw/EzkYeW5v Now trying to debug with gdb according to #11464 (comment): https://pastebin.com/raw/etDsLU7A As far as I can see, the breakpoint was not reached. So this is where the step "crawl up the stack and find the first point where a breakpoint is reached" should come into play, but I'm missing the technical knowledge to proceed. Now the backtrace after crashing according to #13720 (comment): https://pastebin.com/raw/11Uec1dj |
Computer specs:
Fedora 37 / Gnome 43
EDIT: Mixxx 2.3.4
In GNOME 43, if you have Mixxx up and running, and decide to change your "Appearance" theme from Dark or Light (and vice versa), Mixxx hangs and has to be "forced quit" to close and reopen the program again.
I did a quick desktop recording to show this.
In the first 10 seconds, you'll see that Mixxx is working perfectly fine. By 00:15, I decide to change the Appearance theme from Default to Dark. Mixxx then starts to hang as it fails to respond. (I forgot to "show my cursor" as I recorded the desktop, but I'm clicking "wait" in hopes that Mixxx will respond to the crash, and to avoid "quitting' if possible).
Force quitting is the only way to get out.
Screencast.from.2023-04-10.12-12-47.webm
The text was updated successfully, but these errors were encountered: