Bug#757207: systemd: Installation of systemd makes system unbootable

[Michael Biebl]

tags 757207 + moreinfo
thanks

Am 06.08.2014 10:28, schrieb Jens Stavnstrup:
> Package: systemd
> Severity: critical
> Justification: breaks the whole system
> 
> The bug is properly related to #754059, but unlike Filippo, I was stupid enough to update to systemd,

Please keep technical. We won't communicate on that level.

> Using emergency mode (which is also a problem due to #755581), I was able to re-add sysvinit-core, which subsequently removed
> 
> network-manager:i386 (0.9.10.0-1), kde-plasma-desktop:i386
> (84), hplip:i386 (3.14.6-1), plasma-nm:i386 (0.9.3.3-4),
> printer-driver-postscript-hp:i386 (3.14.6-1), systemd-sysv:i386
> (208-6), kde-standard:i386 (84), polkit-kde-1:i386 (0.99.1-1),
> packagekit:i386 (0.8.17-4), appstream-index:i386 (0.7.0-2),
> task-kde-desktop:i386 (3.20), policykit-1-gnome:i386 (0.105-2),
> listaller:i386 (0.5.8-2), plasma-widget-networkmanagement:i386
> (0.9.3.3-4), gvfs:i386 (1.20.2-1), colord:i386 (1.2.1-1),
> libpam-systemd:i386 (208-6), udisks2:i386 (2.1.3-2),
> packagekit-tools:i386 (0.8.17-4), gvfs-daemons:i386 (1.20.2-1),
> policykit-1:i386 (0.105-6.1), apper:i386 (0.8.2-3)
> 
> Have looked at the different bug reports, but have not found anyway to restablish my system.
> 
> What systemd packages should be added, it order for my system to work properly again? And do I need to modify anything else? Looked at the systemd wiki entry, but that seems a bit outdated with respect to the discussion taking place on the debian-devel mailing-list.
> 
> Adding systemd, systemd-shim and cgmanager did not help. 
> 
> Trying to add several of the packages in the above list .e.f. network-manager requires systemd and will remove sysvinit-core and make my system unbootable again. 
> 
> 
> Since I am using a LVM2 encripted disk, this report may also be related to #678438 and/or #692120.
> 
> 

Please enable the debug-shell.service (systemctl enable
debug-shell.service), then boot with the following kernel command line
option to enable a verbose debug log

systemd.log_level=debug


During boot when the system "get's stuck", switch to tty9 and get us the
output of "systemctl list-jobs" and "journalctl -alb"

What is the last output you see on tty1?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140806/af78abb7/attachment-0002.sig>