https://bugs.kde.org/show_bug.cgi?id=403243
Wolfgang Bauer <wba...@tmo.at> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wba...@tmo.at
--- Comment #15 from Wolfgang Bauer <wba...@tmo.at> ---
This seems to happen quite reliable (though not always) here on my system (with
Qt 5.12.1, Plasma 5.15.2, KF 5.55.0).
Here's the xprop output from me in case ksmserver-logout-greeter shows up in
the taskbar:
_NET_WM_ICON_GEOMETRY(CARDINAL) = 710, 995, 190, 28
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_MINIMIZE,
_NET_WM_ACTION_FULLSCREEN, _NET_WM_ACTION_CHANGE_DESKTOP, _NET_WM_ACTION_CLOSE
_KDE_NET_WM_FRAME_STRUT(CARDINAL) = 0, 0, 0, 0
_NET_FRAME_EXTENTS(CARDINAL) = 0, 0, 0, 0
_NET_WM_DESKTOP(CARDINAL) = 0
_NET_WM_USER_TIME(CARDINAL) = 15191022
_KDE_NET_WM_ACTIVITIES(STRING) = "eeb0c209-818e-4b8a-9b51-7c5793d513ae"
WM_STATE(WM_STATE):
window state: Normal
icon window: 0x0
_NET_WM_STATE(ATOM) = _NET_WM_STATE_MAXIMIZED_VERT,
_NET_WM_STATE_MAXIMIZED_HORZ, _NET_WM_STATE_FULLSCREEN
_KDE_NET_WM_BACKGROUND_CONTRAST_REGION(_KDE_NET_WM_BACKGROUND_CONTRAST_REGION)
= 0x3e3e9be8, 0xbc924bc8, 0xbc924bc8, 0x0, 0xbd761317, 0x3e13609b, 0xbd761317,
0x0, 0xbbc6bb3c, 0xbbc6bb3c, 0x3e4aaf87, 0x0, 0x3db851ee, 0x3db851ee,
0x3db851ec, 0x3f800000
WM_WINDOW_ROLE(STRING) = "logoutdialog"
_KDE_NET_WM_BLUR_BEHIND_REGION(CARDINAL) =
XdndAware(ATOM) = BITMAP
WM_NAME(STRING) =
_NET_WM_NAME(UTF8_STRING) = "ksmserver-logout-greeter"
_MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x3, 0x3e, 0x7e, 0x0, 0x0
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL
_KDE_NET_WM_USER_CREATION_TIME(CARDINAL) = 15180327
_XEMBED_INFO(_XEMBED_INFO) = 0x0, 0x1
WM_CLIENT_LEADER(WINDOW): window id # 0x700000d
WM_HINTS(WM_HINTS):
Client accepts input or input focus: True
Initial state is Normal State.
window id # of group leader: 0x700000d
WM_CLIENT_MACHINE(STRING) = "linux-lf90.site"
_NET_WM_PID(CARDINAL) = 24179
_NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 117440524
WM_CLASS(STRING) = "ksmserver", "ksmserver"
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: 0, 0
user specified size: 1280 by 1024
window gravity: Static
I notice in particular that _NET_WM_STATE does *not* include
_NET_WM_STATE_SKIP_TASKBAR and _NET_WM_STATE_SKIP_PAGER when it happens.
And that's actually the only difference, except that _NET_WM_ICON_GEOMETRY is
additionally set in the buggy case whereas it is not when it's working (no idea
if that is relevant though).
--
You are receiving this mail because:
You are watching all bug changes.
