https://bugs.kde.org/show_bug.cgi?id=441005
Ismael Asensio <isma...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|kwin can't read WM_CLASS |kwin doesn't read WM_CLASS
|while xprop can |with a single string
| |(bitwig studio)
Ever confirmed|0 |1
Status|REPORTED |CONFIRMED
--- Comment #5 from Ismael Asensio <isma...@gmail.com> ---
Can reproduce.
The information we retrieve from the window has in fact the relevant fields
empty:
> qdbus org.kde.KWin /KWin org.kde.KWin.queryWindowInfo
caption: Bitwig Studio - New 1
clientMachine: localhost
resourceClass:
resourceName:
. . .
Investigating into the issue, while xprop reports a string for WM_CLASS, the
application is not fully following the X.org specification, as `WM_CLASS`
should have two null-terminated strings, instead of just one, the `instance`
and the `class` (excerpt of the spec here:
https://unix.stackexchange.com/questions/494169/wm-class-vs-wm-instance).
This is probably what's causing the issue. I haven't still find where the
information is loaded to see if we could maybe use that single string.
It also happens on Wayland session, since it loads via XWayland.
--
You are receiving this mail because:
You are watching all bug changes.
