On Tuesday, June 28, 2016 at 3:29:33 PM UTC-4, q wrote:
>
>
>
> On Saturday, June 18, 2016 at 4:49:18 AM UTC-4, Marek Marczykowski-Górecki 
> wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE----- 
>> Hash: SHA256 
>>
>> Details here: 
>>
>> https://www.qubes-os.org/news/2016/06/18/qubes-OS-3-2-rc1-has-been-released/ 
>>
>> As usual, you can download new image from: 
>> https://www.qubes-os.org/downloads/ 
>>
>> Keep in mind it is only release candidate, so not recommended for daily 
>> use. 
>>
>> - -- 
>> Best Regards, 
>> Marek Marczykowski-Górecki 
>> Invisible Things Lab 
>> A: Because it messes up the order in which people normally read text. 
>> Q: Why is top-posting such a bad thing? 
>> -----BEGIN PGP SIGNATURE----- 
>> Version: GnuPG v2 
>>
>> iQEcBAEBCAAGBQJXZQsGAAoJENuP0xzK19csqisIAJRdhruvqDJSU0ynNJ59IrJu 
>> o9rrXtguG0YiiIzwtW/jQpX3YIlmzCf+PG3gSvYugzN2wPciGzedXKsuIKZdQH/d 
>> SrAFS2snNT0Lxq9pMhq2sHGNXw12X46wgp/kMnbm54X/egUSeNHuWEy1fc9Kowe3 
>> HCpVCrRqwOr3e6fdcp5C7QVEmRs4kA5CbHg5GaQouCjlyK6Xoj/XJAkSKSJzegmY 
>> gixq+9ZEybPcAmCmyZnKy7V5noU5US1x0UraPHsgIkVY4Sondb4ArkixOcCqQgRt 
>> wxvDPz/3A/tMTr142fDI7a5udTzSid2aYVy2Y+08Dfu0AhQOw+BFW0pKJ4Z3KN0= 
>> =Suhv 
>> -----END PGP SIGNATURE----- 
>>
>
> thank you for all your hard work. i have everything working. here is some 
> feedback and comments to help other users (i have a lot of qubes 
> troubleshooting experience):
>
> install time: "test install media" crashes. very easy to reproduce so i 
> wont bother typing out the error. not a show stopper.
>
> install time: i noticed that the disk partitioning works much better now 
> and has a slightly better interface. this was a great improvement. i also 
> noticed that installing on older qubes disk doesnt have a bug like it did 
> in the past few versions. these were obscure anyway. some people will 
> appreciate this.
>
> first boot: checked all the boxes except "use netvm for usb" and "do 
> nothing". everything VERY SLOW. user logs in, no task bar. something wrong 
> with kde. can only see qubes vm manager. waited 15 minutes (this is a good 
> idea). switched to a different tty (ctrl+alt+f2) and rebooted. 
>
> second boot: kde looks normal. no other problem detected related to 
> earlier kde issue. this is very good news.
>
> whonix funny: for some reason sys-whonix seems to have a yellow light when 
> everything should be green (various checks i performed). this only happened 
> the first 2 times i launched sys-whonix.
>
> template upgrade notification bug: i have to run update, reboot template, 
> run again, shut down template, then the update notification in 
> qubes-vm-manager goes away. it should go away when the first update 
> completes. i tried reproducing this. it only occurred on whonix-gw and 
> fedora-23 templates. strange and intermittent. when all else fails it is 
> good to let qubes "try again".
>
> updates: there were a lot of updates to install! both in templates and in 
> dom0. this hasnt been out very long. is there a reason?
>
> first reboot after a lot of dom0 updates were installed: a lot of errors 
> dev-mapper device or resource busy. locks at "rebooting" (probably just a 
> power management issue). waited 10 minutes (this is a good idea). had to 
> hard reboot manually.
>
> second reboot after all updates installed dom0 and template-vms: after the 
> failed reboot attempt the machine trys to boot up again. everything feels a 
> bit more smooth than before. no indication of problems. 
>
> lets try rebooting again to see if it misbehaves like last time. no 
> misbehavior. no dev-mapper errors. reboot successful.
>
> note: sys-whonix is yellow again. rebooted sys-whonix. all green. i think 
> that it goes yellow when the tor circuit is unavailable? if so i guess this 
> could be a feature.
>
> questions:
> dom0: when will this be fedora 24? is it intended for 3.2-release to be 
> 24? have you considered changing to debian for consistency (whonix, etc)?
>
>
one more thing: to get dispvm working i had to launch firefox in 
fedora-23-dvm, shut fedora-23-dvm down, and then try to launch a disp-vm. 
dont ask why, it has to do with how disposable-vms are created and 
initialized and the savefile, etc. theres a bug the first time you try to 
launch a disp-vm if it is before fedora-23-dvm has ever been launched.  

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-devel/1621aa08-527b-40d9-9e8a-8932f254b697%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to