Do not start guivm for notifications#82
Conversation
Notifications proxy is started before GUI agent, so just starting a VM will trigger the service. Theoretically starting associated GUI domain shouldn't be an issue (to have where to show the notification), but in practice there are a few corner cases here: - when setting up GUI domain (especially sys-gui-gpu) there are a bunch of steps involved, and starting it too early may interrupt them (as sys-gui-gpu takes keyboard/mouse away from dom0). - just starting GUI domain usually won't make notifications work yet - user needs to log into that GUI domain first QubesOS/qubes-issues#889
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2025082204-4.3&flavor=pull-requests Test run included the following:
New failures, excluding unstableCompared to: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2025081011-4.3&flavor=update
Failed tests6 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/149225#dependencies 72 fixed
Unstable testsDetailsPerformance TestsPerformance degradation:19 performance degradations
Remaining performance tests:53 tests
|
2 participants
Notifications proxy is started before GUI agent, so just starting a VM
will trigger the service. Theoretically starting associated GUI domain
shouldn't be an issue (to have where to show the notification), but in
practice there are a few corner cases here:
of steps involved, and starting it too early may interrupt them (as
sys-gui-gpu takes keyboard/mouse away from dom0).
user needs to log into that GUI domain first
QubesOS/qubes-issues#889