In a discussion on Qubes OS forum, it was decided that I should add some extra text about the netmask, and an example for Network Manager. The purpose being to make the procedure much clearer.
There are two images to go into the text, but I don't understand how to do that yet. I have used '>' at those points. Please advise.
Francis.
- Replace list of certified models with table
- Create page for each certified model
- Organize certified hardware files in subdirectory
- Update certification details of individual model pages
- Add warnings for X230- and T430-based models
(QubesOS/qubes-issues#9782)
- makes it less likely to get the false impression that
the updates proxy does not allow arbitrary outbound connections
- add example of how to download software in templates without
enabling direct networking
I was affected by this problem. When I saw this documentation, I didn't realize this was the problem affecting me. I don't have a 4K monitor; I have a wide monitor. I can click on most things, just not in specific sections of the screen.
Rewrite to be more generic.
The "App menu shortcut troubleshooting" page seemed to be somewhat
outdated and lacking in information to facilitate troubleshooting. This
is what I did:
* trying to use consistently "qube" instead of "vm"
* trying to get consistent placeholders as uppercase between brackets
* the first part now has a title and distinguishes the GUI from the CLI,
when needed, it is referred to in the following part, instead of
repeating it.
* when a shortcut is missing, add a way to check it from the qube, to
get a better understanding of the problem ("Unavailable desktop
entry")
* the example of a desktop entry is simplified to its bare minimum
* "Fixing shortcuts" is replaced by a more accurate title. Not sure if
this part is still useful.
* mention that `my-old-vm` becomes `my_dold_dvm`
* removed an off-topic comment on Windows HVM and a missing (old?) script
* new part about how to troubleshoot a shortcut that doesn't do anything
Todo:
* update the screenshots
* is the "custom entry" still useful ?
* "Behind the scenes" could be developed
Although sys-gui (and its variants sys-gui-gpu and sys-gui-vnc) are clearly marked to be used by advanced users only, there are some limitations that may go beyond the expectations of an advanced user.
This updates the documentation to contain some known issues that probably don't have a quick fix.
