You are not logged in.
After upgrading and switching back and forth between Wayland and X11 in GNOME I can no longer open several applications such as GIMP, Libreoffice, Zotero, etc under Wayland. Similar to this issue, but in my case downgrading mutter doesn't fix the problem.
The Xorg session works as normal (but I need to use Wayland). I have checked journalct, dmesg and the Xorg log. There's nothing in there. It's as though applications started opening but nothing is rendered. Same behavior and no error messages when starting from the terminal.
I have also played with the environment variable GDK_BACKEND without luck.
# pacman -Q linux xorg-xwayland gnome-shell mutter gdm gtk4 gtk3 gtk2
linux 6.9.7.arch1-1
xorg-xwayland 24.1.0-1
gnome-shell 1:46.3.1-1
mutter 46.3-1
gdm 46.2-1
gtk4 1:4.14.4-1
gtk3 1:3.24.42-1
gtk2 2.24.33-4
Hardware and drivers (I'm using the modesetting 2D driver included in xorg-server, no xf86-video-intel):
# lspci -v | grep -A1 -e VGA -e 3D
00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P GT2 [Iris Xe Graphics] (rev 0c) (prog-if 00 [VGA controller])# pacman -Qs xf86
local/libxxf86vm 1.1.5-1
local/xf86-input-libinput 1.4.0-1 (xorg-drivers)# pacman -Q mesa
mesa 1:24.1.2-1
Last edited by isacdaavid (2024-07-10 15:58:15)
Offline
Just to confirm, the processes are running, but no window is shown if the application uses GTK2 or GTK3
# ps -fea | grep -E '(hexchat|emacs|zotero)' | grep -v grep
isaac 14835 13893 0 08:24 ? 00:00:00 /usr/lib/zotero/zotero-bin -app /usr/lib/zotero/application.ini -url
isaac 14841 14835 0 08:24 ? 00:00:00 /usr/lib/zotero/zotero-bin -app /usr/lib/zotero/application.ini -url
isaac 14903 13893 0 08:25 ? 00:00:00 /usr/bin/emacs
isaac 15040 13893 0 08:26 ? 00:00:00 /usr/bin/hexchat --existing
Offline
Same w/ xterm but not w/ https://archlinux.org/packages/extra/x8 … s-wayland/ resp. "GDK_BACKEND=x11 gtk3-demo" behaves differently than "GDK_BACKEND=wayland gtk3-demo"?
(Basically whether this is actually an XWayland situation)
Offline
"GDK_BACKEND=x11 gtk3-demo" behaves differently than "GDK_BACKEND=wayland gtk3-demo"?
(Basically whether this is actually an XWayland situation)
"GDK_BACKEND=wayland gtk3-demo" works.
"GDK_BACKEND=x11 gtk3-demo" doesn't. The process is there, but no window comes up.
$ GDK_BACKEND=x11 gtk3-demo
^C
$ GDK_BACKEND=wayland gtk3-demo
$ echo $?
0
$ GDK_BACKEND=x11 gtk3-demo
^Z
[1]+ Stopped GDK_BACKEND=x11 gtk3-demo
$ ps -fea | grep gtk3-demo | grep -v grep
isaac 9310 9129 0 11:33 pts/1 00:00:00 gtk3-demo
$ fg
GDK_BACKEND=x11 gtk3-demo
^C
Offline
Symptoms and context yell that this is the same as the other thread - are you sure the downgrade was successfully applied?
Offline
Symptoms and context yell that this is the same as the other thread - are you sure the downgrade was successfully applied?
I am. I have gone through the last 3 or 4 versions of mutter in my pacman cache, both alone and together with downgrades of gnome-shell, gdm, gtk{2,3,4}.
Offline
As long as you're running the compromised version of mutter there's probably no point in further investigation, but if it doesn't go away w/ a downgrade or the fixing update you'd check
1. is gtk3-demo still affected
2. is a new user account affected
3. does it go away if you move away eg. your gimp config (gtk3-demo is no longer affected after the downgrade, to see whether it's the client or the mutter configuration)
The upstream bug suggests that using the applicationn switcher (or maybe resizing the window?) mitigates the situation?
Offline
mutter 46.3.1 was released now and includes the fix for Xwayland. Maybe this solves also this problem?
Offline
Fresh user profiles were also affected.
In any case, I worked around this with a fresh install. That means there probably was some weird interaction between my global configuration and gnome software going on, although it's hard to tell what the exact problem was.
Last edited by isacdaavid (2024-07-10 15:57:59)
Offline