Android Virtual Device, how to add to blacklist?

[abenz1267]

Hi,

i can't find out how to add an emulated device from Android Studio to the blacklist, as the window doesn't have a class name.

Any suggestion?

It's flickering a lot when using kwin tiling.

Regards

[faho]

as the window doesn't have a class name.

Wait, what?

What does xprop say on the window?

[laloch]

@faho: @abenz1267 is right. This is what xprop says here:

_NET_WM_ICON_GEOMETRY(CARDINAL) = 3805, 432, 33, 39
_KDE_NET_WM_ACTIVITIES(STRING) = "00000000-0000-0000-0000-000000000000"
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_MOVE, _NET_WM_ACTION_RESIZE, _NET_WM_ACTION_MINIMIZE, _NET_WM_ACTION_MAXIMIZE_VERT, _NET_WM_ACTION_MAXIMIZE_HORZ, _NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE
_NET_WM_DESKTOP(CARDINAL) = 3
WM_STATE(WM_STATE):
                window state: Normal
                icon window: 0x0
_NET_WM_STATE(ATOM) = _NET_WM_STATE_BELOW
_NET_WM_USER_TIME(CARDINAL) = 98168790
_NET_WM_ICON_NAME(UTF8_STRING) = 
_NET_WM_ICON(CARDINAL) =        Icon (128 x 128):
...
XdndAware(ATOM) = BITMAP
_NET_WM_NAME(UTF8_STRING) = "Android Emulator - Pixel_2_API_25:5554"
_MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x2, 0x1, 0x0, 0x0, 0x0
_NET_WM_WINDOW_TYPE(ATOM) = _KDE_NET_WM_WINDOW_TYPE_OVERRIDE, _NET_WM_WINDOW_TYPE_NORMAL
_KDE_NET_WM_USER_CREATION_TIME(CARDINAL) = 98021079
_XEMBED_INFO(_XEMBED_INFO) = 0x0, 0x1
WM_CLIENT_LEADER(WINDOW): window id # 0x7a00005
WM_HINTS(WM_HINTS):
                Client accepts input or input focus: True
                window id # of group leader: 0x7a00005
WM_CLIENT_MACHINE(STRING) = "str"
_NET_WM_PID(CARDINAL) = 705733
_NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 127926276
WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING, _NET_WM_SYNC_REQUEST
WM_NORMAL_HINTS(WM_SIZE_HINTS):
                user specified location: 1229, 1
                user specified size: 647 by 1197
                program specified minimum size: 200 by 200
                window gravity: Static

No WM_CLASS at all. Fascinating... :/

[faho]

No WM_CLASS at all. Fascinating... :/

Wait what?

Okay, yeah, I think we should just be able to get by if we ignore everything with an empty class.

[laloch]

I'd say that all we can do about it is to blacklist all clients with empty or no WM_CLASS.

[faho]

Okay @abenz1267, please try cf264e9 - I couldn't actually test it.

[laloch]

@faho, I did already test the same. Works just fine for me.

[abenz1267]

can confirm, works perfectly.