Had same experience over the summer, run testing, kernel latest due to machine being newer hardware, which is now 2 years old but that doesn’t mean anything in xen world.
- sys-usb-dvm does not always find mouse and i have to restart the dvm
- fractals in the tray sometimes
- it seemed that updating VMs right when the Star sign lights up was a bad idea, would crash to login screen with appVMs still running
dom0 widget-wrapper[14221]: python3: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
dom0 systemd-coredump[28361]: Process 10756 (xss-lock) of user 1000 dumped core.
dom0 qrexec-policy-e[28371]: error calling qrexec-policy-agent in dom0
Traceback (most recent call last):
File “/usr/lib/python3.8/site-packages/qrexec/tools/qrexec_policy_exec.py”, line 133, in execute
await super().execute(caller_ident)
File “/usr/lib/python3.8/site-packages/qrexec/policy/parser.py”, line 556, in execute
raise ExecutionFailed(‘qrexec-client failed: {}’.format(command))
qrexec.exc.ExecutionFailed: qrexec-client failed: [‘/usr/lib/qubes/qrexec-client’, ‘-d’, ‘dom0’, ‘-c’, ‘SOCKET12,sys-net,1’, ‘-E’, ‘QUBESRPC qubes.WindowIconUpdater+ sys-net keyword adminvm’]
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.8/site-packages/qrexec/tools/qrexec_policy_exec.py", line 151, in notify
await call_socket_service(guivm, service, source_domain, params)
File "/usr/lib/python3.8/site-packages/qrexec/server.py", line 105, in call_socket_service_local
reader, writer = await asyncio.open_unix_connection(path)
File "/usr/lib64/python3.8/asyncio/streams.py", line 111, in open_unix_connection
transport, _ = await loop.create_unix_connection(
File "/usr/lib64/python3.8/asyncio/unix_events.py", line 244, in create_unix_connection
await self.sock_connect(sock, path)
File "/usr/lib64/python3.8/asyncio/selector_events.py", line 496, in sock_connect
return await fut
File "/usr/lib64/python3.8/asyncio/selector_events.py", line 501, in _sock_connect
sock.connect(address)
ConnectionRefusedError: [Errno 111] Connection refused
dom0 qrexec[28371]: qubes.WindowIconUpdater: sys-net → dom0: error while executing: qrexec-client failed: ['/usr/lib/qubes
dom0 lvm[4480]: No longer monitoring thin pool qubes_dom0-vm–pool-tpool.
dom0 lvm[4480]: Monitoring thin pool qubes_dom0-vm–pool-tpool.
dom0 systemd-coredump[15815]: Process 10276 (Xorg) of user 0 dumped core.
Stack trace of thread 10276:
Just a few significant looking red parts of journactl.
My conclusion was, wait before updating the system till it goes into a more idle state and that either Heat spikes or some sort of bottleneck wanting data from my nvme causes to login crash.
Not sure how to test the effectiveness of my nvme + current state of nvme drives getting slower over time (there might or there might not be a fw patch that actually works).
Waiting before instant firing up updates seemed to do the trick.
Seemed because there were times where it did not, though rather seldomly.
Maybe i should post the journactl errors on github even though i fear my mobo might be to new, is there already a thread?
