On 2014-11-14 22:28, Pascal Volk wrote: > On 11/14/2014 09:44 AM, Jeroen Massar wrote: [..] > As mentioned in my message from yesterday, the system is unable to > finish the boot process. The message `A start job is running for LSB: …' > can't be interrupted.
You are using a 'testing' branch of Debian. Problems are to be expected. Especially when changing init systems. You should be filing a critical bug with systemd for breaking your system in this way. > The only workaround, known to me, is enabling systemd's debug shell. In > the (INSECURE!) debug shell I'm able to find out the PID of the > systemclt job, which tries to start aiccu. Then I'm able to kill that job. Definitely sounds like a systemd issue. AICCU does not cause that error, it is systemd causing you all that grief and no way out to simply solve it. >> Also, you can always start AICCU simply by typing 'aiccu start' which is >> what the init script does. > > This is what I've done within the last months, since I've reported the > problem. Hence, AICCU works. It is just something messy in systemd that is causing this. I'll look into it this weekend, though diving into systemd will be 'fun'. Greets, Jeroen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
