Ente auth app crash on close (flatpak)

[whdmike]

Description

App crashes on close - Flatpak - Fedora

       PID: 47017 (enteauth)
       UID: 1000 (m....an)
       GID: 1000 (m......n)
    Signal: 11 (SEGV)
 Timestamp: Tue 2026-03-10 14:36:20 CET (5s ago)

Command Line: enteauth
Executable: /app/share/enteauth/enteauth
Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-flatpak-io.ente.auth-3052471915.scope
Unit: user@1000.service
User Unit: app-flatpak-io.ente.auth-3052471915.scope
Slice: user-1000.slice
Owner UID: 1000 (m......n)
Boot ID: c4da33dc8e294a5881cba0f626ebec8c
Machine ID: 44f658c0e.........33d
Hostname: fedora
Storage: /var/lib/systemd/coredump/core.enteauth.1000.c4da33dc8e294a5881cba0f626ebec8c.47017.1773149780000000.zst (present)
Size on Disk: 8.3M
Message: Process 47017 (enteauth) of user 1000 dumped core.

            Module /usr/lib/x86_64-linux-gnu/libglycin-2.so.0 without build-id.
            Module /usr/lib/x86_64-linux-gnu/libglycin-2.so.0
            Stack trace of thread 2:
            #0  0x00007f81bad27d74 n/a (/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2419.32 + 0x527d74)
            ELF object binary architecture: AMD x86-64

Version

4.4.12

What product are you using?

Ente Auth

What platform are you using?

Desktop - Linux

[alexjfinch]

I can reproduce this consistently on every close. Same version, same platform. The journalctl output gives more context about what's happening before the segfault:
Environment:

Fedora (Wayland, GNOME)
Flatpak 4.4.12+521
Framework 13 AMD (Ryzen), Mesa/RadeonSI GPU

Key lines from journalctl -b | grep -i ente immediately before the crash:

io.ente.auth[10251]: eglMakeCurrent failed
io.ente.auth.desktop[10251]: embedder.cc (2566): 'FlutterEngineRemoveView' returned 'kInvalidArguments'. Remove view info was invalid. The implicit view cannot be removed.
kernel: enteauth[10251]: segfault at 18 ip 00007ff08a527d74 sp 00007ffd4045d2f8 error 4 in libgtk-3.so.0.2419.32[527d74,7ff08a21b000+3c0000]

The crash is 100% reproducible on close — the app works correctly otherwise. The sequence suggests Flutter's EGL context is being torn down on window close, eglMakeCurrent then fails, and the engine crashes attempting to remove the view with an already-invalid GL context.

The same offset (527d74 in libgtk-3.so) appears across multiple runs, suggesting this is deterministic rather than a random memory corruption.

Setting LIBGL_ALWAYS_SOFTWARE=1 did not resolve the crash, indicating the issue is in GTK3's cleanup path rather than GPU rendering itself.

[Baysul]

I'm able to consistently reproduce this issue as well.

[whdmike]

I tried to use AppImage, and on Fedora Kinoite it doesn't start. But that is another issue or bug to open...