Bug 2296943 - Disabled by default videoconf configuration requires vbetool which is not available in Fedora
Summary: Disabled by default videoconf configuration requires vbetool which is not ava...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: acpid
Version: 40
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-07-09 21:35 UTC by Maksym Hazevych
Modified: 2024-08-21 03:07 UTC (History)
2 users (show)

Fixed In Version: acpid-2.0.34-10.fc41 acpid-2.0.34-10.fc40
Clone Of:
Environment:
Last Closed: 2024-08-12 16:27:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Maksym Hazevych 2024-07-09 21:35:46 UTC
The `acpid` package provides default configuration in `/etc/acpi/events/videoconf`. The file's content is commented out, but it also contains an instruction to "uncomment if your laptop display stays blank after you close and open the lid."

The problem is, the configuration will not work if you uncomment it, because it tries to run `/usr/sbin/vbetool` which is not available in Fedora's repositories.

Reproducible: Always

Steps to Reproduce:
1. Install acpid
2. See /etc/acpi/events/videoconf
3. See it reference /usr/sbin/vbetool
4. Run `which /usr/sbin/vbetool` to receive `no vbetool in (/usr/sbin)` output
5. Look at the [vbetool package](https://src.fedoraproject.org/rpms/vbetool) to see that it is retired for a very long time.

Comment 1 Jaroslav Škarvada 2024-08-01 10:51:17 UTC
The vbetool was dropped long time ago (IIRC F17), the message from the dist-git:
> Suspend not supported under UMS. Not installed by default since F13.

IMHO with the KMS and other things I think vbetool is outdated - if you have problem with video after suspend, it's very probably kernel driver issue and should be reported against kernel.

Also this is not acpid downstream bug - missing 3rd party tool that is mentioned in one example file. Maybe this could be reported upstream, because the vbetool is very probably outdated in recent distros.

But if you really need vbetool, you can still package it and maintain.

Comment 2 Maksym Hazevych 2024-08-01 11:41:47 UTC
I didn't mean to ask for vbetool, I meant to ask to either remove the example, or leave a sufficient note to explain that it will not work on Fedora.

> … this is not acpid downstream bug … Maybe this could be reported upstream

Looking at the upstream source code, it doesn't have the same configuration file. It has a different set of example configuration files, and none contain any reference to vbetool

Comment 3 Fedora Update System 2024-08-12 14:39:28 UTC
FEDORA-2024-875f7abff0 (acpid-2.0.34-10.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-875f7abff0

Comment 4 Fedora Update System 2024-08-12 15:46:53 UTC
FEDORA-2024-c4fecc8c65 (acpid-2.0.34-10.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-c4fecc8c65

Comment 5 Fedora Update System 2024-08-12 16:27:10 UTC
FEDORA-2024-875f7abff0 (acpid-2.0.34-10.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Fedora Update System 2024-08-13 01:32:49 UTC
FEDORA-2024-c4fecc8c65 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-c4fecc8c65`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-c4fecc8c65

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2024-08-21 03:07:51 UTC
FEDORA-2024-c4fecc8c65 (acpid-2.0.34-10.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.