NetworkManager service not enabled by default in sys-net

[Zrubi]

Qubes OS version (e.g., R3.1):

R3.2-rc3

---

Expected behavior:

NM applet in sys-net by default

Actual behavior:

Users have to manually add the NM service in sys-net

Steps to reproduce the behavior:

Clean install, auto generated system VMs

---

Related issues:

[marmarek]

What files do you have in /var/run/qubes-service in case of broken sys-net?

[marmarek]

What files do you have in /var/run/qubes-service in case of broken sys-net?

[Zrubi]

I will check it when I have a chance to redo a clean install...

What I checked is the Qubes Manager services tab where I have not even found the entry for network manager. I had to add it manually.

[Zrubi]

I will check it when I have a chance to redo a clean install...

What I checked is the Qubes Manager services tab where I have not even found the entry for network manager. I had to add it manually.

[sjug]

It's intermittently visible for me, on first boot it definitely was not after a fresh install.

[sjug]

It's intermittently visible for me, on first boot it definitely was not after a fresh install.

[Zrubi]

Now I can confirm:
network manager tray icon is not shown at the first boot.
the file is in the right place under /var/run/qubes-service, but not shown in the service tab.

rebooting the sys-net solves the problem - however it is remains hidden from the service tab.

[Zrubi]

Now I can confirm:
network manager tray icon is not shown at the first boot.
the file is in the right place under /var/run/qubes-service, but not shown in the service tab.

rebooting the sys-net solves the problem - however it is remains hidden from the service tab.

[marmarek]

I have an idea: it doesn't work on the first boot, because there is no panel (so, place for it) there. It is created only after user choose "Use default config".

[marmarek]

I have an idea: it doesn't work on the first boot, because there is no panel (so, place for it) there. It is created only after user choose "Use default config".

[marmarek]

Since this prompt is mostly useless anyway (if one would choose "Use empty config", he/she would also manage to get rid of default one), better get rid of it and choose "Use default config" automatically.

[marmarek]

Since this prompt is mostly useless anyway (if one would choose "Use empty config", he/she would also manage to get rid of default one), better get rid of it and choose "Use default config" automatically.

[qubesos-bot]

Automated announcement from builder-github

The package garcon-0.5.0-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package garcon-0.5.0-1.fc25 has been pushed to the r4.0 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package garcon-0.5.0-1.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

[qubesos-bot]

Automated announcement from builder-github

The package garcon-0.5.0-1.fc25 has been pushed to the r4.0 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update