Wavebox 10.113.24 is broken after Ubuntu system update

[jeka]

• Wavebox Version: 10.113.24-3 (installed package version)
• Operating System & Version: Ubuntu 22.04 (KDE neon 5.27)

Bug/Feature description

With the recent system update wavebox is broken. It does not even start properly.

from the apt history it happened after applying these updates:

Start-Date: 2023-05-24  10:18:49
Commandline: packagekit role='update-packages'
Requested-By: jekov (1000)
Upgrade: libglx-mesa0:amd64 (22.2.5-0ubuntu0.1~22.04.1, 22.2.5-0ubuntu0.1~22.04.2), libtinfo5:i386 (6.3-2, 6.3-2ubuntu0.1), libtinfo6:amd64 (6.3-2, 6.3-2ubuntu0.1), libgbm1:am
d64 (22.2.5-0ubuntu0.1~22.04.1, 22.2.5-0ubuntu0.1~22.04.2), libxatracker2:amd64 (22.2.5-0ubuntu0.1~22.04.1, 22.2.5-0ubuntu0.1~22.04.2), libegl1-mesa:amd64 (22.2.5-0ubuntu0.1~2
2.04.1, 22.2.5-0ubuntu0.1~22.04.2), mesa-va-drivers:amd64 (22.2.5-0ubuntu0.1~22.04.1, 22.2.5-0ubuntu0.1~22.04.2), libgl1-mesa-dri:amd64 (22.2.5-0ubuntu0.1~22.04.1, 22.2.5-0ubu
ntu0.1~22.04.2), libgl1-mesa-glx:amd64 (22.2.5-0ubuntu0.1~22.04.1, 22.2.5-0ubuntu0.1~22.04.2), firefox:amd64 (113.0.1+build1-0ubuntu0.22.04.1~mt1, 113.0.2+build1-0ubuntu0.22.0
4.1~mt1), mesa-vulkan-drivers:amd64 (22.2.5-0ubuntu0.1~22.04.1, 22.2.5-0ubuntu0.1~22.04.2), ncurses-base:amd64 (6.3-2, 6.3-2ubuntu0.1), libglapi-mesa:amd64 (22.2.5-0ubuntu0.1~
22.04.1, 22.2.5-0ubuntu0.1~22.04.2), python3-apport:amd64 (2.20.11-0ubuntu82.4, 2.20.11-0ubuntu82.5), libegl-mesa0:amd64 (22.2.5-0ubuntu0.1~22.04.1, 22.2.5-0ubuntu0.1~22.04.2)
, libncursesw6:amd64 (6.3-2, 6.3-2ubuntu0.1), ncurses-bin:amd64 (6.3-2, 6.3-2ubuntu0.1), mesa-vdpau-drivers:amd64 (22.2.5-0ubuntu0.1~22.04.1, 22.2.5-0ubuntu0.1~22.04.2), ncurs
es-term:amd64 (6.3-2, 6.3-2ubuntu0.1), python3-problem-report:amd64 (2.20.11-0ubuntu82.4, 2.20.11-0ubuntu82.5), libncurses5:i386 (6.3-2, 6.3-2ubuntu0.1), libncurses6:amd64 (6.
3-2, 6.3-2ubuntu0.1)
End-Date: 2023-05-24  10:18:56

I am attaching a screenshot of my screen when started. It should open MS Teams app on start.

Steps to reproduce (if applicable)

start wavebox

[Thomas101]

Hi, we've had some other users report this and it seems to be a problem with Chromium 113 and a broken Mesa driver. Try quitting Wavebox, removing ~/.config/wavebox/Default/GPUCache/ and starting it up again - this should fix it

[jeka]

Hi, that solution would fix only wavebox. I've noticed that some pages are not rendered correctly in Chrome itself too, namely online versions of MS Office. I took another approach for the time being: enabled ppa:kisak/kisak-mesa and updated mesa-related packages from there. That fixed all the problems I was facing, including Chrome itself.