You are not logged in.
I couldn't find this problem on the wiki or on the forum, so I'm posting it. Sorry if I missed something and it was already discussed.
So I've upgraded to systemd and everything went smoothly, except for one silly issue. Namely, for some reason now NetworkManager seems to start later in the boot process (than it used to before migrating to systemd), and when my KDE loads, there is still no connection and the picture-of-the-day plasmoid and weather wallpaper cannot access the internet and therefore display errors. In couple of seconds the connection is established, but, since these widgets update only once an hour or so, they still show errors for quite a long time, unless manualy updated.
This issue was not present before migrating to systemd, NetworkManager was able to establish the connection before KDE loaded.
That's a bit annoying and I couldn't find a way to fix it. Obviously, it should be solved by forcing NetworkManager to start earlier in the boot process (so that it would have time to establish the connection before KDE loads), but I couldn't find how to do it properly. I've read that it's possible to set "before"/"after" properties for units, so, in principle, modifying NetworkManager unit and listing all other available units in the "before" section could work, but it seems to be a very ugly solution.
Enabling NetworkManager-wait-online.service just increases the boot time by 6 seconds, but doesn't solve the problem.
Last edited by jerf (2012-11-13 13:15:52)
Offline
You think in Units. I think you have to include targets! Maybe the multi-user.target is a good choice? Report, if you got it, I'm interested, if it works, since I did not yet work to much with systemd targets.
Last edited by Lord Bo (2012-11-13 14:21:02)
Offline
You think in Units. I think you have to include targets! Maybe the multi-user.target is a good choice? Report, if you got it, I'm interested, if it works, since I did not yet work to much with systemd targets.
How are targets going to help? Multi-user.target already contains networkmanager.service.
Offline
Ah, ok, the network manager is started by the multiuser target,
but it does not yet complete it's tasks, before KDE starts. Have
you read the systemd concerning part of the wiki entry for the
network manager? Especially the part „Network services with
NetworkManager dispatcher“? It mentions how to handle Programs
which depend on the network interfaces to be configured (by the
network manager).
Last edited by Lord Bo (2012-11-13 17:26:56)
Offline