[X] 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
[X] I have checked the issue tracker to see if others have reported similar issues.
Current Behavior
I encountered this error with the Mullvad app in the background, so I went to go and get logs, however received the same error upon clicking "View app logs" (which is the best way I've found to reproduce it):
Expected Behavior
No error occurs
Steps to Reproduce
Open the app
Navigate to the report a problem page
Click View app logs
Failure Logs
I see no mention of the error in the generated log file that is present which clicking the aforementioned logs button, nor any of the files that it references. Here are the logs regarding the frontend anyway (the multiple report written logs are me reproducing the issue):
====================
Log: ~/.config/Mullvad VPN/logs/frontend-main.log
====================
[2024-05-16 19:36:26.339][verbose] Chromium sandbox is enabled
[2024-05-16 19:36:26.340][info] Running version 2024.3
[2024-05-16 19:36:26.445][info] Detected locale: en-GB
[2024-05-16 19:36:26.542][info] Connected to the daemon
[2024-05-16 19:36:26.638][info] Autoconnect the tunnel
[2024-05-16 20:36:26.573][verbose] GRPC Channel connectivity state changed to 2
[2024-05-16 21:36:26.593][verbose] GRPC Channel connectivity state changed to 2
[2024-05-16 22:36:26.602][verbose] GRPC Channel connectivity state changed to 2
[2024-05-16 23:36:26.614][verbose] GRPC Channel connectivity state changed to 2
[2024-05-17 00:36:26.631][verbose] GRPC Channel connectivity state changed to 2
[2024-05-17 01:36:26.658][verbose] GRPC Channel connectivity state changed to 2
[2024-05-17 02:36:26.703][verbose] GRPC Channel connectivity state changed to 2
[2024-05-17 02:38:02.378][verbose] Problem report was written to /tmp/[REDACTED].log
[2024-05-17 02:41:49.764][verbose] Problem report was written to /tmp/[REDACTED].log
[2024-05-17 02:41:59.585][verbose] Problem report was written to /tmp/[REDACTED].log
[2024-05-17 02:42:51.455][verbose] Problem report was written to /tmp/[REDACTED].log
====================
Log: ~/.config/Mullvad VPN/logs/frontend-renderer.log
====================
[2024-05-16 19:36:27.232][verbose] Tunnel state: connected
[2024-05-16 19:36:27.232][verbose] Initial: Wrong content height: 593, expected 568
[2024-05-16 19:36:27.317][verbose] Map canvas scale factor: 1, using: 1
[2024-05-17 02:40:19.118][verbose] Map canvas scale factor: 1, using: 1
Is it a bug?
I have checked if others have reported this already
Current Behavior
I encountered this error with the Mullvad app in the background, so I went to go and get logs, however received the same error upon clicking "View app logs" (which is the best way I've found to reproduce it):
Expected Behavior
No error occurs
Steps to Reproduce
View app logs
Failure Logs
I see no mention of the error in the generated log file that is present which clicking the aforementioned logs button, nor any of the files that it references. Here are the logs regarding the frontend anyway (the multiple report written logs are me reproducing the issue):
Operating system version
Fedora Linux 40 (KDE Plasma)
Mullvad VPN app version
Only occured in 2024.3, installed from the mullvad-beta RPM repo
Additional Information
Thanks, Elliott