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

CalledProcessError in Qubes VM Manager #1604

Closed
hansWURSCHT10000 opened this Issue Jan 11, 2016 · 4 comments

Comments

@hansWURSCHT10000

I'm on Qubes R3.0 and I think I got this error now for the third time. Always when my PC boots and as soon as Qubes VM Manager starts.

It says:

Whoops. A critical error has occured. This is most likely a bug in Qubes Manager

CalledProcessError: Command '['/usr/bin/wmctrl', '-R', 'Qubes VM Manager']' returned non-zero exit status 1 at line 542 of file subprocess.py.

Details:

----
line: raise CalledProcessError(retcode, cmd)
func: check_call
line no.: 542
file: /usr/lib64/python2.7/subprocess.py
----
line: ['/usr/bin/wmctrl', '-R', str(manager_window.windowTitle())])
func: bring_manager_to_front
line no.: 1959
file: /usr/lib64/python2.7/site-packages/qubesmanager/main.py
----
line: bring_manager_to_front()
func: show_manager
line no.: 1916
file: /usr/lib64/python2.7/site-packages/qubesmanager/main.py

I don't know why this error occurred.

var_log_xen_console_hypervisor_log.txt

@relder251

This comment has been minimized.

Show comment
Hide comment
@relder251

relder251 Aug 2, 2016

I'm having the same issue in 3.2r1. It only started after an update to dom0 (update in the last week).

I'm having the same issue in 3.2r1. It only started after an update to dom0 (update in the last week).

@payalord

This comment has been minimized.

Show comment
Hide comment
@payalord

payalord Dec 7, 2016

I have the same problem on Qubes R3.2, that i downloaded yesturday and after installed updates just right now.

here is details:

----
line: raise CalledProccessError(retcode, cmd)
func: check_call
line no.: 540
file: /usr/lib64/python2.7/subproccess.py
----
line: ['/usr/bin/wmctrl', '-R', str(manager_window.windowTitle())])
func: bring_manager_to_front
line no.: 2006
file: /usr/lib64/python2.7/site-packages/qubesmanager/main.py
----
line: bring_manager_to_front()
func: show_manager
line no.: 1963
file: /usr/lib64/python2.7/site-packages/qubesmanager/main.py

payalord commented Dec 7, 2016

I have the same problem on Qubes R3.2, that i downloaded yesturday and after installed updates just right now.

here is details:

----
line: raise CalledProccessError(retcode, cmd)
func: check_call
line no.: 540
file: /usr/lib64/python2.7/subproccess.py
----
line: ['/usr/bin/wmctrl', '-R', str(manager_window.windowTitle())])
func: bring_manager_to_front
line no.: 2006
file: /usr/lib64/python2.7/site-packages/qubesmanager/main.py
----
line: bring_manager_to_front()
func: show_manager
line no.: 1963
file: /usr/lib64/python2.7/site-packages/qubesmanager/main.py
@Gastonite

This comment has been minimized.

Show comment
Hide comment
@Gastonite

Gastonite Jun 22, 2017

I have the same problem on R3.2.
I didn't change anything to the system. Yesterday it was working without problems, but today i have the above error message, and no windows borders.

I tried to kill the qubes manager process and relauch it : the message does not appear anymore, but when i restart the computer, it reappears.

So i tried to update dom0, nothing changed.

How to recover an operational system?

Gastonite commented Jun 22, 2017

I have the same problem on R3.2.
I didn't change anything to the system. Yesterday it was working without problems, but today i have the above error message, and no windows borders.

I tried to kill the qubes manager process and relauch it : the message does not appear anymore, but when i restart the computer, it reappears.

So i tried to update dom0, nothing changed.

How to recover an operational system?

@Gastonite

This comment has been minimized.

Show comment
Hide comment
@Gastonite

Gastonite Jun 25, 2017

Ok
I reproduced the bug on a R3.2 freshly installed:

  1. create some windows (e.g. Firefox of sys-net)
  2. press ALT+F4 multiple times (this will close all the windows and when all are closed, the xfce session menu opens.
  3. click the shut down button
  4. power on and login

Now all the windows borders disappeared, there is only 1 desktop instead of 4 and an error prompt says: CalledProcessError: Command '['/usr/bin/wmctrl', '-R', 'Qubes VM Manager']...

Thanks to this post, i followed the instructions of http://wiki.xfce.org/faq#i_have_only_one_desktop_and_can_t_move_my_windows_anymore_help

So, to resolve the problem, press ALT+F2 and type the following command :

xfwm4 --sm-client-id=${SESSION_MANAGER##*/} & disown

Normally, all windows will reappear and no error message will prompt at startup.

Gastonite commented Jun 25, 2017

Ok
I reproduced the bug on a R3.2 freshly installed:

  1. create some windows (e.g. Firefox of sys-net)
  2. press ALT+F4 multiple times (this will close all the windows and when all are closed, the xfce session menu opens.
  3. click the shut down button
  4. power on and login

Now all the windows borders disappeared, there is only 1 desktop instead of 4 and an error prompt says: CalledProcessError: Command '['/usr/bin/wmctrl', '-R', 'Qubes VM Manager']...

Thanks to this post, i followed the instructions of http://wiki.xfce.org/faq#i_have_only_one_desktop_and_can_t_move_my_windows_anymore_help

So, to resolve the problem, press ALT+F2 and type the following command :

xfwm4 --sm-client-id=${SESSION_MANAGER##*/} & disown

Normally, all windows will reappear and no error message will prompt at startup.

marmarta added a commit to marmarta/qubes-manager that referenced this issue Jul 11, 2018

Tiny fix for rare error in Qubes Manager
It's not necessary to use check_call, especially as raising Qubes
Manager can cause errors shortly after system start.

fixes QubesOS/qubes-issues#1604

@marmarta marmarta referenced this issue in QubesOS/qubes-manager Jul 11, 2018

Merged

Tiny fix for rare error in Qubes Manager #102

@marmarek marmarek closed this Jul 14, 2018

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