systemd daemon-reload timed out in package trigger
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
I just upgrame my system and it crash
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: systemd 225-1ubuntu9
ProcVersionSign
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
Date: Fri Oct 23 22:42:52 2015
DuplicateSignature: package:
ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1
InstallationDate: Installed on 2015-01-15 (282 days ago)
InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
Lsusb:
Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire 4738
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
dpkg 1.18.2ubuntu5
apt 1.0.10.2ubuntu1
SourcePackage: systemd
Title: package systemd 225-1ubuntu9 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
UpgradeStatus: Upgraded to wily on 2015-08-04 (81 days ago)
dmi.bios.date: 05/27/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: V1.16
dmi.board.
dmi.board.name: JE41_CP
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.
dmi.modalias: dmi:bvnINSYDE:
dmi.product.name: Aspire 4738
dmi.product.
dmi.sys.vendor: Acer
tags: | removed: need-duplicate-check |
Do you still have the system in that state? I'm afraid the logs are rather useless -- According to DpkgHistoryLog.txt you started the upgrade on 2015-10-23 22:34:14, but JournalErrors.txt is from the following day, and does not contain useful info. DpkgTerminalLog.txt does not have timestamps, so I don't know when that actually ran (and it's suspiciously short).
This happened during systemd's package trigger, so obviously it failed in "systemctl daemon-reload", and as such is almost surely a followup problem from some underlying real bug. But there is no trace of that so far. Can you please attach /var/log/syslog, and /var/log/syslog.1 ? Perhaps they still have some useful information.
I suppose you rebooted since that incident, so "sudo apt-get -f install" succeeds and cleans up your system? Or does that still fail? If so, that would be highly interesting. Thanks!