Euwiiwueir

Recent posts in the forum thread have me wondering if this is something specific to my configuration rather than a more general issue. I will take another look when I...

I've also been seeing this on my `sys-net`, `sys-firewall`, and `sys-vpn` qubes (`journalctl -b`), all based on Debian 12 or 13 minimal: ``` network-proxy-setup.sh[586]: Error: No such file or directory...

None of these qubes have `systemd-resolved` installed. But neither do `debian-12-xfce` or `debian-13-xfce`, so probably that is not the issue?

If it really is caused by that commit then maybe @HW42 has some thoughts.

I see. So the implementation on Debian is more surgical than on Fedora, it accomplishes what it is intended to do. And the expectation about what `/etc/qubes/post-install.d` is for is...

On 4.3, or a patched `qubes-gui-daemon` on 4.2, the strobe effect could perhaps be mitigated with: ``` [user@dom0 ~]$ qvm-features gui-window-background-color black ``` Assuming it is a redraw loop, not...

Is there anything suggestive in the journal after this happens? In dom0: `sudo journalctl -b`. How does `free -m` look while `xfwm4` is going rogue? What other processes are high-ish...