Q widget going unresponsive

[xaki23]

Qubes OS version:

R4-RC3

Affected TemplateVMs:

---

Steps to reproduce the behavior:

not sure yet. so far happened two out of two times i had an RC3 with more than a bit of uptime and usage.
only known-to-me recovery is logout+login which has about as unpleasant side effects as a reboot.
i am unsure where to look or what to kick to revitalize it.

Expected behavior:

responsive Q widget

Actual behavior:

completely unresponsive Q widget

General notes:

this is even more annoying with the lack of vm-manager

---

Related issues:

[xaki23]

unsure how to debug this.
what process is even responsible for the Q-widget?
is there any less invasive action than logout/login (or reboot) to revitalize the Q-widget?

and a may-or-may-not-be-related ...
right now i have a dbus-daemon in dom0 that is 2.7G virt, 1.4G res (at 8 days of uptime).
i would like to see how that responds to a working q-widget.

[xaki23]

unsure how to debug this.
what process is even responsible for the Q-widget?
is there any less invasive action than logout/login (or reboot) to revitalize the Q-widget?

and a may-or-may-not-be-related ...
right now i have a dbus-daemon in dom0 that is 2.7G virt, 1.4G res (at 8 days of uptime).
i would like to see how that responds to a working q-widget.

[xaki23]

hm. after some messing around with DispVMs (which are not getting purged for me right now, i am collecting halted Disp1234 instances) and USB devices (which seem to work less well than on R3) ...
... suddenly Q-widget is working again ...
... and dbus-daemon is down to <1GB (which is still "too much", but lets blame fragmentation for the moment) ...

so still unsure why Q-widget got stuck, but the dbus-daemon mem footprint relation seems confirmed.

[xaki23]

hm. after some messing around with DispVMs (which are not getting purged for me right now, i am collecting halted Disp1234 instances) and USB devices (which seem to work less well than on R3) ...
... suddenly Q-widget is working again ...
... and dbus-daemon is down to <1GB (which is still "too much", but lets blame fragmentation for the moment) ...

so still unsure why Q-widget got stuck, but the dbus-daemon mem footprint relation seems confirmed.

[qubesos-bot]

Automated announcement from builder-github

The package qubes-desktop-linux-manager-4.0.10-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package qubes-desktop-linux-manager-4.0.10-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package qubes-desktop-linux-manager-4.0.10-1.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package qubes-desktop-linux-manager-4.0.10-1.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update