Strange 'critical error' from Qubes Manager

I open a firefox browser dispVM.

Then, I receive a critical error message - which originates from qubes Manager.

I was going to paste the text into nano and screenshot for debug here, but I get code execution warning (I guess because it references python functions).

Still, strange ‘critical error’, given there was no apparent malfunction.

1 Like

Here’s the error message from several recent dom0 critical errors that I’ve gotten, also related to the beloved Qubes Manager:

----
line: yield from self._listen_for_events(vm)
func: listen_for_events
line no.: 139
file: /usr/lib/python3.8/site-packages/qubesadmin/events/__init__.py
----
line: return future.result()
func: run_until_complete
line no.: 313
file: /usr/lib/python3.8/site-packages/qasync/__init__.py
----
line: loop.run_until_complete(
func: run_asynchronous
line no.: 529
file: /usr/lib/python3.8/site-packages/qubesmanager/utils.py

Looks similar…

1 Like

@qubes-kernel-5.8

This is the same error.
Did this appear after a particular action?

As above, for me, there was no apparent action, other than opening the dispVM (which opened & ran without any other issues), which I could think initiated this.

This has happened at least thrice in the past month. I haven’t noticed any patterns, but I haven’t deliberately tracked what I’ve been doing either…

I’m running a 4.1 .iso from the OpenQA

Update: I have gotten this error twice since posting, and it has happened both times right after I close a whonix-ws-15-dvm Tor Browser (AnonDist).