I have a request that I believe would tremendously help new and experienced users of Qubes alike.
When the system encounters an error and throws an error message popup or a system notification, it would be extremely helpful if the resultant error codes and associated filenames were hyperlinked to relevant Qubes man/wiki pages - with the additional option of having the problematic files hyperlinked to their relevant config files.
It would place Qubes light years ahead when it came to trouble-shooting Qubes errors and considerably ease the Qubes learning curve.
Unfortunately, that kind of error message is a Python traceback: the program is falling in some unexpected way, so there is no related manpage or documentation page. A link to the specific file might not help either.
If the ālink to the specific file might not help eitherā, then what purpose is served by including it - along with a line number - in the error message? Doing so would only seem to make the error more difficult to solve as it leads one to believe there is some sort of a discrepancy in the file at that line number.
It is the āDevice ā%sā not in treeā % dev.name link that would direct to the corresponding man/wiki page.
If a link to the file doesnāt help, and a link to the error description doesnāt help, then doesnāt showing messages with this type of information only add to the confusion and difficulty of solving whatever error has occurred?
Thanks, but youāre missing my point.
I obviously used a bad example.
My suggestion was meant to refer to error messages that display to the user where he/she is expected to troubleshoot/repair the issue themselves.
