acpi-support prevents Groovy and Hirsute booting in LXC

Bug #1938088 reported by Nazar
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Canonical SSO provider
Invalid
Undecided
Unassigned
acpi-support (Ubuntu)
Fix Released
Undecided
Unassigned
Jammy
Fix Released
Undecided
Unassigned

Bug Description

Hi,

Installing ubuntu-desktop package in LXC containers of Groovy and Hirsute (no issues in Focal) will cause the installation process to stall for hours right after the acpi-support package with many timeout errors:

>Setting up acpi-support (0.143) ...
>Failed to restart acpid.service: Transport endpoint is not connected
>See system logs and 'systemctl status acpid.service' for details.
>invoke-rc.d: initscript acpid, action "restart" failed.
>Failed to get properties: Transport endpoint is not connected
>dpkg: error processing package acpi-support (--configure):
>installed acpi-support package post-installation script subprocess returned error exit status 1

When the installation process eventually ended in errors, specifically at the acpid package, repetitive errors can be seen in the /var/log/syslog:

>Condition check resulted in ACPI event daemon being skipped

After forcing the LXC container to restart, it will no longer boot up normally stuck at systemd-journald using 100% CPU usage. Figured out a quick dirty fix to this is to chroot or attach to the affected container then removed the acpi-support package. Immediately after removing this acpi-support package the boot up resumes till the desktop.

I can only find one reference online: https://forum.proxmox.com/threads/looking-to-install-ubuntu-desktop-on-proxmox-lxc-template-21-04.88175/

Thank you.

Daniel Manrique (roadmr)
Changed in canonical-identity-provider:
status: New → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in acpi-support (Ubuntu):
status: New → Confirmed
Revision history for this message
con (conloos) wrote :

I can confirm that behavior on lxd 4.23. I have to mask acpid and acpi-support to install kde in a container.

Revision history for this message
Steve Dodd (anarchetic) wrote (last edit ):

Hit the same thing trying to upgrade a focal container to jammy in systemd-nspawn :(

tags: added: fr-2165
Revision history for this message
con (conloos) wrote (last edit ):

So i found the source of the problem at: https://github.com/OpenNebula/one/issues/5504

Systemd disables acpid with the line: 'ConditionVirtualization=!container' since it recognizes that it is running in a container.
However, there is an error in the configuration file for acpid.path because the line is missing here. Hence the hint that the endpoint is missing.
In the acpi.path after the line: 'Description=ACPI Events Check' in the section [UNIT] ' create a new line with: 'ConditionVirtualization=!container' and then restart the unit.

So it is a problem of acpid and not acpi-support.

Steve Langasek (vorlon)
tags: added: rls-jj-incoming
tags: removed: rls-jj-incoming
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package acpi-support - 0.144

---------------
acpi-support (0.144) jammy; urgency=medium

  * Use dpkg-source format 3.0 (native)
  * debian/control: Drop obsolete DM-Upload-Allowed
  * Switch to debhelper 13 (version 5 is not supported any more)
  * Do not create empty /usr/bin directory (LP: #1374981)
  * Update debian/copyright
  * Do not fail to install if restarting acpid fails (LP: #1938088)
  * Drop unsupported architectures ia64 and lpia
  * Bump Standards-Version to 4.6.0

 -- Benjamin Drung <email address hidden> Thu, 14 Apr 2022 18:54:07 +0200

Changed in acpi-support (Ubuntu Jammy):
status: Confirmed → Fix Released
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.