Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upCalledProcessError in Qubes VM Manager #1604
Comments
marmarek
added
bug
C: qubes-manager
P: major
labels
Jan 11, 2016
marmarek
added this to the Release 3.0 updates milestone
Jan 11, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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).
relder251
commented
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). |
marmarek
modified the milestones:
Release 3.0 updates,
Release 3.1 updates
Nov 19, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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:
|
andrewdavidwong
modified the milestones:
Release 3.1 updates,
Release 3.2 updates
May 31, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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 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? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Gastonite
Jun 25, 2017
Ok
I reproduced the bug on a R3.2 freshly installed:
- create some windows (e.g. Firefox of sys-net)
- press ALT+F4 multiple times (this will close all the windows and when all are closed, the xfce session menu opens.
- click the shut down button
- 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
Now all the windows borders disappeared, there is only 1 desktop instead of 4 and an error prompt says: 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 :
Normally, all windows will reappear and no error message will prompt at startup. |
hansWURSCHT10000 commentedJan 11, 2016
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:
Details:
I don't know why this error occurred.
var_log_xen_console_hypervisor_log.txt