You are not logged in.
I have the latest Arch version with Gnome 48.2 on Wayland. I use a Thinkpad X1 Carbon Gen 10 with a Intel Iris Xe Graphics GPU.
Several applications start and seem to work, but they are invisible. I only see the icon.
I first had that problem with Bitwarden, but I could solve that like this:
echo '--ozone-platform=wayland' > ~/.config/electron-flags.confBut I also have this problem with Spotify and PhpStorm. In PhpStorm I can see the splash screen, but the there is a window to accept the license agreement that I can not see.
The windows are in the list when using alt-tab, but there is nothing to see.
Any idea what could cause this?
Update:
I solved spotify with these settings in ~/.config/spotify-launcher.conf
[spotify]
extra_arguments = ["--enable-features=UseOzonePlatform", "--ozone-platform=wayland"]I fixed PhpStorn with a vm option:
-Dawt.toolkit.name=WLToolkitBut the easiest solution is to just install XWayland and restart Gnome.
sudo pacman -Suy extra/xorg-xwaylandLast edited by roel4d (2025-06-03 23:09:44)
Offline
Online
I think it is a different problem. I have to force wayland in some application that try to use X11? I don't have X11 or XWayland installed.
I got most applications working for now. Thanks.
Offline
You're solving stuff by forcing those clients to use the native Wayland backend.
What do you think they've been using before? Nurses?
Online
Gnome and Chromium worked without any special settings. I assumed Chromium based applications would do the same or at least give a simple error message.
Offline
https://curiumsolutions.com/wp-content/ … Assume.jpg
The wiki shows how to check whether those are xwayland clients…
Though actually, https://wiki.archlinux.org/title/Chromi … er_Wayland
Online
I think this is the problem we're facing.
https://gitlab.gnome.org/GNOME/mutter/-/issues/4133
`killall mutter-x11-frames && /usr/lib/mutter-x11-frames &`
is a workaround provided by Michel Danzer on that issue.
Offline
Yup, it's linked in w/ the bugs referenced in the other thread and afaiu upstream has already confirmed that the same patch fixes it (there's an open question because of the slightly different symptoms, but transparent = black = 0 if you ignore the alpha channel, so w/o any deeper insight I could imagine that there's some optimized path that operates on 24bit only until the first actual ARGB drawable shows up)
Online