Cant open settings

[SoyRober]

Im using the latests version of CachyOS with Hyprland Noctalia.

I installed mouzi using shelly. Whenever I try to open the settings I only get a gray window.

Ask for more info If needed.

[hsr88]

Hi, thanks for reporting this. This looks like a WebKitGTK rendering issue under Wayland/Hyprland rather than a problem with the settings themselves.
Mouzi already disables the WebKit DMABUF renderer on Linux, but accelerated compositing can still produce a blank or gray window on some GPU and driver combinations.
Could you please quit Mouzi completely from the tray and try launching it from a terminal with:
WEBKIT_DISABLE_COMPOSITING_MODE=1 mouzi
If mouzi is not available as a terminal command, please try running the downloaded AppImage directly:
WEBKIT_DISABLE_COMPOSITING_MODE=1 ./Mouzi_*.AppImage
Then open Settings again and let me know whether it renders correctly.
Please also send me:

echo $XDG_SESSION_TYPE
inxi -Gxx

It would also help to know whether Shelly installed Mouzi as an AppImage or another package type, and to see any output printed in the terminal when you open Settings.
If the compositing flag fixes it, I can include the workaround in the next build.

[SoyRober]

If I use the command "WEBKIT_DISABLE_COMPOSITING_MODE=1 ./Mouzi_*.AppImage" I only get a "Could not create default EGL display: EGL_BAD_PARAMETER. Aborting..." when I open the app, any tab.

Here's the "echo $XDG_SESSION_TYPE && inxi -Gxx" info:

Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 44 [Radeon RX 9060 XT]
    vendor: ASRock driver: amdgpu v: kernel arch: RDNA-4 pcie: speed: 32 GT/s
    lanes: 16 ports: active: DP-2,HDMI-A-1 empty: DP-1,Writeback-1
    bus-ID: 2f:00.0 chip-ID: 1002:7590
  Device-2: Razer USA Kiyo Pro driver: snd-usb-audio,uvcvideo type: USB
    rev: 3.2 speed: 5 Gb/s lanes: 1 bus-ID: 6-3:2 chip-ID: 1532:0e05
  Display: wayland server: X.org v: 1.21.1.24 with: Xwayland v: 24.1.13
    compositor: Hyprland v: 0.56.2 driver: X: loaded: amdgpu
    unloaded: modesetting alternate: fbdev,vesa dri: radeonsi gpu: amdgpu
    display-ID: 1
  Monitor-1: DP-2 model: OZDSP25PRO res: 1920x1080 dpi: 87 diag: 635mm (25")
  Monitor-2: HDMI-A-1 model: Lenovo P24h-2L res: 2560x1440 dpi: 123
    diag: 604mm (23.8")
  API: EGL v: 1.5 platforms: device: 0 drv: radeonsi device: 1 drv: swrast
    gbm: drv: radeonsi surfaceless: drv: radeonsi wayland: drv: radeonsi x11:
    drv: radeonsi
  API: OpenGL v: 4.6 vendor: amd mesa v: 26.1.6-arch3.1 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon RX 9060 XT (radeonsi gfx1200 ACO
    DRM 3.64 6.18.42-1-cachyos-lts) device-ID: 1002:7590
  API: Vulkan v: 1.4.357 surfaces: N/A device: 0 type: discrete-gpu
    driver: mesa radv device-ID: 1002:7590
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo gpu: lact x11: xprop,xrandr

I installed mouzi with shelly as an AppImage.

[hsr88]

The EGL_BAD_PARAMETER result shows that disabling compositing is not a usable workaround on your RDNA 4 / Mesa / Hyprland setup, so please don’t use that flag again.
Could you try one more comparison by launching the AppImage through XWayland?
GDK_BACKEND=x11 ./Mouzi_*.AppImage
Please also run the AppImage normally from the terminal:
./Mouzi_*.AppImage
Then open Settings and paste any warnings printed in the terminal at that moment.
Mouzi already disables WebKitGTK’s DMABUF renderer on Linux, so this appears to be a separate WebKitGTK/EGL rendering issue affecting this newer AMD and Wayland setup. If the XWayland test works, it will help narrow down the cause. I’ll keep the issue open while I look for a proper workaround.

[SoyRober]

I got the same exact result with both recommendations.

AppImage normally:
❯ ./Mouzi_0.1.5_amd64.AppImage \n Could not create default EGL display: EGL_BAD_PARAMETER. Aborting... Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

With x11:
❯ GDK_BACKEND=x11 ./Mouzi_*.AppImage \n Could not create default EGL display: EGL_BAD_PARAMETER. Aborting... Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

[hsr88]

Thanks for testing this, and sorry for the delayed response. This confirms that forcing XWayland does not help the same WebKitGTK/EGL initialization error occurs with both backends.
I noticed that the tested file is still Mouzi_0.1.5_amd64.AppImage. Could you please download the current 0.1.6 AppImage directly from GitHub Releases, rather than through Shelly, and confirm whether it produces the same result?
Version 0.1.6 does not contain a targeted fix for this issue, so I’m not assuming it will solve it. I just want to make sure further investigation is based on the current build.
If the problem remains, could you also share the output of:
pacman -Q webkit2gtk-4.1 gtk3 mesa
Please don’t use WEBKIT_DISABLE_COMPOSITING_MODE=1 again, as we already know it is not compatible with this setup. I’ll keep the issue open and investigate an application-side workaround or prepare a dedicated test build.

[SoyRober]

Exact same issue opening without shelly.

Forcing x11:
GDK_BACKEND=x11 ./Mouzi_*.AppImage
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...

GTK depen:
pacman -Q webkit2gtk-4.1 gtk3 mesa
webkit2gtk-4.1 2.52.6-1
gtk3 1:3.24.52-1.1
mesa 3:26.2.1-1

If you want me to test something send me a message

[Alexblaster31]

Close the app, then execute in shell:
LD_PRELOAD=/usr/lib64/libwayland-client.so.0 ./Mouzi_0.1.5_amd64.AppImage

^_^

[SoyRober]

My goat, my savior