GUI in 3.34 LTR Prizren does not display properly on PopOS 22.04 with Mate Window Manager

[82Streetcar]

What is the bug or the crash?

I am running PopOS 22.04 with the Mate window manager. Until recently, I had been using QGIS 3.28 LTR Firenze without issue, but my package manager recently updated me to QGIS 3.34 FTR Prizren. Unfortunately, I discovered that when I opened the Prizren install, the GUI was not displaying correctly, with buttons and the like weirdly compressed:

Furthermore, I found that the hot locations to click for buttons and text (for example in the Layers menu) were offset a significant amount from their visual depictions. I was able to downgrade back to Firenze to continue using QGIS, but I haven't been able to find any documentation online of this issue, or what might be causing it/how to get Prizren to play nice with my set-up.

Steps to reproduce the issue

Installing QGIS 3.34 FTR Prizren on a Linux machine running Ubuntu or, ideally, PopOS, version 22.04 with the Mate window manager was sufficient for me to get the abberent behavior discussed above.

Versions

3.34 Prizren. Unfortunately, I've already downgraded back to Firenze, and so can't copy the text to confirm.

Supported QGIS version

• I'm running a supported QGIS version according to the roadmap.

New profile

• I tried with a new QGIS profile

Additional context

No response

[nyalldawson]

Are you running an x11 or Wayland session?

[82Streetcar]

I'm running an X11 session. (I'm sorry I didn't specify that in the original report: I didn't actually know the distinction until looking it up to figure out how to answer your question.

…

On Sun, May 5, 2024 at 3:39 PM Nyall Dawson ***@***.***> wrote: Are you running an x11 or Wayland session? — Reply to this email directly, view it on GitHub <#57345 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BIJHRPMQ42QL7GP2BTHO3RLZA2DFRAVCNFSM6AAAAABHH2TCGCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJUHEZDINZUGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>