System: Fedora Linux 37 (Workstation Edition)
Kernel: Linux 6.2.8-200.fc37.x86_64
GNOME Shell: 43.3
As the topic states, neither of those commands can find the id of an opened terminal window.
I have two terminals opened, but according to those commands they are not there:
wmctrl -l
0x00800006 0 ITx220 1yZmw0-uswmWXZ9Hd7VMzavnFNtqhW0m5 [Zablokowana] - KeePassXC
0x02200003 0 ITx220 Title: Prompt Creator Assistance. — Osobisty — Microsoft Edge
0x03000003 0 ITx220 testclose.py - myscripts (Workspace) - Visual Studio Code
0x00e0000a 0 ITx220 #welcome | GNOME - Discord
xdotool search --shell --name ^.Terminal. $
WINDOWS=()
Am I missing something?
fmuellner
(Florian Müllner)
April 5, 2023, 2:02am
2
You are probably using the (default) wayland session. Both xdotool
and wmctl
are X11 tools, so they don’t work with native wayland clients.
Oh. I see. Are there xdtool
/ wmctl
like tools for wayland? Also, why do both of those tools recognize some windows and some not? If they were not supposed to work with Wayland how come is that possible?
ebassi
(Emmanuele Bassi)
April 5, 2023, 4:56pm
4
Because those applications likely use X11, via XWayland, and so they appear as X11 clients to X11 applications. GNOME Terminal works as a Wayland client, so it does not appear as an X11 client to other X11 clients.
fmuellner
(Florian Müllner)
April 5, 2023, 4:57pm
5
Not really. Not giving a client access to all other clients that are connected to the same display server is one of the selling points of wayland.
On GNOME, you can use extensions to hook into window management.
Because you can still run X11 clients in a wayland session, and those are visible to other X11 clients (like those tools).
system
(system)
Closed
May 20, 2023, 4:57pm
6
This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.