New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better handle unusual technical error messages #1823

Closed
bnvk opened this Issue Mar 9, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@bnvk

bnvk commented Mar 9, 2016

I just encountered a strange Dom0 error. I am uncertain what triggered this error or how it affected the Qubes VM Manager, as it seemed to be running just fine.

Houston, we have a problem...

AttributeError: 'module' object has no attribute 'VIR_INTERNAL_ERROR'

This is mostly a bug in the Qubes Manager

----
line: elif e.get_error_code() == libvirt.VIR_INTERNAL_ERROR:
func: is_running
line no.: 935
file: /usr/lib64/python2.7/site-packages/qubes/modules/000QubesVm.py
----
line: if not vm.is_running():
func: measure_cpu_usage
line no.: 234
file: /usr/lib64/python2.7/site-packages/qubes/qubes.py
----
line: self.last_measure_time)
func: update_table
line no.: 768
file: /usr/lib64/python2.7/site-packages/qubesmanager/main.py

I have no idea what this message meant. Regarding messages of this nature, perhaps we should handle them in the one of the following ways:

  1. Offer a way to report this message to Qubes (if useful)
  2. A simple notification like Something small went wrong
  3. Or suppress them entirely from the end user
@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong May 19, 2016

Member

Duplicate of #1300.

Member

andrewdavidwong commented May 19, 2016

Duplicate of #1300.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment