monitor layout change regression in 4.0-rc2

[o-]

Qubes OS version:

4.0-rc2

Affected TemplateVMs:

all

---

Steps to reproduce the behavior:

Start i3 with the default configuration from qubes-i3 package. Change layout (e.g. add an external monitor) with xrandr.

Expected behavior:

All appvms get notified of the layout change.

Actual behavior:

The clickable area in all running appvms is not updated (only the area of the previous virtual screen are clickable). Rebooting the appvm updates the layout.

General notes:

I had this issue in older releases and was able to resolve it with qubes-monitor-layout-notify. Unfortunately this script was removed in QubesOS/qubes-gui-daemon@25aa33c by @woju . I was not able to find this service in core-admin, as the commit message suggests. Grepping for relevant strings only surfaces a layout-notify event in the gui daemon, but I can't find the actual implementation.

Also it seems, that the gui-daemon-repo still has a references to the removed script in https://github.com/QubesOS/qubes-gui-daemon/blob/cf7cdd09fb425bd37fc6b58cd19222729bb125df/screen-layout-handler/qubes-screen-layout-watches.desktop .

Since I did not find the replacement mechanism, I was not able to debug the issue. If you can point me to it I am happy to investigate further.

--

Related issues:

[marmarek]

Try qvm-start-gui --notify-monitor-layout

[marmarek]

Try qvm-start-gui --notify-monitor-layout

[o-]

@marmarek that works

[o-]

@marmarek that works

[o-]

So what is the expected behavior? Should the notify be triggered automatically, or does the WM have to watch it?

In the second case I could create a PR against qubes-desktop-linux-i3, since I have some other qubes 4.0 changes for it.

[o-]

So what is the expected behavior? Should the notify be triggered automatically, or does the WM have to watch it?

In the second case I could create a PR against qubes-desktop-linux-i3, since I have some other qubes 4.0 changes for it.

[tasket]

BTW, I have experienced this with Xfce.

[tasket]

BTW, I have experienced this with Xfce.

[GAhlekzis]

I experience this in 3.2 with i3wm at the moment. Never had this before and now it happens rather often.

The funny thing is, that it mostly happens with one of my few debian vms. I don't think I ever noticed it with another vm.

[GAhlekzis]

I experience this in 3.2 with i3wm at the moment. Never had this before and now it happens rather often.

The funny thing is, that it mostly happens with one of my few debian vms. I don't think I ever noticed it with another vm.

[DTMW2]

This bug is still active (at least in my system: Thinkpad X1C 5th, Qubes 4 with newest updates installed in both dom0, fedora and debian). Duplicate bug-report: #4052

[DTMW2]

This bug is still active (at least in my system: Thinkpad X1C 5th, Qubes 4 with newest updates installed in both dom0, fedora and debian). Duplicate bug-report: #4052