Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App Graphical Interface Does Not Display In New Version 2024.8 in Pop!_OS 22.04 LTS #7284

Open
2 tasks done
amd1890 opened this issue Dec 4, 2024 · 7 comments
Open
2 tasks done
Labels
bug Desktop frontend Issues related to the desktop GUI Linux Issues related to Linux

Comments

@amd1890
Copy link

amd1890 commented Dec 4, 2024

Is it a bug?

  • I know this is an issue with the app, and contacting Mullvad support is not relevant.

I have checked if others have reported this already

  • I have checked the issue tracker to see if others have reported similar issues.

Current Behavior

The Mullvad VPN is not displaying any information at all. When I open it, there is a green lock displayed and it shows a notification of a connection. The lock then disappears. There is no window displaying any information for the App. I can check the connection using the command line and the tunnel is connecting. I can use socks in the Mullvad Browser.

Expected Behavior

App opens allowing features to be changed with graphical interface and lock does not go away.

Steps to Reproduce

Install Pop!_OS 22.04 LTS.
Install Mullvad 2024.8 and open App using icon.

Failure Logs

System information:
id: 173ccfd8-301e-4c96-b154-91d8e537e1b6
kernel: 6.9.3-76060903-generic
mullvad-product-version: 2024.8
nm: 1.36.6
os: Linux Pop!_OS 22.04 LTS
systemd: systemd 249 (249.11-0ubuntu3.12pop0~1727961019~22.04~2b3beb7)

====================
Log: ~/.config/Mullvad VPN/logs/frontend-main.log
====================
[2024-12-04 20:04:13.205][verbose] Chromium sandbox is enabled
[2024-12-04 20:04:13.206][info] Running version 2024.8
[2024-12-04 20:04:13.284][info] Detected locale: en-US
[2024-12-04 20:04:13.442][info] Connected to the daemon
[2024-12-04 20:04:13.520][info] Skip autoconnect because GUI setting is disabled
[2024-12-04 20:04:14.304][error] Child process of type GPU exited with exit code 139 due to crashed
[2024-12-04 20:04:15.227][error] Child process of type GPU exited with exit code 139 due to crashed
[2024-12-04 20:04:16.048][error] Child process of type GPU exited with exit code 139 due to crashed
[2024-12-04 20:04:16.874][error] Child process of type GPU exited with exit code 139 due to crashed
[2024-12-04 20:04:17.668][error] Child process of type GPU exited with exit code 139 due to crashed
[2024-12-04 20:04:18.478][error] Child process of type GPU exited with exit code 139 due to crashed
[2024-12-04 20:04:18.609][error] Child process of type GPU exited with exit code 139 due to crashed
[2024-12-04 20:04:18.740][error] Child process of type GPU exited with exit code 139 due to crashed

====================
Log: ~/.config/Mullvad VPN/logs/frontend-main.old.log
====================
[2024-12-04 19:57:42.648][verbose] Chromium sandbox is enabled
[2024-12-04 19:57:42.649][info] Running version 2024.8
[2024-12-04 19:57:42.730][info] Detected locale: en-US
[2024-12-04 19:57:42.893][info] Connected to the daemon
[2024-12-04 19:57:42.936][warning] Failed to fetch account data. Retrying in 8000 ms
[2024-12-04 19:57:42.936][warning] Failed to update device info: 14 UNAVAILABLE: Cannot reach the API
[2024-12-04 19:57:42.971][info] Skip autoconnect because GUI setting is disabled
[2024-12-04 19:57:43.761][error] Child process of type GPU exited with exit code 139 due to crashed
[2024-12-04 19:57:44.812][error] Child process of type GPU exited with exit code 139 due to crashed
[2024-12-04 19:57:45.785][error] Child process of type GPU exited with exit code 139 due to crashed
[2024-12-04 19:57:46.768][error] Child process of type GPU exited with exit code 139 due to crashed
[2024-12-04 19:57:47.749][error] Child process of type GPU exited with exit code 139 due to crashed
[2024-12-04 19:57:48.711][error] Child process of type GPU exited with exit code 139 due to crashed
[2024-12-04 19:57:48.855][error] Child process of type GPU exited with exit code 139 due to crashed
[2024-12-04 19:57:48.997][error] Child process of type GPU exited with exit code 139 due to crashed

Operating system version

Pop!_OS 22.04 LTS

Mullvad VPN app version

2024.8

Additional Information

Using rocm drivers for amd Ryzen graphics

@amd1890 amd1890 added the bug label Dec 4, 2024
@raksooo
Copy link
Member

raksooo commented Dec 5, 2024

Thanks for reporting this! This looks like an incompatibility in Electron/Chromium. Unfortunately we don't officially support Pop OS. I can imagine this being connected to graphics card/driver as well.

We do intend to update Electron soon which might solve this issue.

@raksooo
Copy link
Member

raksooo commented Dec 5, 2024

You could try to run the app without GPU acceleration: /opt/Mullvad\ VPN/mullvad-vpn --disable-gpu

@hulthe hulthe added Linux Issues related to Linux Desktop frontend Issues related to the desktop GUI labels Dec 5, 2024
@amd1890
Copy link
Author

amd1890 commented Dec 5, 2024

You could try to run the app without GPU acceleration: /opt/Mullvad\ VPN/mullvad-vpn --disable-gpu

$ /opt/Mullvad\ VPN/mullvad-vpn --disable-gpu
[2024-12-05 14:28:22.469][verbose] Chromium sandbox is enabled
[2024-12-05 14:28:22.470][info] Running version 2024.8
[2024-12-05 14:28:22.546][info] Detected locale: en-US
[2024-12-05 14:28:22.715][info] Connected to the daemon
[2024-12-05 14:28:22.792][info] Skip autoconnect because GUI setting is disabled
ac: Unknown GPU, using 0 for raster_config
Cannot find target for triple amdgcn-- Unable to find target for this triple (no targets are registered)
[27589:1205/142823.530703:ERROR:gpu_process_host.cc(997)] GPU process exited unexpectedly: exit_code=139
[2024-12-05 14:28:23.531][error] Child process of type GPU exited with exit code 139 due to crashed
ac: Unknown GPU, using 0 for raster_config
Cannot find target for triple amdgcn-- Unable to find target for this triple (no targets are registered)
[27589:1205/142824.466773:ERROR:gpu_process_host.cc(997)] GPU process exited unexpectedly: exit_code=139
[2024-12-05 14:28:24.467][error] Child process of type GPU exited with exit code 139 due to crashed
ac: Unknown GPU, using 0 for raster_config
Cannot find target for triple amdgcn-- Unable to find target for this triple (no targets are registered)
[27589:1205/142825.388801:ERROR:gpu_process_host.cc(997)] GPU process exited unexpectedly: exit_code=139
[2024-12-05 14:28:25.389][error] Child process of type GPU exited with exit code 139 due to crashed
ac: Unknown GPU, using 0 for raster_config
Cannot find target for triple amdgcn-- Unable to find target for this triple (no targets are registered)
[27589:1205/142825.539285:ERROR:gpu_process_host.cc(997)] GPU process exited unexpectedly: exit_code=139
[2024-12-05 14:28:25.539][error] Child process of type GPU exited with exit code 139 due to crashed
ac: Unknown GPU, using 0 for raster_config
Cannot find target for triple amdgcn-- Unable to find target for this triple (no targets are registered)
[27589:1205/142825.697807:ERROR:gpu_process_host.cc(997)] GPU process exited unexpectedly: exit_code=139
[2024-12-05 14:28:25.698][error] Child process of type GPU exited with exit code 139 due to crashed
ac: Unknown GPU, using 0 for raster_config
Cannot find target for triple amdgcn-- Unable to find target for this triple (no targets are registered)
[27589:1205/142825.858094:ERROR:gpu_process_host.cc(997)] GPU process exited unexpectedly: exit_code=139
[27589:1205/142825.858144:FATAL:gpu_data_manager_impl_private.cc(448)] GPU process isn't usable. Goodbye.
Trace/breakpoint trap (core dumped)

i get the same error without the flag.

@amd1890
Copy link
Author

amd1890 commented Dec 5, 2024

Thanks for reporting this! This looks like an incompatibility in Electron/Chromium. Unfortunately we don't officially support Pop OS. I can imagine this being connected to graphics card/driver as well.

We do intend to update Electron soon which might solve this issue.

It's frustrating because Ubuntu has a modified gnome interface with an unwanted toolbar and some hardware just wouldn't work. Ubuntu also asks to send telemetry, which I don't like. When I tried Debian the kernel also led to problems, I probably should have just tried Debian testing or Debian unstable. I tried Ubuntu and Debian with this system prior to trying Pop.

Can you think of any other way to run it so there's some visual information? Command line makes it much harder to switch things easily. I wish there were a nyx-like version of things for terminal, but probably few would use it.

I still don't understand what is causing the problem because it worked perfectly in 2024.7. It was only when I did sudo apt update && sudo apt upgrade -y that this problem started, and I can use timeshift to revert the upgrade but then I am dealing with unpatched software.

@tomaskikutis
Copy link

It does work fine for me (os info). I'm using AMD integrated graphics.

@amd1890
Copy link
Author

amd1890 commented Dec 19, 2024

It does work fine for me (os info). I'm using AMD integrated graphics.

Do you have the rocm package installed? I timeshifted to prior to rocm being installed and didn't install rocm again and the error went away. I just wish I could install rocm again.

This is specific to the rocm package then, which comes from amd's repository.

@tomaskikutis
Copy link

No, I don't have rocm package

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Desktop frontend Issues related to the desktop GUI Linux Issues related to Linux
Projects
None yet
Development

No branches or pull requests

4 participants