What makes Qubes unsuitable for non-geek audience could be fixed in liteqube! The problem is, when "something" fails, we do not know what happened -- or did it at all. I suggest making a self-diagnostic tool that could be run periodically to detect common error conditions and warn user (or even take some actions), like:
if network works
if tor works
if time sync works
if core services did not run out of disk space on any fs
if OOM killer damaged something in any core VMs
if input devices are available to dom0
if core-usb did not get 100% cpu load because of stupid "control queue full" bug (who was that idiot who made a handler that works that way?)
What makes Qubes unsuitable for non-geek audience could be fixed in liteqube! The problem is, when "something" fails, we do not know what happened -- or did it at all. I suggest making a self-diagnostic tool that could be run periodically to detect common error conditions and warn user (or even take some actions), like:
did I miss something?