untrusted_qdb invoked before qubesdb fully started #9514
Labels
affects-4.2
This issue affects Qubes OS 4.2.
C: core
needs diagnosis
Requires technical diagnosis from developer. Replace with "diagnosed" or remove if otherwise closed.
P: default
Priority: default. Default priority for new issues, to be replaced given sufficient information.
T: bug
Type: bug report. A problem or defect resulting in unintended behavior in something that exists.
How to file a helpful issue
Qubes OS release
Qubes OS 4.2.0 (R4.2)
Brief summary
During vm start
sys-gui-gpu
failed to start. After checking journalctl the following error found:The error causes sys-gui-gpu to restart and get new
xid
. Some vms might start before sys-gui-gpu and uses the oldqubes-gui-domain-xid
. As a result,qubes-gui-agent
run with unsyncedqubes-gui-domain-xid
.After tracing the error
untrusted_qdb
is used at core3ext. which might be invoked before startingqubesdb
I tried to add a check at
untrusted_qdb
for the sock file/var/run/qubes/qubesdb.sys-gui-gpu.sock
created byqubesdb
to make sure it started before anyone tries to invoke it. After adding the check the error didn't appear again.Steps to reproduce
Occurs randomly
Expected behavior
sys-gui-gpu starts normally and gui-agent in appvms run with correct xid
Actual behavior
sys-gui-gpu restart once which causes gui-agents in appvm to run with wrong gui-domain-xid
The text was updated successfully, but these errors were encountered: