mullvadvpn-app icon indicating copy to clipboard operation
mullvadvpn-app copied to clipboard

Published 20 hours ago • verified publisher icon mullvad

Mullvad VPN GUI crashes on Linux

Open Project579 opened this issue 1 year ago • 20 comments

Issue report

Operating system: Arch Linux

App version: 2023.6

Issue description

After the latest update to version 2023.6 the Mullvad VPN GUI application for Linux crashes after a few seconds, it seems to be caused by a bug in Electron 26: https://github.com/electron/electron/issues/32760

Application log

[2023-12-07 00:34:55.807][verbose] Chromium sandbox is disabled
[2023-12-07 00:34:55.807][info] Running version 2023.6
[2023-12-07 00:34:55.894][info] Detected locale: en-US
[2023-12-07 00:34:55.941][info] Connected to the daemon
[2023-12-07 00:34:56.070][info] Skip autoconnect because GUI setting is disabled
[28098:1207/003458.465706:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[28098:1207/003458.478125:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[28098:1207/003500.270665:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
[2023-12-07 00:35:01.469][error] Render process exited with exit code 139 due to crashed
[2023-12-07 00:35:01.469][info] before-quit received
[2023-12-07 00:35:01.470][info] Quit initiated
[2023-12-07 00:35:01.471][info] Unsubscribed from the daemon events
[2023-12-07 00:35:01.471][verbose] GRPC Channel connectivity state changed to 4
[2023-12-07 00:35:01.472][info] Disposable logging outputs disposed
[2023-12-07 00:35:01.472][info] Quit preparations finished
[2023-12-07 00:35:01.478][info] will-quit received
[2023-12-07 00:35:01.479][info] quit received

Project579 avatar Dec 06 '23 23:12 Project579

Thanks for reporting! Is this happening every time you launch the GUI? Does it help if you launch it with --disable-gpu? (/opt/Mullvad\ VPN/mullvad-vpn --disable-gpu)

raksooo avatar Dec 07 '23 07:12 raksooo

Having the same issue. --disable-gpu didn't fix it for me, still crashing when I hover over the application. Arch Linux - 6.5.13-hardened2-1-hardened

m2rk1312 avatar Dec 07 '23 18:12 m2rk1312

Can confirm, --disable-gpu doesn't seem to have any effect.

Project579 avatar Dec 07 '23 19:12 Project579

Having the same issue on Fedora 39 after the newest update, though for me, the --disable-gpu option does seem to fix it. It's at least more stable for now. I'll update if it crashes again.

ADHDefy avatar Dec 08 '23 23:12 ADHDefy

Same issue

cloanyvpn avatar Dec 10 '23 22:12 cloanyvpn

Also having the same GUI issue on Arch Linux 6.6.6.

Using AUR package mullvad-vpn-bin 2023.6-1.

/opt/Mullvad\ VPN/mullvad-vpn gives:

[2023-12-13 16:09:19.831][verbose] Chromium sandbox is disabled
[2023-12-13 16:09:19.832][info] Running version 2023.6
[2023-12-13 16:09:19.874][info] Detected locale: en-GB
[2023-12-13 16:09:19.900][info] Connected to the daemon
[2023-12-13 16:09:19.964][info] Autoconnect the tunnel
src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 538982482

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 943215175

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 842094158

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 842094169

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 538982482

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 943215175

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 842094158

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 842094169

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 538982482

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 943215175

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 842094158

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 842094169

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 538982482

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 943215175

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 842094158

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 842094169

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 538982482

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 943215175

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 842094158

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 842094169

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

[2023-12-13 16:09:24.060][error] Render process exited with exit code 139 due to crashed
[2023-12-13 16:09:24.060][info] before-quit received
[2023-12-13 16:09:24.060][info] Quit initiated
[2023-12-13 16:09:24.060][info] Unsubscribed from the daemon events
[2023-12-13 16:09:24.061][verbose] GRPC Channel connectivity state changed to 4
[2023-12-13 16:09:24.061][info] Disposable logging outputs disposed
[2023-12-13 16:09:24.061][info] Quit preparations finished
[2023-12-13 16:09:24.067][info] will-quit received
[2023-12-13 16:09:24.067][info] quit received

/opt/Mullvad\ VPN/mullvad-vpn --disable-gpu gives

[2023-12-13 16:10:22.171][verbose] Chromium sandbox is disabled
[2023-12-13 16:10:22.171][info] Running version 2023.6
[2023-12-13 16:10:22.212][info] Detected locale: en-GB
[2023-12-13 16:10:22.239][info] Connected to the daemon
[2023-12-13 16:10:22.297][info] Autoconnect the tunnel
src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 538982482

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 943215175

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 842094158

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 842094169

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 538982482

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 943215175

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 842094158

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 842094169

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 538982482

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 943215175

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 842094158

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 842094169

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 538982482

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 943215175

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 842094158

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 842094169

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 538982482

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 943215175

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 842094158

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 842094169

src/gbm_drv_common.c:57: GBM-DRV error (get_bytes_per_component): Unknown or not supported format: 808530000

[2023-12-13 16:10:26.357][error] Render process exited with exit code 139 due to crashed
[2023-12-13 16:10:26.358][info] before-quit received
[2023-12-13 16:10:26.358][info] Quit initiated
[2023-12-13 16:10:26.358][info] Unsubscribed from the daemon events
[2023-12-13 16:10:26.358][verbose] GRPC Channel connectivity state changed to 4
[2023-12-13 16:10:26.359][info] Disposable logging outputs disposed
[2023-12-13 16:10:26.359][info] Quit preparations finished
[2023-12-13 16:10:26.369][info] will-quit received
[2023-12-13 16:10:26.369][info] quit received

raja-grewal avatar Dec 13 '23 05:12 raja-grewal

Same under Linux Mint 21.2 / Base: Ubuntu 22.04.3 LTS (Jammy)

App version: 2023.6

And also --disable-gpu doesn't solve the problem.

Any progress here?

mav-noob avatar Dec 20 '23 12:12 mav-noob

Hi. Arch linux user here. App version: 2023.6 --disable-gpu doesn't help

logs:

$ mullvad-vpn --disable-gpu
[2023-12-xx 00:30:34.816][verbose] Chromium sandbox is disabled
[2023-12-xx 00:30:34.817][info] Running version 2023.6
[2023-12-xx 00:30:34.879][info] Detected locale: en
[2023-12-xx 00:30:34.914][info] Connected to the daemon
[2023-12-xx 00:30:34.970][info] Autoconnect the tunnel
[19686:1221/140837.678201:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[19686:1221/140839.141300:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[2023-12-xx 00:30:43.144][error] Render process exited with exit code 139 due to crashed
[2023-12-xx 00:30:43.144][info] before-quit received
[2023-12-xx 00:30:43.144][info] Quit initiated
[2023-12-xx 00:30:43.144][info] Unsubscribed from the daemon events
[2023-12-xx 00:30:43.145][verbose] GRPC Channel connectivity state changed to 4
[2023-12-xx 00:30:43.145][info] Disposable logging outputs disposed
[2023-12-xx 00:30:43.145][info] Quit preparations finished
[2023-12-xx 00:30:43.149][info] will-quit received
[2023-12-xx 00:30:43.149][info] quit received

SyntheticBird45 avatar Dec 21 '23 13:12 SyntheticBird45

NixOS user here, App version: 2023.5 GUI starts normally and I could input my Account Number but any further interaction crashes the GUI. --disable-gpu actually worked for me!


mullvad-gui --disable-gpu
[2023-12-23 17:59:36.621][verbose] Chromium sandbox is enabled
[2023-12-23 17:59:36.624][info] Running version 2023.5
[4347:1223/175938.202991:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.InvalidArgs: No such interface “org.freedesktop.portal.FileChooser”
[4347:1223/175938.203638:ERROR:select_file_dialog_linux_portal.cc(274)] Failed to read portal version property
[2023-12-23 17:59:38.235][info] Detected locale: en-US

(mullvad-gui:4347): GLib-GIO-CRITICAL **: 17:59:38.249: g_settings_schema_source_lookup: assertion 'source != NULL' failed
[2023-12-23 17:59:38.302][error] Error while retrieving theme {"code":127,"killed":false,"signal":null,"cmd":"gsettings get org.gnome.desktop.interface icon-theme"}
[2023-12-23 17:59:38.311][info] Connected to the daemon
[2023-12-23 17:59:38.462][info] Skip autoconnect because GUI setting is disabled
[2023-12-23 17:59:38.967][error] Failed to check autostart file: ENOENT: no such file or directory, access '/home/ltm/.config/autostart/mullvad-vpn.desktop'

lasumn avatar Dec 23 '23 17:12 lasumn

App version: 2023.5

The issue I am having started occurring with version 2023.6.

Judging by the previous comments, this seems to be the case with other users as well.

I also had no issues with version 2023.5.

On the bright side, the delay in resolving this issue has gotten me accustomed with exclusively using the CLI.

raja-grewal avatar Dec 24 '23 08:12 raja-grewal

Having the same issue on Fedora 39 after the newest update, though for me, the --disable-gpu option does seem to fix it. It's at least more stable for now. I'll update if it crashes again.

Confirming: '--disable-gpu' is also working for me on Fedora 39

schweineimweltall avatar Dec 24 '23 10:12 schweineimweltall

Fedora 39 + Gnome (Wayland). Mullvad 2023.6

I don't know if my issue has same origin but the mullvad window displays nothing (see screenshot). Launching with --disable-gpu doesn't fix the issue. MullvadGUI-24-12-2023-Fedora39

Even if the window appears empty, it responds to certain mouse-click interactions, but no elements are displayed.

frontend-renderer.log :
2023-12-24 15:34:47.378][info] Loaded translations fr/messages
[2023-12-24 15:34:47.378][info] Loaded translations fr/relay-locations
[2023-12-24 15:34:47.379][verbose] Tunnel state: connected
[2023-12-24 15:34:47.380][verbose] Initial: Wrong content height: 596, expected 568
[2023-12-24 15:35:07.907][verbose] Resize: Wrong content height: 569, expected 568

Jo-Panic avatar Dec 24 '23 14:12 Jo-Panic

Yes for me too the latest upgrade is a huge regression. But this is another bug. Maybe relevant is that my GUI is completely pixelated mess, nothing usable at all.

secretmango avatar Dec 25 '23 20:12 secretmango

Same issue on Artix Linux

twann4 avatar Jan 02 '24 15:01 twann4

Having the same issue on Fedora 39 after the newest update, though for me, the --disable-gpu option does seem to fix it. It's at least more stable for now. I'll update if it crashes again.

Confirming: '--disable-gpu' is also working for me on Fedora 39

Some necessary information were missing in my post: Fedora 39, Gnome (Wayland), Mullvad 2023.5 Linux 6.6.9-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Jan 1 20:05:54 UTC 2024 x86_64 GNU/Linux

schweineimweltall avatar Jan 05 '24 16:01 schweineimweltall

I'm using Fedora 39 Cinnamon on X11, but am seeing the same as @Jo-Panic above. I'm running version 2023.6, but I'm not sure if the problem occurred due to the mullvad update or the update to Fedora 39, as I did both around the same time. When opened, the app window is either all white, all black, or black on the top third of the window and blue on the bottom (similar to how it would look normally, but none of the text / buttons / etc appear).

The app doesn't crash or freeze, clicking on the window title bar close button still closes it, but it appears the GUI doesn't load or render completely. The VPN still works, the tray icon and its context menu controls (reconnect, disconnect, quit) still work, but the app window / GUI itself doesn't.

Running it with --disable-gpu does fix it for me. If it doesn't work for you, make sure you "disconnect & quit" the currently running GUI app before you try opening it again with --disable-gpu.

seekermoc avatar Jan 08 '24 19:01 seekermoc

I have managed to solve the issue on my end without the use of --disable-gpu, I upgraded mesa to version 23.3.2 (latest on ArchLinux as of this writing), deleted any config files regarding Mullvad VPN in my home folder and that seems to have solved the issue, currently it functions just fine; I'm also running the app using the Wayland backed in case that makes a difference, also as another possible solution that has worked for me in the past with other applications is deleting the mesa shaders cache in your users home, as that can also sometimes cause weird crashes when mesa receives breaking changes.

Also I'm using an AMD GPU in case that makes any difference.

Project579 avatar Jan 08 '24 19:01 Project579

Same issue for me MacOS Sonoma 2023.6

BEaXt7f97 avatar Jan 17 '24 15:01 BEaXt7f97

Same issue on linux mint

Tre-brock avatar Feb 07 '24 14:02 Tre-brock

Same on Ubuntu 22.04.3 LTS (kernel = 6.5). It typically happens after waking my computer, but can happen at anytime. I'm using X11.

TJonCooper avatar Mar 31 '24 15:03 TJonCooper