Hi Marek, On Sat, Nov 05, 2016 at 01:57:44AM +0100, Marek Marczykowski-Górecki wrote: > > I believe I also found a workaround: > > sudo qubes-dom0-update enablerepo=qubes-dom0-current-testing > > --releasever=3.2 qubes-release > > sudo qubes-dom0-update enablerepo=qubes-dom0-current --releasever=3.2 does that make sense?
> What exactly do you mean? Some X server startup error? Do you have any > logs? X crashed or the system shut down. (It was late at night and due to other hardware problems (using external monitor which at this moment I didnt use anymore since an hour) I had experienced many unexpected sudden poweroffs before so I dont really recall whether just X crashed or the hw…) > What exactly do you get when trying to start sys-net and sys-firewall > from shell? `qvm-start sys-firewall` should work just fine from text > console. Of course you'll not get GUI there, but qvm-run should work. ERROR: ERROR: Failed to connect to qmemman: [Errno 2] No such file or directory > > p.s./btw: https://www.qubes-os.org/doc/upgrade-to-r3.1/ advices one to > > install qubes-mgmt-salt-admin-tools but this package does not exist?! > That's interesting, this step should be in 3.1->3.2 instruction... ah. so I guess I should send a patch for qubes-doc tomorrow… (gn8 ;) -- cheers, Holger -- You received this message because you are subscribed to the Google Groups "qubes-users" 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-users/20161105011625.GC16942%40layer-acht.org. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Digital signature
