doing a windowunmap followed by a windowmap creates an extra window about xdotool HOT 4 OPEN

Can you get me info about that black window? Run each of these commands, then click on the window, then put the output in a gist or pastebin:

• xwininfo
• xprop

from xdotool.

Hi Jordan,

This is the info you requested.

Cheers,

Dolf.

xwininfo: Window id: 0x2e00001 "Terminal"

Absolute upper-left X: 1
Absolute upper-left Y: 91
Relative upper-left X: 10
Relative upper-left Y: 40
Width: 10
Height: 10
Depth: 24
Visual: 0x21
Visual Class: TrueColor
Border width: 0
Class: InputOutput
Colormap: 0x20 (installed)
Bit Gravity State: NorthWestGravity
Window Gravity State: NorthWestGravity
Backing Store State: NotUseful
Save Under State: no
Map State: IsViewable
Override Redirect State: no
Corners: +1+91 -3509+91 -3509-979 +1-979
-geometry 10x10+-9+51

_NET_WM_STATE(ATOM) = _NET_WM_STATE_FOCUSED
_NET_WM_DESKTOP(CARDINAL) = 0
XKLAVIER_STATE(INTEGER) = 0, 1
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x0
_NET_FRAME_EXTENTS(CARDINAL) = 1, 1, 32, 1
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE, _NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_SHADE, _NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_MAXIMIZE_VERT, _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE, _NET_WM_ACTION_ABOVE, _NET_WM_ACTION_BELOW
SM_CLIENT_ID(STRING) = "10b0c975a9293ba586135487701930248700000027560073"
_NET_STARTUP_ID(UTF8_STRING) = "gnome-shell-2859-dolfdesktop-gnome-terminal-3_TIME5283069"
WM_CLASS(STRING) = "gnome-terminal", "Gnome-terminal"
WM_COMMAND(STRING) = { "gnome-terminal" }
_NET_WM_USER_TIME_WINDOW(WINDOW): window id # 0x2e00002
WM_CLIENT_LEADER(WINDOW): window id # 0x2e00001
_NET_WM_PID(CARDINAL) = 4993
WM_LOCALE_NAME(STRING) = "en_US.UTF-8"
WM_CLIENT_MACHINE(STRING) = "dolfdesktop"
WM_NORMAL_HINTS(WM_SIZE_HINTS):
program specified size: 10 by 10
WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING
WM_ICON_NAME(STRING) = "gnome-terminal"
_NET_WM_ICON_NAME(UTF8_STRING) = "gnome-terminal"
WM_NAME(STRING) = "Terminal"
_NET_WM_NAME(UTF8_STRING) = "Terminal"

----- Original Message -----

From: "Jordan Sissel" [email protected]
To: "jordansissel/xdotool" [email protected]
Cc: "dolfandringa" [email protected]
Sent: Thursday, 6 December, 2012 10:57:45 AM
Subject: Re: [xdotool] doing a windowunmap followed by a windowmap creates an extra window (#13)

Can you get me info about that black window? Run each of these commands, then click on the window, then put the output in a gist or pastebin:

* xwininfo 
* xprop 

—
Reply to this email directly or view it on GitHub .

from xdotool.

This little 10x10 window sounds liek some kind of utility window that GTK or gnome-terminal uses to do things behind the scenes and is never intended to be mapped, and you are mapping it (making it visible) with your search parameters.

from xdotool.

I'm using Ubuntu 20.04, with xfce4 (specifically 4.14) as my window manager, and I can confirm that this is periodically happening to me. I use xdotool along with xfce4 hotkeys to switch between different windows. Occasionally I'm finding that new "visible" windows are being created. The result is that my hotkeys don't behave quite the way they should.

I've noticed that the extra "visible" windows are created when I start a drag and drop operation. The windows are showing up as visible, even though they've never been shown. My testing shows that, so long as I do not raise the invisible windows, they do not have the WM_STATE prop set.

I believe this issue can be fixed by having "onlyvisible" include a secondary test to see if WM_STATE is present. That will prevent %@ from truly mapping a window that it seems should not be mapped.

from xdotool.