White Screen

[Johnnyreyman]

When I first launch the app it is showing only a white screen.
Running on Steam Deck with Latest Nobara OS 43.

[madisvain]

@Johnnyreyman Sorry to hear this. I got a sentry exception that "Migration failed: migration 18 was previously applied but is missing in the resolved migrations"

Was this a fresh install? Or have you used upcount before?

[Johnnyreyman]

This was on a fresh install. Using the Appimage AMD64 version. I installed the rpm instead and it just works.

[madisvain]

@Johnnyreyman thank you - it's awesome to hear it works. The crash was about database initialization. We are anyway refactoring it so every organization will have its own database and can be stored anywhere. Also in dropbox etc. Kinda like KeePass files are.

I'll try to spin up a virtual machine to test out the Appimage failure you had also.

[vfauth]

I got the same issue when trying the AppImage in Manjaro:

Initializing database at: sqlite:///home/victor/.local/share/com.upcount.dev/sqlite.db
SQLite version: 3.46.0
Database initialized successfully
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

** (upcount:93574): WARNING **: 19:06:28.173: atk-bridge: get_device_events_reply: unknown signature```

[madisvain]

@vfauth thank you for reporting this - I'll take a look

[Kentoseth]

Just bumping this to find out if the bug has been resolved. The app isn't usable at all with the white screen bug.

Hoping a fix is in the works soon.

[madisvain]

@Johnnyreyman @vfauth @Kentoseth — a fix for this is now released in v2.0.0-beta.24.

Root cause: the AppImage was built on ubuntu-22.04, which bundled WebKitGTK 2.36/2.40. That version calls the deprecated eglGetDisplay(EGL_DEFAULT_DISPLAY), which libglvnd 1.7+ (shipped on Ubuntu 26.04, Nobara, recent Manjaro, and likely Steam Deck's current OS) rejects with EGL_BAD_PARAMETER. The new AppImage is built on ubuntu-24.04 with libwebkit2gtk-4.1 ≥ 2.44, which uses the modern eglGetPlatformDisplay API. Fix in #211.

New AppImage: https://github.com/namespace-ee/upcount/releases/download/v2.0.0-beta.24/Upcount_2.0.0-beta.24_amd64.AppImage

Could you give it a try and confirm? If it launches cleanly I'll close this issue.

[Kentoseth]

Could you give it a try and confirm? If it launches cleanly I'll close this issue.

./Upcount_2.0.0-beta.24_amd64.AppImage
Gtk-Message: 21:20:30.714: Failed to load module "appmenu-gtk-module": 'gtk_module_display_init': /usr/lib64/gtk-3.0/modules/libwindow-decorations-gtk-module.so: undefined symbol: gtk_module_display_init
Initializing database at: sqlite:///home/client/.local/share/com.upcount.dev/sqlite.db
SQLite version: 3.46.0
Database initialized successfully
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

Issue persists on my end.

[madisvain]

Thanks for testing @Kentoseth — sorry to hear it still crashes. The EGL error is the same as before, which means the fix in #211 didn't fully cover your environment.

To narrow it down, could you share:

1. Distro and version (cat /etc/os-release)
2. GPU/driver (glxinfo -B | head or just the vendor — Intel / AMD / NVIDIA + Mesa version)
3. libwebkit2gtk and libglvnd versions on your system:

   ldconfig -p | grep -E 'libwebkit2gtk-4\.1|libEGL|libGLdispatch'
   apt list --installed 2>/dev/null | grep -E 'libwebkit2gtk-4.1|libglvnd' || \
   rpm -qa 2>/dev/null | grep -E 'libwebkit2gtk|libglvnd' || \
   pacman -Q 2>/dev/null | grep -E 'webkit2gtk|libglvnd'
   

Also: the extra appmenu-gtk-module ... undefined symbol: gtk_module_display_init line in your log suggests there may be a separate GTK module mismatch on your system. That alone wouldn't cause the crash, but it points to a deeper lib mismatch between what the AppImage bundles and what your system loads.

In the meantime, if you have a .deb or .rpm based distro, the native package (Upcount_2.0.0-beta.24_amd64.deb or Upcount-2.0.0-beta.24-1.x86_64.rpm on the release page) should work — it uses your system's WebKitGTK instead of the bundled one, which was @Johnnyreyman's successful workaround.

[lnagel]

Issue persists on my side as well on the latest release. I can build a working version locally on Kubuntu 26.04 LTS though. So this means the build chain issue persists in GitHub.

$ ldconfig -p | grep -E 'libwebkit2gtk-4\.1|libEGL|libGLdispatch'
apt list --installed 2>/dev/null | grep -E 'libwebkit2gtk-4.1|libglvnd' || \
rpm -qa 2>/dev/null | grep -E 'libwebkit2gtk|libglvnd' || \
pacman -Q 2>/dev/null | grep -E 'webkit2gtk|libglvnd'
        libwebkit2gtk-4.1.so.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.1.so.0
        libwebkit2gtk-4.1.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.1.so
        libGLdispatch.so.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0
        libGLdispatch.so.0 (libc6) => /usr/lib/i386-linux-gnu/libGLdispatch.so.0
        libGLdispatch.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libGLdispatch.so
        libEGL_mesa.so.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libEGL_mesa.so.0
        libEGL_mesa.so.0 (libc6) => /usr/lib/i386-linux-gnu/libEGL_mesa.so.0
        libEGL.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libEGL.so.1
        libEGL.so.1 (libc6) => /usr/lib/i386-linux-gnu/libEGL.so.1
        libEGL.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libEGL.so
libglvnd-core-dev/resolute,now 1.7.0-3 amd64 [installed,automatic]
libglvnd-dev/resolute,now 1.7.0-3 amd64 [installed,automatic]
libglvnd0/resolute,now 1.7.0-3 amd64 [installed,automatic]
libglvnd0/resolute,now 1.7.0-3 i386 [installed,automatic]
libwebkit2gtk-4.1-0/resolute-security,resolute-updates,now 2.52.3-0ubuntu0.26.04.2 amd64 [installed,automatic]
libwebkit2gtk-4.1-dev/resolute-security,resolute-updates,now 2.52.3-0ubuntu0.26.04.2 amd64 [installed]