- 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)
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
Add information about `QREXEC_REMOTE_DOMAIN` which is still on the qrexec2.md file but not on the V3. However, this still applies, so it should be documented.
Users keep getting confused because their output doesn't match the
examples, even though the text already says, "This is just an example,
so the output you receive may not look exactly the same."
Recent examples of this:
- https://www.reddit.com/r/Qubes/comments/1f2b221/
- https://forum.qubes-os.org/t/29384
Specifically, users seem to get confused because their RSK has a
different date and key ID than the one in the example (which makes
sense, because RSKs change with each release), so replacing these
specific values with variables may avert some confusion.
