Bug 311382 – Webkit2gtk crashes when trying to login in Proton Authenticator app.

• Status: NEW
• Component: JavaScriptCore

Created attachment 478912 [details]
Button to open login form

Steps to reproduce:
1. Create a proton account at https://account.proton.me/start
1. Install the .deb from https://proton.me/authenticator
2. Open the app and login with you account credentials (see the attached screenshot)

Result is a hang of the app, followed by a crash dump notification and the loaded site inside the app goes blank.
Kubuntu debuginfod servers doesn't seem to have symbols... ¯\_(ツ)_/¯

[Thread debugging using libthread_db enabled]                                                                                                         
Using host libthread_db library "/usr/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/x86_64-linux-gnu/webkit2gtk-4.1/WebKitWebProcess 6 30'.
Program terminated with signal SIGTRAP, Trace/breakpoint trap.
#0  0x000073bb1259c801 in ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.1.so.0
[Current thread is 1 (Thread 0x73ba28df86c0 (LWP 46275))]
(gdb) bt full
#0  0x000073bb1259c801 in ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.1.so.0
No symbol table info available.
#1  0x0000000000030002 in ?? ()
No symbol table info available.
#2  0x0000000000030002 in ?? ()
No symbol table info available.
#3  0x0000000000000000 in ?? ()
No symbol table info available.

Operating System: Kubuntu 26.04
KDE Plasma Version: 6.6.3
KDE Frameworks Version: 6.24.0
Qt Version: 6.10.2
Kernel Version: 7.0.0-10-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 8 GiB of RAM (7.6 GiB usable)
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Acer
Product Name: Aspire A515-51G
System Version: V2.02

Created attachment 479160 [details]
thread_apply_all_bt.txt

This issue also reproduces in Fedora 44. I managed to obtain debug symbols on Fedora, but the specific frame for the crashing thread still seems to be missing details. Probably some JIT?

#0  0x00007fa836a44901 in ipint_reserved_0xcb_validate () from /lib64/libjavascriptcoregtk-4.1.so.0
No symbol table info available.
#1  0x0000000000030002 in ?? ()
No symbol table info available.
#2  0x0000000000030002 in ?? ()
No symbol table info available.
#3  0x0000000000000000 in ?? ()
No symbol table info available.

Also attached backtrace for other threads as attachment.

I don't know if this is caused by Webkit2gtk, but I'm experiencing similar symptoms with the same application.
I'm running Debian Testing and Debian Sid (unstable).

I can't use the Proton Authenticator app. When I enter the password, try to enable synchronization on new installation, or create a password on new installation, the app screen turns gray/white and nothing happens.
It seems to be spinning its wheels.

I don't know if this is caused by Webkit2gtk, but I'm experiencing similar symptoms with the same application.
I'm running Debian Testing and Debian Sid (unstable).

I can't use the Proton Authenticator app. When I enter the password, try to enable synchronization on new installation, or create a password on new installation, the app screen turns gray/white and nothing happens.
It seems to be spinning its wheels.

Correction: It works on Debian Testing. But it doesn't work on Debian Unstable.
Here are some details about the Debian systems used:
Both are running Xfce and X11:
Xfce version: 4.20
GTK version: 3.24.52 for Debian Unstable
                      3.24.49 for Debian Testing