Version 2.2.4 was tagged much earlier but then not released officially due to internal build server issues. Nothing to worry about.
The issue might depend on the exact Qt version, the build settings used by Arch, and how Mixxx is started (i.e. with "-platform xcb" on Wayland?). I have never experienced such an issue on Fedora with Qt 5.12/5.13/5.14. If you resume Mixxx after creating the backtrace and then suspend Mixxx again to create a new backtrace: Does the call stack look similiar, i.e. is it still blocking in QSemaphore::acquire(int)? Then this could be a hint for a deadlock in some Qt UI code. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789059 Title: continual GUI freeze To manage notifications about this bug go to: https://bugs.launchpad.net/mixxx/+bug/1789059/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
