Bug 2338425

Summary: zcfan.service: Failed at step EXEC spawning /usr/local/bin/zcfan: No such file or directory
Product: [Fedora] Fedora EPEL Reporter: Brendan Mchugh <bmchugh>
Component: zcfanAssignee: Davide Cavalca <davide>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: epel9CC: davide, michel
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: zcfan-1.4.0-3.el9 zcfan-1.4.0-3.el8 zcfan-1.4.0-3.fc41 zcfan-1.4.0-3.fc40 zcfan-1.4.0-3.el10_1 zcfan-1.4.0-3.el10_0 zcfan-1.4.0-3.fc42 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-03-05 00:43:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Brendan Mchugh 2025-01-16 13:55:52 UTC
Description of problem:
zcfan.service: Failed at step EXEC spawning /usr/local/bin/zcfan: No such file or directory

The /usr/lib/systemd/system/zcfan.service has ExecStart=/usr/local/bin/zcfan rather than the expected /usr/bin/zcfan.

rpm -ql zcfan
/usr/bin/zcfan
/usr/lib/.build-id
/usr/lib/.build-id/e4
/usr/lib/.build-id/e4/b77fc57ed4b12529e5e37b80392740d04fe1c2
/usr/lib/systemd/system/zcfan.service
/usr/share/doc/zcfan
/usr/share/doc/zcfan/README.md
/usr/share/licenses/zcfan
/usr/share/licenses/zcfan/LICENSE
/usr/share/man/man1/zcfan.1.gz


Version-Release number of selected component (if applicable):
zcfan-1.4.0-1.el9

How reproducible:
Always

Steps to Reproduce:
1. Install/Upgrade to zcfan-1.4.0-1.el9
2. Try to start Service
3.

Actual results:
Jan 16 14:53:57 thinkpad systemd[30303]: zcfan.service: Failed at step EXEC spawning /usr/local/bin/zcfan: No such file or directory
Jan 16 14:42:19 thinkpad systemd[1]: zcfan.service: Failed with result 'exit-code'.
Jan 16 14:42:19 thinkpad systemd[1]: zcfan.service: Scheduled restart job, restart counter is at 5.
Jan 16 14:42:19 thinkpad systemd[1]: Stopped Zero-configuration fan control for ThinkPad.
Jan 16 14:42:19 thinkpad systemd[1]: zcfan.service: Start request repeated too quickly.
Jan 16 14:42:19 thinkpad systemd[1]: zcfan.service: Failed with result 'exit-code'.
Jan 16 14:42:19 thinkpad systemd[1]: Failed to start Zero-configuration fan control for ThinkPad.


Expected results:
Service runs as it is pointing to the correct binary location of /usr/bin/zcfan.

Additional info:

Comment 1 Fedora Update System 2025-02-24 20:01:22 UTC
FEDORA-EPEL-2025-27749d9ddc (zcfan-1.4.0-3.el10_0) has been submitted as an update to Fedora EPEL 10.0.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-27749d9ddc

Comment 2 Fedora Update System 2025-02-24 20:01:23 UTC
FEDORA-2025-a95e295bcf (zcfan-1.4.0-3.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-a95e295bcf

Comment 3 Fedora Update System 2025-02-24 20:01:24 UTC
FEDORA-EPEL-2025-433032c4cd (zcfan-1.4.0-3.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-433032c4cd

Comment 4 Fedora Update System 2025-02-24 20:01:25 UTC
FEDORA-2025-1049a6a2a7 (zcfan-1.4.0-3.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-1049a6a2a7

Comment 5 Fedora Update System 2025-02-24 20:01:25 UTC
FEDORA-EPEL-2025-bf743171a0 (zcfan-1.4.0-3.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-bf743171a0

Comment 6 Fedora Update System 2025-02-25 00:21:29 UTC
FEDORA-EPEL-2025-433032c4cd has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-433032c4cd

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

Comment 7 Fedora Update System 2025-02-25 01:06:25 UTC
FEDORA-2025-a95e295bcf has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-a95e295bcf`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-a95e295bcf

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

Comment 8 Fedora Update System 2025-02-25 01:23:32 UTC
FEDORA-EPEL-2025-bf743171a0 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-bf743171a0

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

Comment 9 Fedora Update System 2025-02-25 01:31:56 UTC
FEDORA-2025-d1aee6d484 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-2025-d1aee6d484`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-d1aee6d484

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

Comment 10 Fedora Update System 2025-02-25 01:42:34 UTC
FEDORA-2025-1049a6a2a7 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-1049a6a2a7`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-1049a6a2a7

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

Comment 11 Fedora Update System 2025-02-25 02:40:31 UTC
FEDORA-EPEL-2025-d123615671 has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-d123615671

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

Comment 12 Fedora Update System 2025-02-25 02:43:57 UTC
FEDORA-EPEL-2025-27749d9ddc has been pushed to the Fedora EPEL 10.0 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-27749d9ddc

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

Comment 13 Fedora Update System 2025-03-05 00:43:45 UTC
FEDORA-EPEL-2025-433032c4cd (zcfan-1.4.0-3.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2025-03-05 01:07:22 UTC
FEDORA-EPEL-2025-bf743171a0 (zcfan-1.4.0-3.el8) has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2025-03-05 01:14:44 UTC
FEDORA-2025-1049a6a2a7 (zcfan-1.4.0-3.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2025-03-05 01:39:14 UTC
FEDORA-2025-d1aee6d484 (zcfan-1.4.0-3.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 17 Fedora Update System 2025-03-05 02:41:20 UTC
FEDORA-EPEL-2025-d123615671 (zcfan-1.4.0-3.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 18 Fedora Update System 2025-03-05 02:59:12 UTC
FEDORA-EPEL-2025-27749d9ddc (zcfan-1.4.0-3.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 19 Fedora Update System 2025-03-15 00:29:49 UTC
FEDORA-2025-a95e295bcf (zcfan-1.4.0-3.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.