Failed to restart error on upgrade

Bug #1816742 reported by fossfreedom
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
acpid (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

On upgrade I got an upgrade issue as a result of yesterdays new upload

dad@dad-VirtualBox:~$ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up acpi-support (0.143) ...
Job for acpid.service failed because of unavailable resources or another system error.
See "systemctl status acpid.service" and "journalctl -xe" for details.
invoke-rc.d: initscript acpid, action "restart" failed.
dpkg: error processing package acpi-support (--configure):
 installed acpi-support package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 acpi-support
E: Sub-process /usr/bin/dpkg returned an error code (1)
dad@dad-VirtualBox:~$ journalctl -xe

dad@dad-VirtualBox:~$ journalctl -xe
-- Support: http://www.ubuntu.com/support
--
-- The unit acpid.service has entered the 'failed' state with result 'resources'.
Feb 20 11:07:59 dad-VirtualBox systemd[1]: Failed to start ACPI event daemon.
-- Subject: A start job for unit acpid.service has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit acpid.service has finished with a failure.
--
-- The job identifier is 1894 and the job result is failed.

systemctl status acpid.service

● acpid.service - ACPI event daemon
   Loaded: loaded (/lib/systemd/system/acpid.service; disabled; vendor preset: enabled)
   Active: failed (Result: resources)

Feb 20 11:05:07 dad-VirtualBox systemd[1]: acpid.service: Failed with result 'resources'.
Feb 20 11:05:07 dad-VirtualBox systemd[1]: Failed to start ACPI event daemon.
Feb 20 11:06:38 dad-VirtualBox systemd[1]: acpid.service: Got no socket.
Feb 20 11:06:38 dad-VirtualBox systemd[1]: acpid.service: Failed to run 'start' task: Invalid argument
Feb 20 11:06:38 dad-VirtualBox systemd[1]: acpid.service: Failed with result 'resources'.
Feb 20 11:06:38 dad-VirtualBox systemd[1]: Failed to start ACPI event daemon.
Feb 20 11:07:59 dad-VirtualBox systemd[1]: acpid.service: Got no socket.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: acpi-support 0.143
ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
Uname: Linux 4.19.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Wed Feb 20 11:12:44 2019
InstallationDate: Installed on 2019-02-15 (4 days ago)
InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190214)
SourcePackage: acpi-support
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
fossfreedom (fossfreedom) wrote :
Revision history for this message
Steve Langasek (vorlon) wrote :

The failure is in the acpid package, because for some reason the service is failing start. As a package included in the default install, we should be ensuring that the unit does not fail to start (and therefore the system is not considered degraded by systemd). Reassigning to acpid.

affects: acpi-support (Ubuntu) → acpid (Ubuntu)
Revision history for this message
Ahmad Mushtaq (ahmadmushtaq110) wrote :

hello. I am facing a similar one. is there any update on this issue? where can i follow it? thanks

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in acpid (Ubuntu):
status: New → Confirmed
Revision history for this message
alex (astein58) wrote :

I'm affected by this also.
This occurred during LTS dist-upgrade to 18.04 on a physical computer with very basic configuration.

Any ideas how to solve this?

Thanks

Revision history for this message
Christoph Roeder (brightdroid) wrote :

Also having this issue while installing "kubuntu-desktop" on top of an minimal installed (new) ubuntu 18.04.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.