acpid missing - fresh install of Enlightenment on Arch #23

Closed
opened 2022-10-31 18:20:56 -07:00 by CNRO · 2 comments

Upon first boot of fresh install of current versions of both Arch and Enlightenment, after the preliminary Englightenment configuration prompts when reaching the desktop, a warning pops up telling me acpid cannot load.

I am not sure if this is a bug per-se, since it may be intentionally left out, and the warning only designed to remind users of this functionality and to install on a systems where it is required; however on a previous release (circa 2019) this issue did not appear

My system is:
Lenovo G780
Arch Linux x86_64
Kernal 6.0.6-arch1-1
WM: Enlightenment
CPU: Intel i5-3210M
GPU: 3rd Gen Core processor

I have produced issue 2 times, both times were from current versions of Arch and Enlightenment

  1. Arch installer with:
    #pacstrap -K /mnt base linux linux-firmware vim nano

followed by chroot
#pacman -S networkmanager
#systemctl enable NetworkManager

and reboot into the system.

  1. Once in the system, update and install Enlightenment:
    #pacman -Syu
    #pacman -S xorg lightdm lightdm-gtk-greeter efl enlightenment terminology
    #systemctl enable lightdm

and reboot into lightdm + Enlightenment

  1. Followed the Enlightenment first run configuration prompts and load into the desktop environment and the ACPID warning appears automatically, first thing

  2. Issue solved
    #pacman -S acpid
    #systemctl enable acpid.service
    #systemctl start acpid.service

_
Sorry I do not have logs or know what is a trace extract

Upon first boot of fresh install of current versions of both Arch and Enlightenment, after the preliminary Englightenment configuration prompts when reaching the desktop, a warning pops up telling me acpid cannot load. I am not sure if this is a bug per-se, since it may be intentionally left out, and the warning only designed to remind users of this functionality and to install on a systems where it is required; however on a previous release (circa 2019) this issue did not appear My system is: Lenovo G780 Arch Linux x86_64 Kernal 6.0.6-arch1-1 WM: Enlightenment CPU: Intel i5-3210M GPU: 3rd Gen Core processor I have produced issue 2 times, both times were from current versions of Arch and Enlightenment 1) Arch installer with: #pacstrap -K /mnt base linux linux-firmware vim nano followed by chroot #pacman -S networkmanager #systemctl enable NetworkManager and reboot into the system. 2) Once in the system, update and install Enlightenment: #pacman -Syu #pacman -S xorg lightdm lightdm-gtk-greeter efl enlightenment terminology #systemctl enable lightdm and reboot into lightdm + Enlightenment 3) Followed the Enlightenment first run configuration prompts and load into the desktop environment and the ACPID warning appears automatically, first thing 4) Issue solved #pacman -S acpid #systemctl enable acpid.service #systemctl start acpid.service _ Sorry I do not have logs or know what is a trace extract
Owner

Yes - I added the dialog to detect if acpid would be needed and remind the user in e 0.25 - it didnt check before then and just assumed you'd do the right thing and e would silently just lose features and not let you know. It's not a bug. it's intended. no - it's not a REQUIREMENT of the e package as not all systems use ACPI. for example on arm systems like raspberry pi's - no ACPI. If you go to an old enough x86 PC it will also not have ACPI. So it's detected at runtime and if the system appears to have ACPI support - e will complain to remind you to install it. acpidd is listed as an optdepends which is technically correct.

Yes - I added the dialog to detect if acpid would be needed and remind the user in e 0.25 - it didnt check before then and just assumed you'd do the right thing and e would silently just lose features and not let you know. It's not a bug. it's intended. no - it's not a REQUIREMENT of the e package as not all systems use ACPI. for example on arm systems like raspberry pi's - no ACPI. If you go to an old enough x86 PC it will also not have ACPI. So it's detected at runtime and if the system appears to have ACPI support - e will complain to remind you to install it. acpidd is listed as an optdepends which is technically correct.
Owner

Yes - I added the dialog to detect if acpid would be needed and remind the user in e 0.25 - it didnt check before then and just assumed you'd do the right thing and e would silently just lose features and not let you know. It's not a bug. it's intended. no - it's not a REQUIREMENT of the e package as not all systems use ACPI. for example on arm systems like raspberry pi's - no ACPI. If you go to an old enough x86 PC it will also not have ACPI. So it's detected at runtime and if the system appears to have ACPI support - e will complain to remind you to install it. acpidd is listed as an optdepends which is technically correct.

Yes - I added the dialog to detect if acpid would be needed and remind the user in e 0.25 - it didnt check before then and just assumed you'd do the right thing and e would silently just lose features and not let you know. It's not a bug. it's intended. no - it's not a REQUIREMENT of the e package as not all systems use ACPI. for example on arm systems like raspberry pi's - no ACPI. If you go to an old enough x86 PC it will also not have ACPI. So it's detected at runtime and if the system appears to have ACPI support - e will complain to remind you to install it. acpidd is listed as an optdepends which is technically correct.
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: enlightenment/enlightenment#23
No description provided.