[qubes-users] Deleting Disposable VMs / Qubes Docs / Warning

Hi. Just a little warning: The typing error [user@dom0 ~]$ QUBES[instead of qvm]-prefs default_disp "" in the section »Deleting Disposable VM« on https://www.qubes-os.org/doc/dispvm-customization can cost you hours of research –if you are as

[qubes-users] Qubes 4.0 / Updated to Fedora 27 / Networking

Hello all. Just a little hint:Using tasket's brilliant Qubes-vpn-support(easy to searx and find),I had to update/reinstall it in order to see thebeloved box »Link is up!« again. #Qubes-4.0  #updating  #templates  #appvms  #Fedora-26-to-27 Cheers,Pony Boy -- You received this message because

[qubes-users] Upgrade Fedora 26 to 27 (+ Whonix 14, Debian 10)

This – now – works very well following the instructions on Qubes' (/ Whonix') websites. ★ Qubes 4★ Asus »Zenbook« UX303LNB Best regards! -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails

Re: [qubes-users] No boot after dom0 security repo update on may 15

>> My machine directly boots into BIOS screen if my Asus Zenbook UX303 after >> updating Qubes 4.0 dom0, security repo enabled. I don't remember the error >> messages (s.th. with keys). >> So I boot from rescue USB Stick. Have to choose (3), going directly to >> shell. — >> And here I'm stuck,

Re: [qubes-users] No boot after dom0 security repo update on may 15

> My machine directly boots into BIOS screen if my Asus Zenbook UX303 after > updating Qubes 4.0 dom0, security repo enabled. I don't remember the error > messages (s.th. with keys). > So I boot from rescue USB Stick. Have to choose (3), going directly to shell. > — > And here I'm stuck, since

[qubes-users] No boot after dom0 security repo update on may 15

Hi all. My machine directly boots into BIOS screen if my Asus Zenbook UX303 after updating Qubes 4.0 dom0, security repo enabled. I don't remember the error messages (s.th. with keys). So I boot from rescue USB Stick. Have to choose (3), going directly to shell. — And here I'm stuck, since many,