On Thursday, June 6, 2019 at 9:17:49 PM UTC+2, awokd wrote:
> Qubes666 wrote on 6/6/19 6:56 PM:
> > On Thursday, June 6, 2019 at 7:49:05 PM UTC+2, awokd wrote:
> >> Qubes666 wrote on 6/6/19 8:39 AM:
>
> >>> Ok, have made your two screenshots.
> >>>
On Thursday, June 6, 2019 at 7:49:05 PM UTC+2, awokd wrote:
> Qubes666 wrote on 6/6/19 8:39 AM:
> > Am Donnerstag, 6. Juni 2019 00:34:13 UTC+2 schrieb awokd:
> >> Qubes666:
> >>> Am Mittwoch, 5. Juni 2019 21:58:12 UTC+2 schrieb awokd:
> >>>> indigo1...
Am Donnerstag, 6. Juni 2019 00:34:13 UTC+2 schrieb awokd:
> Qubes666:
> > Am Mittwoch, 5. Juni 2019 21:58:12 UTC+2 schrieb awokd:
> >> indigo1...@gmail.com:
> >>
> >>> Tried to start sys-net or sys-firewall with qvm-start, but did not work:
> >>&
Am Mittwoch, 5. Juni 2019 21:58:12 UTC+2 schrieb awokd:
> indigo1...@gmail.com:
>
> > Tried to start sys-net or sys-firewall with qvm-start, but did not work:
> > File"usr/lib/python3.5/site-packages/qubesadmin/app.py", line 540, in
> > qubesd_call client_socket-connect(qubesadmin.config.QUBESD_
Hi,
need really help. Yesterday i started on my Thinkpad dom0 update through the
terminal command. During verification process the program got stuck. I powered
off. Now, the boot process seems to stop after the login.
Qubes manager, other programs and all VM do no start. (sudo journalctl).
qube
