Package: systemd
Version: 37-1.1
Followup-For: Bug #634472
Is there any plan on bringing closure to this bug report. I don't know
why setserial was installed default on my box but looking at it, it is
not really a package required to be installed.
If it is something that'll be installed on most b
Hi,
> I suspect
>
> # chkconfig: 2345 50 75
>
> in the setserial init script might be to blame. Any chance you could
> remove that line and see if that fixes it?
Yes, removing that line does fix the problem.
Regards
Matthias
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debi
]] Matthias Berndt
Hi,
| thank you for your reply. I do not have nfs-common installed, but the
| problem may yet be the same. Here's an excerpt from my /var/log/dmesg:
|
| [5.413304] systemd[1]: Found ordering cycle on basic.target/start
| [5.413312] systemd[1]: Walked on cycle path to
Hi Tollef,
thank you for your reply. I do not have nfs-common installed, but the
problem may yet be the same. Here's an excerpt from my /var/log/dmesg:
[5.413304] systemd[1]: Found ordering cycle on basic.target/start
[5.413312] systemd[1]: Walked on cycle path to sockets.target/start
[
]] Matthias Berndt
| After I installed systemd today, I noticed that NetworkManager had stopped
| working.
Do you have nfs-common installed? If so, I suspect this is a duplicate
of http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622394
--
Tollef Fog Heen
UNIX is user friendly, it's just pick
Package: systemd
Version: 29-1
Severity: normal
Hi,
After I installed systemd today, I noticed that NetworkManager had stopped
working. There were two reasons, the first was that NetworkManager wasn't
enabled; this could easily be fixed with "systemctl enable
NetworkManager.service". But that alo
6 matches
Mail list logo
