Re: [qubes-users] Done with Qubes

2019-08-25 Thread scurge1tl
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 O K: > Thanks for all the help but I've been trying to figure out how to > get Qubes running for months and I've decided it's just a giant > waste of my time because every time I get one bug fixed, two more > show up to take it's place. I think

Re: [qubes-users] Some problems with 4.0.2-rc1

2019-08-25 Thread Rusty Bird
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 donoban: > On 8/25/19 5:58 PM, Rusty Bird wrote:> Here are some screenshots of how to > get automatic btrfs partitioning: > > https://openqa.qubes-os.org/tests/3240 ("install_partitioning_btrfs" > > is the relevant section.) > > Thanks Rusty, after

Re: [qubes-users] Some problems with 4.0.2-rc1

2019-08-25 Thread Rusty Bird
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 donoban: > On 8/25/19 4:22 PM, Rusty Bird wrote: > > donoban: > > > 2) Btrfs installation seems too hard. After some tries I did an unbootable > > > installation. > > > > Did you create the btrfs partitions manually or did you use the > > installer

Re: [qubes-users] Some problems with 4.0.2-rc1

2019-08-25 Thread donoban
On 8/25/19 4:22 PM, Rusty Bird wrote: donoban: 2) Btrfs installation seems too hard. After some tries I did an unbootable installation. Did you create the btrfs partitions manually or did you use the installer partitioning screen's "Click here to create them automatically" button? The latter

Re: [qubes-users] Some problems with 4.0.2-rc1

2019-08-25 Thread Rusty Bird
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 donoban: > 2) Btrfs installation seems too hard. After some tries I did an unbootable > installation. Did you create the btrfs partitions manually or did you use the installer partitioning screen's "Click here to create them automatically" button?

Re: [qubes-users] Qubes does not recover from crashed X11 (related to shmoverride and GUID)

2019-08-25 Thread Vít Šesták
OK, I have created https://github.com/QubesOS/qubes-issues/issues/5273 . There is not much new information in the issue. The main new information is that the recovery by renaming the shm.id.0 and restarting lightdm is just partial – all running VMs lose sound output (until rebooted) and some