Before submitting
Operating system
Linux
System details
Fedora Linux 44, KDE Plasma, Wayland, x86_64, Intel graphics, Mesa 26.1.5
OpenQuota version
0.4.1
Affected provider
Not provider-specific
What happened?
OpenQuota 0.4.1 crashes immediately when launching the official OpenQuota_0.4.1_amd64.AppImage on Fedora 44 KDE Plasma.
The bundled WebKitGTK WebKitWebProcess aborts during EGL initialization with:
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...
The process then terminates with SIGABRT and produces a core dump.
The application does not reach a usable UI, so the issue occurs before configuring or using any provider.
Steps to reproduce
-
Download OpenQuota_0.4.1_amd64.AppImage from the official v0.4.1 GitHub release.
-
Make the AppImage executable.
-
Launch it on Fedora Linux 44 KDE Plasma / Wayland.
-
Observe that the application immediately fails with:
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...
-
WebKitWebProcess terminates with SIGABRT.
Expected behavior
OpenQuota should launch normally and display its main interface on Fedora 44 KDE Plasma.
Additional context
I also tested the following launch-time workarounds, but all produced the same EGL error and WebKitWebProcess crash:
GDK_BACKEND=x11 ./OpenQuota_0.4.1_amd64.AppImage
WEBKIT_DISABLE_DMABUF_RENDERER=1 ./OpenQuota_0.4.1_amd64.AppImage
WEBKIT_DISABLE_COMPOSITING_MODE=1 ./OpenQuota_0.4.1_amd64.AppImage
Relevant reviewed log excerpt:
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...
The crashing executable is the WebKitGTK process bundled inside the AppImage, under a path similar to:
/tmp/.mount_OpenQu.../usr/lib/x86_64-linux-gnu/webkit2gtk-4.1/WebKitWebProcess
System graphics stack observed in the crash report includes Mesa 26.1.5 and libEGL/libGL from Fedora 44.
No credentials, account identifiers, tokens, or provider data are included in this report.
Before submitting
Operating system
Linux
System details
Fedora Linux 44, KDE Plasma, Wayland, x86_64, Intel graphics, Mesa 26.1.5
OpenQuota version
0.4.1
Affected provider
Not provider-specific
What happened?
OpenQuota 0.4.1 crashes immediately when launching the official
OpenQuota_0.4.1_amd64.AppImageon Fedora 44 KDE Plasma.The bundled WebKitGTK
WebKitWebProcessaborts during EGL initialization with:Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...The process then terminates with SIGABRT and produces a core dump.
The application does not reach a usable UI, so the issue occurs before configuring or using any provider.
Steps to reproduce
Download
OpenQuota_0.4.1_amd64.AppImagefrom the official v0.4.1 GitHub release.Make the AppImage executable.
Launch it on Fedora Linux 44 KDE Plasma / Wayland.
Observe that the application immediately fails with:
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...WebKitWebProcessterminates with SIGABRT.Expected behavior
OpenQuota should launch normally and display its main interface on Fedora 44 KDE Plasma.
Additional context
I also tested the following launch-time workarounds, but all produced the same EGL error and WebKitWebProcess crash:
GDK_BACKEND=x11 ./OpenQuota_0.4.1_amd64.AppImageWEBKIT_DISABLE_DMABUF_RENDERER=1 ./OpenQuota_0.4.1_amd64.AppImageWEBKIT_DISABLE_COMPOSITING_MODE=1 ./OpenQuota_0.4.1_amd64.AppImageRelevant reviewed log excerpt:
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...The crashing executable is the WebKitGTK process bundled inside the AppImage, under a path similar to:
/tmp/.mount_OpenQu.../usr/lib/x86_64-linux-gnu/webkit2gtk-4.1/WebKitWebProcessSystem graphics stack observed in the crash report includes Mesa 26.1.5 and libEGL/libGL from Fedora 44.
No credentials, account identifiers, tokens, or provider data are included in this report.