Modal dialogs are inivisble (arch, wayland, v2.8.0)

[jaseg]

Description of the bug

Since updating to v2.8.0, whenever PrusaSlicer shows a modal dialog, the main window looses focus, but the dialog is never shown on screen. I can still interact with the dialog through the keyboard (like tab, enter, Alt+F4).

Project file & How to reproduce

Run PrusaSlicer v2.8.0 on archlinux, under wayland. I was able to reproduce the issue with both arch's native package, and with the the flatpak from flathub.

Checklist of files included above

• [x] Project file
• [x] Screenshot

(no project file b/c the issue happens right after opening PrusaSlicer)

Version of PrusaSlicer

2.8.0-linux

Operating system

Arch Linux, running gnome on wayland

Printer model

I was only using PrusaSlicer for STL manipulation

[eliliam]

Can confirm same issue, found when trying to log in via top right "Log In" button. Also running Arch, however I am using Xorg/X11. This is running the latest 2.8.0 installed via the AUR. Same behavior using the AppImage however.

After clicking "Log In"

After force closing the blank modal

Relevant logs that appear when clicking "Log In" (captured by starting Prusa Slicer with the --loglevel 5 argument)

04:28:36 PM: Debug: window wxTreeCtrl@0x5f99982ca1f0 ("treeCtrl") lost focus even though it didn't have it
04:28:36 PM: Debug: window wxTreeCtrl@0x5f99982ca1f0 ("treeCtrl") lost focus even though it didn't have it
04:28:36 PM: Debug: window wxTreeCtrl@0x5f99982ca1f0 ("treeCtrl") lost focus even though it didn't have it
04:28:36 PM: Debug: window wxTreeCtrl@0x5f99982ca1f0 ("treeCtrl") lost focus even though it didn't have it
04:28:36 PM: Debug: window wxTreeCtrl@0x5f99982ca1f0 ("treeCtrl") lost focus even though it didn't have it
04:28:36 PM: Debug: window wxTreeCtrl@0x5f99982ca1f0 ("treeCtrl") lost focus even though it didn't have it
04:28:36 PM: Debug: window wxTreeCtrl@0x5f99982ca1f0 ("treeCtrl") lost focus even though it didn't have it
04:28:36 PM: Debug: window wxTreeCtrl@0x5f99982ca1f0 ("treeCtrl") lost focus even though it didn't have it
04:28:36 PM: Debug: window wxTreeCtrl@0x5f99982ca1f0 ("treeCtrl") lost focus even though it didn't have it
04:28:36 PM: Debug: window wxTreeCtrl@0x5f99982ca1f0 ("treeCtrl") lost focus even though it didn't have it
04:28:36 PM: Debug: window wxTreeCtrl@0x5f99982ca1f0 ("treeCtrl") lost focus even though it didn't have it
[2024-07-02 16:28:37.703232] [0x00007d5ccf81a200] [info]    code verifier: m1RAIjE0B82L3mfQqB5Nti7b75PMgoQrg51TVVJX
[2024-07-02 16:28:37.703244] [0x00007d5ccf81a200] [info]    code challenge: yYel3_q3hQ7dUuCaSbggRmzraOQvmoqIIiB6GaDS340
[2024-07-02 16:28:37.708562] [0x00007d5ccf81a200] [info]    open login browser: https://account.prusa3d.com/o/[REDACTED URL]
src/nv_gbm.c:300: GBM-DRV error (nv_gbm_create_device_native): nv_common_gbm_create_device failed (ret=-1)

Edit: added images

[jaseg]

I just observed the same bug (main window focused, but modal dialogs invisible) in Thunderbird on the same computer. So maybe this is an upstream bug?

[jaseg]

@eliliam Your screenshots look like a slightly different issue: On my machine, the modal dialogs are never even shown. I don't even see a blank window. The only trace of them existing that I could find is that gnome's screenshot tool when asked to screenshot a window reserves an empty space for the invisible dialog.

[vivienm]

@eliliam Got the same problem as you, with the additional log message

Failed to get GBM device

When PrusaSlicer is started with the environment variable WEBKIT_DISABLE_COMPOSITING_MODE=1, the log in dialog shows up and is correctly displayed.

Using Arch + Sway + Nvidia.

[jaseg]

It seems we're talking about two distinct bugs after all. @vivienm the behavior I observed where the dialogs don't appear at all does not change with WEBKIT_DISABLE_COMPOSITING_MODE=1.

[vivienm]

Interesting. Probably worth opening a second issue then, but I can't do it ATM (at work).

[lordekeen]

Works with WEBKIT_DISABLE_DMABUF_RENDERER=1 the same thing happens with Orcaslicer, which is odd.

[eliliam]

the same thing happens with Orcaslicer, which is odd.

@lordekeen isn't Orcaslicer based on Prusaslicer?

[lordekeen]

the same thing happens with Orcaslicer, which is odd.

@lordekeen isn't Orcaslicer based on Prusaslicer?

It is based on Bambu Studio which is based on Prusaslicer, but i didnt think they would all have the same problem with their UI

[eliliam]

i didnt think they would all have the same problem with their UI

Since they're all based on Prusaslicer it makes sense why they'd have similar issues, especially since this appears to be an underlying deeper UI issue instead of an issue with a specific feature, as I would guess that all three slicers share most of the core UI framework.