Bug#893369: systemd-udevd is killed at startup

LEDUQUE Mickaël mleduque at gmail.com
Mon Mar 19 15:36:10 GMT 2018


In /var/log/apt/history.log, I found that

Start-Date: 2018-03-15  09:28:21
Commandline: apt dist-upgrade
Install: libdevmapper1.02.1:i386 (2:1.02.145-4.1, automatic),
libseccomp2:i386 (2.3.1-2.1, automatic), libargon2-0:i386 (0~20161029-1.1,
automatic), libacl1:i386 (2.2.52-3+b1, automatic), libkmod2:i386 (25-1,
automatic), libapparmor1:i386 (2.12-3, automatic), libpam-systemd:i386
(238-2, automatic), systemd:i386 (238-2, automatic), libidn11:i386
(1.33-2.1, automatic), libcryptsetup12:i386 (2:2.0.1-1, automatic),
libjson-c3:i386 (0.12.1-1.3, automatic), libip4tc0:i386 (1.6.2-1, automatic)
Upgrade: libsystemd0:amd64 (237-4, 238-2), libsystemd0:i386 (237-4, 238-2),
libpam-systemd:amd64 (237-4, 238-2), libnss-systemd:amd64 (237-4, 238-2),
ruby-molinillo:amd64 (0.5.0-2, 0.6.4-1)
Remove: bundler:amd64 (1.15.1-1), systemd:amd64 (237-4), ruby-bundler:amd64
(1.15.1-1)
End-Date: 2018-03-15  09:28:29

Also it seems at some point I had systemd:amd64 237-4 and many other
packages as 238-2.
Strangely I find no mention of removing system:amd64 even though

Sélection du paquet systemd:i386 précédemment désélectionné.
Préparation du dépaquetage de .../systemd_238-2_i386.deb ...
Dépaquetage de systemd:i386 (238-2) sur (237-4) ...

(sorry, the logs are in french which is a bit illogical for logs).

(BTW, do I leak anything important with all these logs ? system logs, apt
logs ?)


2018-03-19 16:04 GMT+01:00 Michael Biebl <biebl at debian.org>:

> Am 19.03.2018 um 09:51 schrieb LEDUQUE Mickaël:
> > You're right, but honestly, I have no idea how this happened :
> >
> > $ dpkg -l systemd
> > Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
> > |
> > État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/
> H=semi-installé/W=attend-traitement-déclenchements
> > |/ Err?=(aucune)/besoin Réinstallation (État,Err: majuscule=mauvais)
> > ||/ Nom
> > Version
> > Architecture                          Description
> > +++-========================================================
> =========-=====================================-============
> =========================-==================================
> ============================================================
> =========================================
> > ii  systemd:i386
> > 238-2
> > i386                                  system and service manager
>
> I have no idea how this happened either and why apt decided to replace
> systemd:amd64 with systemd:i386 on an amd64 system.
> But apparently you are not the only one,
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893054 sounds like the
> user ran into a similar problem.
>
> Do you still have the apt logs (check /var/log/apt) which show the
> installation of systemd:i386 and removal of systemd:amd64?
>
> Julian, do you have an idea why something like this can happen?
>
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180319/96958288/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: history.log
Type: text/x-log
Size: 64153 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180319/96958288/attachment-0004.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: term.log
Type: text/x-log
Size: 380475 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180319/96958288/attachment-0005.bin>


More information about the Pkg-systemd-maintainers mailing list