[Linux] GPU process crashes on startup (exit_code=11) with AMD + Mesa on Debian 12 — window never shown, --disable-gpu as workaround

[ghostintheshell-192]

• I have searched open and closed issues for duplicates
• This isn't a feature request
• This is not a report about my app not working as expected

---

Is it expected that --disable-gpu is now required on AMD + Mesa (Debian 12)
starting from 1.13.0? Previous versions worked without it. I'll describe what happens.

Description

Starting with version 1.13.0, the app launches but the window never appears.
Previous versions (tested up to 1.12.1 as far as I remember) worked correctly without any flags.

The GPU subprocess crashes immediately at startup with exit code 11 (SIGSEGV),
and the app never shows its window, yet the web content continues to load in the background (the mail view fetches assets and navigates to /u/0/ successfully).

Environment

• OS: Debian 12 (Bookworm), kernel 6.12.12+bpo-amd64
• GPU: AMD (vendorId 0x1002, deviceId 0x164E and 0x747E)
• Display server: Wayland (XDG_SESSION_TYPE=wayland)
• Proton Mail Desktop version: 1.13.0

Relevant log output

GPU process exited unexpectedly: exit_code=11
App#child-process-gone: { type: 'GPU', reason: 'crashed', exitCode: 11 }
quit-reason set: child-crash: crashed (11)

GPU info from log:

"glImplementationParts":"(gl=none,angle=none)"
"hardwareSupportsVulkan":false
"inProcessGpu":true

OpenGL initialization fails completely — both native GL and ANGLE report none.

Workaround

proton-mail --disable-gpu

This allows the app to start and work normally.

Notes

AMD + Mesa on Debian stable is a very common configuration.