mirror of
https://github.com/Qubes-Community/Contents.git
synced 2024-12-23 06:09:29 -05:00
Create gui-not-working.md
This commit is contained in:
parent
e01c8f9305
commit
8d81dab4fc
33
troubleshooting/gui-not-working.md
Normal file
33
troubleshooting/gui-not-working.md
Normal file
@ -0,0 +1,33 @@
|
|||||||
|
---
|
||||||
|
layout: doc
|
||||||
|
title: GUI Troubleshooting
|
||||||
|
permalink: /doc/gui-troubleshooting/
|
||||||
|
redirect_from:
|
||||||
|
- /en/doc/gui-troubleshooting/
|
||||||
|
- /doc/GuiTroubleshooting/
|
||||||
|
- /wiki/GuiTroubleshooting/
|
||||||
|
---
|
||||||
|
|
||||||
|
# GUI Troubleshooting
|
||||||
|
|
||||||
|
If you can start your VM, but can't launch any applications, then you need to fix the issues from the `VM console`, accessible from xen through:
|
||||||
|
|
||||||
|
~~~
|
||||||
|
qvm-start <VMname> # Make sure the VM is started
|
||||||
|
sudo xl console <VMname>
|
||||||
|
~~~
|
||||||
|
|
||||||
|
## Tips
|
||||||
|
|
||||||
|
### Disable auditd messages
|
||||||
|
|
||||||
|
To disable auditd messages, you need to edit your VM kernel parameters:
|
||||||
|
|
||||||
|
~~~
|
||||||
|
previous_kernel_parameters=$(qvm-prefs --get <VMname> kernelopts) # Get current kernel parameters
|
||||||
|
qvm-prefs --set <VMname> kernelopts "<previous_kernel_parameters> audit=0"
|
||||||
|
~~~
|
||||||
|
|
||||||
|
Then, restart your VM.
|
||||||
|
|
||||||
|
Once your troubleshooting is done, don't forget to remove this kernel parameters, it makes troubleshooting VMs not starting easier.
|
Loading…
Reference in New Issue
Block a user