Re: [qubes-devel] Window border colors

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-07-26 14:52, Manuel Amador (Rudd-O) wrote:
> Hello. I just did an update, rebooted, and now my window borders do not
> have the VM's colors. The prefix on the window title is correct tho.
>
>
> What gives?
>
>

That sounds very strange. Have you done any kind of customization or made any
changes from the defaults? For example, have you changed the colors or changed
the window border style?

Also, are you using KDE or XFCE? R3.1 or R3.2-rc1?

[Moving to qubes-users.]

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXl+AUAAoJENtN07w5UDAwZfsP/3EvTm3JbXR3VHaLkyqsIiy2
8X0B5EIclOH1TuCAMhRfaV6PV/CxHzn1HBjC/53Fav6p6D8GpV+F9Y2WrcmFaBry
oPgbyfc1NXlyZa2y9v9Y+qJEMvii+fQlaD1UFm/Xmyiph7Wet8wrRHwMJ8KAWuJY
Y9epJbI7n76wrR9zsUWBFgm7VqtBY5kb/TbbT8Ev+aimTDp0btJJ7SgMA3AOXMvp
N9b7zJlBD010WL8dG2n3V9qosUaVJpwy8aSP0fbUE3knYVuGviqk0NC8r0Bscqng
KGvIblhhN2Ul91xp9iW4WqR+COBJjliPHPMJRbs6JhJ93a9b0xLw3GsplDGvcwV4
Hd+2JThlnuI9j/5KjxDwt3h3yQ7vV19NPfj/25sK9GANIS7HxPIwh8JaFPJkiuuI
pQfxYehxBRRs8ujrLt4hQ8CEf3hLlcs8f3SoOb7MOQGgbfLzlSb6IjW9aiO+xyNQ
n1K8xfK1v9xTJVFD2ao1Qi8PaEmMMtmO/S7G0v5pw7F8cp9MtRvjN0JCeoiGSMWM
KDkPNgDUi0wYwCMA0EVNSgSh1nJ9f68iJj/5/cFQaolutftROUT96QM1ls1pS38l
UWZJiFJ8Wzr35WX7DEOQ9kVfMnaIKU93FUpAC/4nDFLq9trsMdsINvTqiE07374B
PcrEkyvF18DYqX707LbL
=Gomr
-----END PGP SIGNATURE-----

[45fv2s+682...@guerrillamail.com]

Same problem here. Window border colors are no longer working since today's update on Qubes 3.2-rc1.
How can one restore it back to its original working state?
Since this update every time a command is launched, when the respective AppVM is down, the window is not displayed and the AppVm shows as being in a transient state (for instance, when launching the gnome-terminal, the terminal console only gets displayed after another instance of gnome-terminal is launched, then two terminal console windows are displayed)
Something definitively went wrong with this update...

----
Sent using GuerrillaMail.com
Block or report abuse: https://www.guerrillamail.com/abuse/?a=UFR2AB5NVqcQmh2U93EQdRjCStifx8dDiadNcQ%3D%3D

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 2016-07-26 15:35, 45fv2s+682x23ntdh9z4 via qubes-users wrote:
> Same problem here. Window border colors are no longer working since today's
> update on Qubes 3.2-rc1. How can one restore it back to its original
> working state? Since this update every time a command is launched, when the
> respective AppVM is down, the window is not displayed and the AppVm shows
> as being in a transient state (for instance, when launching the
> gnome-terminal, the terminal console only gets displayed after another
> instance of gnome-terminal is launched, then two terminal console windows
> are displayed) Something definitively went wrong with this update...
>

Tracking:

https://github.com/QubesOS/qubes-issues/issues/2201

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXl+ukAAoJENtN07w5UDAwWpEP/A19YGmaSDBscBwdiJTrwKYJ
uVONeS+KXOiVwCyi6DVd5QWeyFN6qOlAbCTJa7hhKh1KAW8dxUOR4IvgtD06LwCv
9j0pUtC66F70myo03W970oiwH5h0wFqMwbBmVxcTnWdFiJxGKexROxupJ12/W64M
6h90KzqGB4LRUenwIFr5qFe01mE/enNSzHzf8sVdblpEPInwlVNGVXSfrLrSc8mp
+g4Z29nnqP8bJb80bn0P+J7+kpHLCh90La2Iidhf8eWNLrjOXQdz7FkjEf9ZU+7X
TW2hxZ4l8zHpbLa84+VH6xEgJFrenz9FlDT9hQlo3iYWVr6z51NI9Jwrfd0zC52J
WOkmPY/FOWeaXV6nf10BOpgR6P1DFrPXgdckOgkXGTaM3VUeq70T0u4k3J8jSG9m
+sHIhyjWcDqJ5sgy6I++W6dYC4fp27r6IaZr+Y81yDKXkSoDheq8XiaNsJ8w29uT
X3ernQrdAqUG/umq3CiUp2W7s15loFQrWragyRrnWyjkDSx598RWIsl9MJ/MpcNe
ajjp7GnSbKht01N0iAM4yXvT7dIs0AvZ+4vhm7PE1u64EdHoLt/oAc6oxQ2l+NYA
AludozKgzxWZhdJrPxjYMVnU7nNUBs47f6FN+xTzBM4mm3/zc3RJKoYJTLkOj4xs
+11W4iQD/JvQ62b37ObA
=uvUq
-----END PGP SIGNATURE-----

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Tue, Jul 26, 2016 at 03:11:33PM -0700, Andrew David Wong wrote:
> On 2016-07-26 14:52, Manuel Amador (Rudd-O) wrote:
> > Hello. I just did an update, rebooted, and now my window borders do not
> > have the VM's colors. The prefix on the window title is correct tho.
> >
> >
> > What gives?
> >
> >
>
> That sounds very strange. Have you done any kind of customization or made any
> changes from the defaults? For example, have you changed the colors or changed
> the window border style?
>
> Also, are you using KDE or XFCE? R3.1 or R3.2-rc1?

Those are important questions.

In addition, please provide version of qubes-gui-dom0 package. And check
properties of some VM window using xprop from dom0 (call xprop, then
click on some VM window). Especially those properties:
_QUBES_LABEL
_QUBES_LABEL_COLOR
_KDE_NET_WM_COLOR_SCHEME

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXl/JjAAoJENuP0xzK19cskcoH/3M2R7JHpTfeBpDMR0GH0ePj
Y7KKa92693Yeo9ymfQ7pPkXYVI9hOOS3enAhjga+cv5n8b6pzyyMBXlA9rjs+kWs
YzMrZFRg02pS1MRfB+4wrObetYbvkF5THXbbJ6dpb9q8Z+E4Q4YR9vci17i9lUkE
gAmIxNw2Orwi0cJ09Id0k0GMhnu7HrHW0sjQ3Bl5CX1QWQ5lbm5BMxbViN9yOzgU
WgzQMi6SD9NxLe56zTA6kOFJnXUwwztIywnseD1Jpa2jGzjw6D13QmTrehpg5fpS
aDuMARGBN1NgQaiztmtO1lc1cd3OzRqkIYl7ejxZ9khjx0aQh0Oah+LMqBeg5EM=
=9Lw3
-----END PGP SIGNATURE-----

[Jeremy Rand]

Marek Marczykowski-Górecki:

> On Tue, Jul 26, 2016 at 03:11:33PM -0700, Andrew David Wong wrote:
>> On 2016-07-26 14:52, Manuel Amador (Rudd-O) wrote:
>>> Hello. I just did an update, rebooted, and now my window borders do not
>>> have the VM's colors. The prefix on the window title is correct tho.
>>>
>>>
>>> What gives?
>>>
>>>
>
>> That sounds very strange. Have you done any kind of customization or made any
>> changes from the defaults? For example, have you changed the colors or changed
>> the window border style?
>
>> Also, are you using KDE or XFCE? R3.1 or R3.2-rc1?
>
> Those are important questions.
>
> In addition, please provide version of qubes-gui-dom0 package. And check
> properties of some VM window using xprop from dom0 (call xprop, then
> click on some VM window). Especially those properties:
> _QUBES_LABEL
> _QUBES_LABEL_COLOR
> _KDE_NET_WM_COLOR_SCHEME
>
>

Same thing has happened to me.

No customizations have been done. I initially thought it might be due
to customizations, so I reinstalled Qubes from scratch, did a
qubes-dom0-update, and rebooted, and it happened. So definitely not due
to customizations.

All the windows now appear to have the window border coloring that is
normally associated with dom0 (gray when not in focus, cyan when in
focus). Also interestingly, the icon of the Launcher in the Panel has
disappeared and became solid white. (I was able to workaround it by
right-clicking it, and in the settings dialog manually choosing an icon
from the list.) In addition, there is now an odd icon on the left side
of every window title bar (just to the right of the application icon)
that I don't recall ever being there before; it looks like a 1-pixel
thick square with the corner pixels removed. (I can provide a
screenshot if you need it.)

KDE on 3.2rc1.

"dnf info qubes-gui-dom0" in dom0 shows version 3.2.1.

I did the xprop you requested, and clicked on the fedora-23 TemplateVM.

_QUBES_LABEL is 8.
_KDE_NET_WM_COLOR_SCHEME is
"/home/jeremy/.local/share/qubes-kde/black.colors".

_QUBES_LABEL_COLOR does not show up in the xprop output at all.

Hope this helps in diagnosing.

Cheers,
-Jeremy Rand

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

This looks ok. I assume the file exists too.

> _QUBES_LABEL_COLOR does not show up in the xprop output at all.

This is also ok in qubes-gui-dom0 3.2.1.

> Hope this helps in diagnosing.

Try this:

Go to system settings -> Application Style -> Window Decorations. It
should be set to "Breeze". If it is set to "Plastik", it may be the
cause of the problems.

If this is the case, I think this may be related to KDE update done by
Fedora recently (a lot of kf5-* packages), so unrelated to
qubes-gui-dom0 version.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXmD46AAoJENuP0xzK19csPtgH/Anmul9RmxX/prK2j1q1iyMt
43aLfNXcLjsQBh45pxi94HE/eYGnuZC/cuFZs5aTFJwVfigk3Xir5F/+2h573kTX
YNceUj9ZghLqigu7gsJQJAZ4O5Y6Nd43h2l6/6tcdsj2oSjExT0/uifI0FBJ8LU3
doE/TT1WNixZ9vKf5js9RU2GxsC5Gg5l+Qasp6dHjo0IaJQpYYMr5BmYAJtSXDbG
2BTrWo1YodPTgLIZiwmdgCe8zGUQ+F0eM/9TVin1+kEAF9KNI7WCKI3GLs3zr5eZ
TmbzOCuupAQS2FFKQE2T9Sv5O2mCpBaFi79YOXavZeL+wDioqD3FJ6o4Fr/kY9c=
=3Ts+
-----END PGP SIGNATURE-----

[Jeremy Rand]

Jeremy Rand:

Other interesting note. When I right-click the title bar of a window,
the context menu's background color is still correct (e.g. for a window
that is supposed to be red, the context menu's background is
red-tinged). So, at least some of the coloring information is still
getting to KDE.

-Jeremy

[Jeremy Rand]

Marek Marczykowski-Górecki:

Yes! It was set to Plastik. Changing it to Breeze and clicking Apply
instantly fixed the issues. (Well, I can't test whether it fixed the
icon of the launcher, because I've already done the workaround that I
described previously. But everything else is fixed now.)

Thank you Marek!

-Jeremy

[45in10+d44...@guerrillamail.com]

The proposed workaround solved part of the issue, however I'm still facing issues with application windows that are not displayed as outlined on my previous comment:

Since this update every time a command is launched, when the respective AppVM is down, the window is not displayed and the AppVm shows as being in a transient state (for instance, when launching the gnome-terminal, the terminal console only gets displayed after another instance of gnome-terminal is launched, then two terminal console windows are displayed)

----

[Manuel Amador (Rudd-O)]

On 07/26/2016 10:11 PM, Andrew David Wong wrote:
> On 2016-07-26 14:52, Manuel Amador (Rudd-O) wrote:
> > Hello. I just did an update, rebooted, and now my window borders do
> not
> > have the VM's colors. The prefix on the window title is correct tho.
>
>
> > What gives?
>
>
>
> That sounds very strange. Have you done any kind of customization or
> made any
> changes from the defaults? For example, have you changed the colors or
> changed
> the window border style?

Nope.

KDE. R3.2.

--
Rudd-O
http://rudd-o.com/

[Manuel Amador (Rudd-O)]

On 07/26/2016 11:29 PM, Marek Marczykowski-Górecki wrote:
> On Tue, Jul 26, 2016 at 03:11:33PM -0700, Andrew David Wong wrote:
> > On 2016-07-26 14:52, Manuel Amador (Rudd-O) wrote:
> >> Hello. I just did an update, rebooted, and now my window borders
> do not
> >> have the VM's colors. The prefix on the window title is correct tho.
> >>
> >>
> >> What gives?
> >>
> >>
>
> > That sounds very strange. Have you done any kind of customization or
> made any
> > changes from the defaults? For example, have you changed the colors
> or changed
> > the window border style?

No. Not willingly and probably not accidentally.

>
> > Also, are you using KDE or XFCE? R3.1 or R3.2-rc1?
>
> Those are important questions.
>
> In addition, please provide version of qubes-gui-dom0 package.

3.2.1-1.fc23.x86_64.

> And check
> properties of some VM window using xprop from dom0 (call xprop, then
> click on some VM window). Especially those properties:
> _QUBES_LABEL
> _QUBES_LABEL_COLOR
> _KDE_NET_WM_COLOR_SCHEME

_QUBES_LABEL(CARDINAL) = 6

_QUBES_LABEL_COLOR is absent

_KDE_NET_WM_COLOR_SCHEME(STRING) =
"/home/@user@/.local/share/qubes-kde/blue.colors"

Content of file:

---------------------------------
[Colors:Window]
BackgroundNormal=52,101,164

[WM]
activeBackground=52.101.164
inactiveBackground=26,50,82
---------------------------------

--
Rudd-O
http://rudd-o.com/

[Manuel Amador (Rudd-O)]

On 07/27/2016 04:53 AM, Marek Marczykowski-Górecki wrote:
>
> Go to system settings -> Application Style -> Window Decorations. It
> should be set to "Breeze". If it is set to "Plastik", it may be the
> cause of the problems.

Shit yo, for some reason my thing was set to Plastik, and I set it to
Breeze by hand, and that made the problem go away!

Thanks!>

--
Rudd-O
http://rudd-o.com/

[Jeremy Rand]

45in10+d44wd6z0yzqcg via qubes-users:

> The proposed workaround solved part of the issue, however I'm still facing issues with application windows that are not displayed as outlined on my previous comment:
>
> Since this update every time a command is launched, when the respective AppVM is down, the window is not displayed and the AppVm shows as being in a transient state (for instance, when launching the gnome-terminal, the terminal console only gets displayed after another instance of gnome-terminal is launched, then two terminal console windows are displayed)

I think this is an independent issue. It's been happening to me
intermittently for at least a week prior to the update that broke the
window border colors. In fact, I think it's been happening to me
intermittently since I started using 3.2rc1.

-Jeremy

[45iunz+bse...@guerrillamail.com]

It might be, although I've only noticed it after this upgrade and this is now happening all the time and not only intermittently. Fortunately enough this is only reproducible in KDE and not on XFCE, so possibly this could be something related to KDE.

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I think this is another instance of this:
https://github.com/QubesOS/qubes-issues/issues/2085

When it happen, check /var/log/qubes/guid.VMNAME.log.old for something
like:
XDestroyWindow 0x5e00005
ErrorHandler: BadWindow (invalid Window parameter)
Major opcode: 10 (X_UnmapWindow)
ResourceID: 0x5e00005
Failed serial number: 194
Current serial number: 197

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXmI3FAAoJENuP0xzK19cs5ZQIAJkHD5qYDcsNnDaKNlkgmlpN
aVAwNfRu81u3fmDs9tGsc2Mv0RgoCQ41ta9dFHpXI/CNu+d8qW1AikfGxHdNe1Vo
PNQHlHqCVeoMRxdgxI0mD0Ghzgio3jWL9O1OI/OnD33r+auCByyHe/XBBUdbTrVc
jGv44qHio/XIfEov2FV+6uBObWN6QKnSfgOzXrKO4j2C02dikXS+Npddj6X7D8p0
0QnlM3uXcCyoS7Sne5Yn2MoMjQUpTxRxXLk993wcyIBDcU2L5pu0ezAc59lRWPeW
FPFraUnXIF6SjGcl/Q9vkP4AszNaWolc3Pu29n+sOPhjORSasE9tP2xX0c8RDNY=
=aJvZ
-----END PGP SIGNATURE-----

[Jeremy Rand]

Marek Marczykowski-Górecki:

> On Wed, Jul 27, 2016 at 09:53:00AM +0000, Jeremy Rand wrote:
>> 45in10+d44wd6z0yzqcg via qubes-users:
>>> The proposed workaround solved part of the issue, however I'm still facing issues with application windows that are not displayed as outlined on my previous comment:
>>>
>>> Since this update every time a command is launched, when the respective AppVM is down, the window is not displayed and the AppVm shows as being in a transient state (for instance, when launching the gnome-terminal, the terminal console only gets displayed after another instance of gnome-terminal is launched, then two terminal console windows are displayed)
>
>> I think this is an independent issue. It's been happening to me
>> intermittently for at least a week prior to the update that broke the
>> window border colors. In fact, I think it's been happening to me
>> intermittently since I started using 3.2rc1.
>
> I think this is another instance of this:
> https://github.com/QubesOS/qubes-issues/issues/2085
>
> When it happen, check /var/log/qubes/guid.VMNAME.log.old for something
> like:
> XDestroyWindow 0x5e00005
> ErrorHandler: BadWindow (invalid Window parameter)
> Major opcode: 10 (X_UnmapWindow)
> ResourceID: 0x5e00005
> Failed serial number: 194
> Current serial number: 197
>
>

Hi Marek,

I was able to reproduce this today. The requested log file is pasted below:

Icon size: 128x128
invalid PMinSize for 0x7200004 (0/0)
invalid PMaxSize for 0x7200004 (0/0)
invalid PResizeInc for 0x7200004 (0/0)
invalid PBaseSize for 0x7200004 (0/0)
invalid PMinSize for 0x7200005 (0/0)
invalid PMaxSize for 0x7200005 (0/0)
invalid PResizeInc for 0x7200005 (0/0)
invalid PBaseSize for 0x7200005 (0/0)
invalid PMaxSize for 0x7200005 (0/0)
invalid PResizeInc for 0x7200005 (0/0)

ErrorHandler: BadWindow (invalid Window parameter)

Major opcode: 4 (X_DestroyWindow)
ResourceID: 0x7200005
Failed serial number: 144
Current serial number: 146

The affected AppVM in this case is a Whonix WS AppVM; the window being
opened was Konsole. This is on Qubes 3.2rc1 with KDE.

Hope this helps in diagnosing it.

Cheers,
-Jeremy Rand

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

What qubes-gui-dom0 package version do you have? The case with
X_DestroyWindow should be already fixed in version 3.2.3 (in testing
repository).

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJXmSA/AAoJENuP0xzK19csXKMH/RsZv6VyOgygZwEtvEvLb3Gk
oEMp2bwl9jIAsgsKiXlADpztEEz+dnz8yDl2SAuq5IKb01nLtnqVBDF1pz1YbeCJ
FggHmM0vTQa8SzZOAcNhbJunfFq1MrbjIyFJjGhqKybulMdF9fpnu/5Xhekyly+g
cYMjiSXIY8wjP/UejZt7h0x5q1bdy8/HYVSzxiEuXO6m+Eq29dk3zYjEnhNW0/AQ
JbVtf2oeWOMgrSYTfJ+y7ZHDjA2KBe1IIkLzhsQhzozR/h3n4rIF+asfTvMHRCw9
MXsV+lkJ6i20g0aHcDRZpbnAWBJ3sMybx/qRgud6wHZ/KbBnTIhsC6lFJbKh2Xc=
=Iyra
-----END PGP SIGNATURE-----

[Qubed One]

> Jeremy Rand:
>> Marek Marczykowski-Górecki:

>> Try this:
>>
>> Go to system settings -> Application Style -> Window Decorations. It
>> should be set to "Breeze". If it is set to "Plastik", it may be the
>> cause of the problems.
>>
>> If this is the case, I think this may be related to KDE update done by
>> Fedora recently (a lot of kf5-* packages), so unrelated to
>> qubes-gui-dom0 version.
>
> Yes! It was set to Plastik. Changing it to Breeze and clicking Apply
> instantly fixed the issues. (Well, I can't test whether it fixed the
> icon of the launcher, because I've already done the workaround that I
> described previously. But everything else is fixed now.)
>
> Thank you Marek!
>
> -Jeremy
>

This also instantly fixed the same problem for me, and I can confirm
that it began at about the same time as the kf5-* updates from Fedora.

Thank you!