Error final part of installation

[adeptcoder7]

I get an error message at final part of installation, it happens after configuring the template vms. I also left all the options default. I believe its to do with network manager:

['/usr/sbin/service', 'qubes-netvm', 'start'] failed:
stdout: ""
stderr: "Redirecting to /bin/systemctl start qubes-netvm.service
Job for qubes-netvm.service failed because the control process exited with error code. "See ststemctl status qubes-netvm.service" and "journalctl -xe" for details.
"
Note I checked the digests and I the media test passed fine. I also tried to complete the installation on different computers but that different help.

Its the same issue as described in this post: https://www.reddit.com/r/Qubes/comments/6b484q/having_an_issue_in_the_last_part_of_the/?st=J35Y5Y0X&sh=83624631

[adeptcoder7]

[adeptcoder7]

[marmarek]

Check details as instructed in the error message (you should be able to login after closing this error message).

[marmarek]

Check details as instructed in the error message (you should be able to login after closing this error message).

[adeptcoder7]

Yes I can login but what does the error mean and the consequences of it? Thanks, Harri

…

On Sat, 17 Mar 2018, 12:16 Marek Marczykowski-Górecki, < ***@***.***> wrote: Check details as instructed in the error message (you should be able to login after closing this error message). — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3710 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AjuUfPkcevxvB9m-5PopBalPijYVF9PMks5tfP6QgaJpZM4Suvjm> .

[adeptcoder7]

Yes I can login but what does the error mean and the consequences of it? Thanks, Harri

…

On Sat, 17 Mar 2018, 12:16 Marek Marczykowski-Górecki, < ***@***.***> wrote: Check details as instructed in the error message (you should be able to login after closing this error message). — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3710 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AjuUfPkcevxvB9m-5PopBalPijYVF9PMks5tfP6QgaJpZM4Suvjm> .

[marmarek]

It failed to start sys-net and/or sys-firewall. If that was temporary, everything else should be fine. But if it's persistent, you wont be able to start any network-connected VM. See "journalctl -xe".

[marmarek]

It failed to start sys-net and/or sys-firewall. If that was temporary, everything else should be fine. But if it's persistent, you wont be able to start any network-connected VM. See "journalctl -xe".

[adeptcoder7]

Okay I can get it working on my old computer, but on my main computer. The disk password box never shows up can I fix this? Or alternatively type it through the console?

…

On Sat, 17 Mar 2018, 15:07 Marek Marczykowski-Górecki, < ***@***.***> wrote: It failed to start sys-net and/or sys-firewall. If that was temporary, everything else should be fine. But if it's persistent, you wont be able to start any network-connected VM. See "journalctl -xe". — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3710 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AjuUfD6c3dFC7GY7OpdY1W9FDlToaOr8ks5tfSbGgaJpZM4Suvjm> .

[adeptcoder7]

Okay I can get it working on my old computer, but on my main computer. The disk password box never shows up can I fix this? Or alternatively type it through the console?

…

On Sat, 17 Mar 2018, 15:07 Marek Marczykowski-Górecki, < ***@***.***> wrote: It failed to start sys-net and/or sys-firewall. If that was temporary, everything else should be fine. But if it's persistent, you wont be able to start any network-connected VM. See "journalctl -xe". — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3710 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AjuUfD6c3dFC7GY7OpdY1W9FDlToaOr8ks5tfSbGgaJpZM4Suvjm> .