Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start
Pete Batard
pete at akeo.ie
Sun Aug 14 22:38:50 BST 2016
Didn't fix it for me... :(
I went to an 'apt-get --reinstall install' of every single package that
is listed under 'Description' above (expect -udeb and -dev), and got the
231-2 version alright, but the issue remains exactly the same, even
after a full reboot.
I should point out that I did get the following warning when updating
udev, which I gather is due to using 'rpi-update'
(https://github.com/Hexxeh/rpi-update) to run a recent kernel:
---------------------------------------------------------------------
# uname -a
Linux pi 4.4.17-v7+ #901 SMP Fri Aug 12 17:57:27 BST 2016 armv7l GNU/Linux
# apt-get --reinstall install udev
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 50 not
upgraded.
Need to get 0 B/1,045 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 130230 files and directories currently installed.)
Preparing to unpack .../archives/udev_231-2_armhf.deb ...
Unpacking udev (231-2) over (231-2) ...
Processing triggers for systemd (231-2) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up udev (231-2) ...
addgroup: The group `input' already exists as a system group. Exiting.
update-initramfs: deferring update (trigger activated)
insserv: warning: current start runlevel(s) (empty) of script `udev'
overrides LSB defaults (S).
insserv: warning: current stop runlevel(s) (S) of script `udev'
overrides LSB defaults (empty).
Processing triggers for initramfs-tools (0.125) ...
/boot/initrd.img-3.18.0-trunk-rpi2 does not exist. Cannot update.
---------------------------------------------------------------------
I guess I'm just going to have to revert those systemd components to
231-1 then...
Regards,
/Pete
More information about the Pkg-systemd-maintainers
mailing list