Bug#1039859: mixxx: Mixxx GUI is broken / elements not rendered

[lynthian4]

Package: mixxx
Version: 2.3.3~dfsg-2+b2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: lynt...@trash-mail.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

* What led up to the situation?
Upgrading from Debain 11 to Debian 12 caused the issue to appear.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Starting mixxx
* What was the outcome of this action?
GUI is not being rendered correctly. Some elements, like the two waveforms on top, are 'transparent' and show a glitched view of the window below the mixxx application. Since these waveforms are part of the main GUI and a visual guide for mixing track this makes the package ununsable.
* What outcome did you expect instead?
GUI being displayed normally, as it was the case in Debian 11.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 12.0
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mixxx depends on:
ii libavcodec59 7:5.1.3-1
ii libavformat59 7:5.1.3-1
ii libavutil57 7:5.1.3-1
ii libc6 2.36-9
ii libchromaprint1 1.5.1-2+b1
ii libebur128-1 1.2.6-1+b1
ii libflac12 1.4.2+ds-2
ii libgcc-s1 12.2.0-14
ii libglib2.0-0 2.74.6-2
ii libhidapi-libusb0 0.13.1-1
ii libid3tag0 0.15.1b-14
ii liblilv-0-0 0.24.14-1
ii libmad0 0.15.1b-10.1+b1
ii libmodplug1 1:0.8.9.0-3
ii libmp3lame0 3.100-6
ii libogg0 1.3.5-3
ii libopus0 1.3.1-3
ii libopusfile0 0.12-4
ii libportaudio2 19.6.0-1.2
ii libportmidi0 1:217-6.1
ii libprotobuf-lite32 3.21.12-3
ii libqt5core5a 5.15.8+dfsg-11
ii libqt5dbus5 5.15.8+dfsg-11
ii libqt5gui5 5.15.8+dfsg-11
ii libqt5keychain1 0.13.2-5
ii libqt5network5 5.15.8+dfsg-11
ii libqt5opengl5 5.15.8+dfsg-11
ii libqt5script5 5.15.8+dfsg-2
ii libqt5scripttools5 5.15.8+dfsg-2
ii libqt5sql5 5.15.8+dfsg-11
ii libqt5sql5-sqlite 5.15.8+dfsg-11
ii libqt5svg5 5.15.8-3
ii libqt5widgets5 5.15.8+dfsg-11
ii libqt5x11extras5 5.15.8-2
ii libqt5xml5 5.15.8+dfsg-11
ii librubberband2 3.1.2+dfsg0-1
ii libsndfile1 1.2.0-1
ii libsoundtouch1 2.3.2+ds1-1
ii libsqlite3-0 3.40.1-2
ii libssl3 3.0.9-1
ii libstdc++6 12.2.0-14
ii libswresample4 7:5.1.3-1
ii libtag1v5 1.13-2
ii libupower-glib3 0.99.20-2
ii libusb-1.0-0 2:1.0.26-1
ii libvorbis0a 1.3.7-1
ii libvorbisenc2 1.3.7-1
ii libvorbisfile3 1.3.7-1
ii libwavpack1 5.6.0-1
ii libx11-6 2:1.8.4-2+deb12u1
ii mixxx-data 2.3.3~dfsg-2

mixxx recommends no packages.

Versions of packages mixxx suggests:
ii evince [pdf-viewer] 43.1-2+b1

-- no debconf information

[Christian Beier]

Same here,

Running GNOME 43.4 on Wayland, OpenGL renderer string: AMD Radeon
Graphics (renoir, LLVM 15.0.6, DRM 3.49, 6.1.0-9-amd64).

Note that I can get at least the waveform display back if I switch from
"RGB (GLSL)" to "RGB". The virtual turntable elements are still
transparent and flickery.

Maybe a Qt issue?

--
Christian Beier

what is, is; what is not is possible.

[Dennis Braun]

I was not able to reproduce that so far, not on bookworm and not on sid,
anybody else?

i use GNOME on wayland, too.

[Christian Beier]

What kind of GPU are you using? Maybe it's an AMD-related thing.

Am 31. Juli 2023 14:23:07 MESZ schrieb Dennis Braun <d_b...@kabelmail.de>:

I was not able to reproduce that so far, not on bookworm and not on sid, anybody else?

i use GNOME on wayland, too.

--

[Dennis Braun]

Hm maybe, because both GPUs i use are Intel:
Xeon E3-1200 on bookworm and
HD Graphics 620 on sid.


Am 31.07.23 um 15:29 schrieb Christian Beier:

> What kind of GPU are you using? Maybe it's an AMD-related thing.
>
> Am 31. Juli 2023 14:23:07 MESZ schrieb Dennis Braun <d_b...@kabelmail.de>:
>> I was not able to reproduce that so far, not on bookworm and not on sid, anybody else?
>>
>> i use GNOME on wayland, too.
>>
>> --

>> To unsubscribe, send mail to 1039859-u...@bugs.debian.org.
>

[Matthew Ruffell]

Hi everyone,

This is a wayland related bug, and a known issue upstream:

https://bugs.launchpad.net/mixxx/+bug/1850729
https://github.com/mixxxdj/mixxx/issues/9787

It seems the waveform code is incompatible with the QtWayland platform
plugin change, which is mentioned on their troubleshooting page:
https://github.com/mixxxdj/mixxx/wiki/Troubleshooting#mixxx-on-wayland

A workaround is to launch mixxx with

$ mixxx -platform xcb

Which uses the x11 platform plugin.

Upstream actually have -platform xcb set in their desktop file by
default, and if you look at debian/patches/0002-desktop_file.patch:

diff --git a/res/linux/org.mixxx.Mixxx.desktop
b/res/linux/org.mixxx.Mixxx.desktop
index bf90e33..35f4b68 100644
--- a/res/linux/org.mixxx.Mixxx.desktop
+++ b/res/linux/org.mixxx.Mixxx.desktop
@@ -8,7 +8,8 @@ GenericName[fr]=Interface numérique pour DJ
Comment=A digital DJ interface
Comment[de]=Ein digitales DJ-System
Comment[fr]=Une interface numérique pour DJ
-Exec=sh -c "pasuspender -- mixxx -platform xcb || mixxx -platform xcb"
+Exec=mixxx
+Keywords=dj;music;alsa;jack:realtime;standalone;
Terminal=false
Icon=mixxx
Type=Application

The exec line gets changed to remove the pasuspender call and platform
plugin changes. I understand removing pasuspender, but maybe we should
restore -platform xcb.

Gnome-Shell is wayland by default, and I think other desktops are
moving the same way, so maybe we should force the x11 backend by
default to have a working application while upstream decides how to
rebuild their interface for wayland to fix the issue.

Thanks,
Matthew