Activity log for bug #1805559

Date Who What changed Old value New value Message
2018-11-28 04:13:13 Be bug added bug
2018-11-28 04:13:13 Be attachment added backtrace.txt https://bugs.launchpad.net/bugs/1805559/+attachment/5216897/+files/backtrace.txt
2018-11-28 04:58:11 Be mixxx: importance Undecided Critical
2018-11-28 04:58:14 Be mixxx: milestone 2.2.0
2018-11-28 16:42:12 Be mixxx: status New In Progress
2018-11-28 16:42:14 Be mixxx: assignee Be (be.ing)
2018-12-16 04:25:47 Be mixxx: status In Progress Fix Committed
2018-12-16 04:29:19 Be bug watch added https://bugs.freedesktop.org/show_bug.cgi?id=59361
2018-12-16 04:29:19 Be attachment added testCase.c https://bugs.launchpad.net/mixxx/+bug/1805559/+attachment/5222640/+files/testCase.c
2018-12-25 06:14:29 Daniel Schürmann mixxx: status Fix Committed Fix Released
2019-03-29 14:18:39 Daniel Schürmann tags qt5
2019-06-02 19:22:35 Daniel Schürmann bug task added mixxx (Ubuntu)
2019-06-02 19:38:59 Daniel Schürmann description I encountered this numerous times tonight using 2.2 with RGB (GL) waveforms on XWayland with Qt 5.11.1-9.fc29.x86_64, libX11 1.6.7-1.fc29.x86_64, libxcb 1.13.1-1.fc29.x86_64. I haven't figured out what triggers it. IMO this is a release blocker for 2.2.0. [Impact] Current Mixxx 2.2.0 beta and Mixxx 2.1.3 using 2.2 with RGB (GL) waveforms on XWayland with Qt 5.11.1-9.fc29.x86_64, libX11 1.6.7-1.fc29.x86_64, libxcb 1.13.1-1.fc29.x86_64 causes a GUI deadlock. The issue can be isolated and fixed with the code posted in comment #11 below. It is not reliable reproducible with the original Mixxx build. [Test Case] * Use Mixxx with the effected setup and verify that there is no GUI deadlock. [Regression Potential] None. [Other Info] The Cosmic 2.1.3 build is also effected, see: https://bugs.launchpad.net/ubuntu/+source/mixxx/+bug/1804513
2022-10-08 21:06:56 Swiftb0y bug watch added https://github.com/mixxxdj/mixxx/issues/9533
2022-10-08 21:06:57 Swiftb0y lock status Unlocked Comment-only