Bug 1087616

Summary: Update of beep overwrites modprobe config with default, disabling speaker.
Product: [Fedora] Fedora Reporter: Joost Ruijsch <joost>
Component: beepAssignee: Hans Ulrich Niedermann <rhbugs>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 23CC: rhbugs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: beep-1.3-11.fc22 beep-1.3-11.fc23 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-16 22:25:53 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 Joost Ruijsch 2014-04-14 20:13:52 UTC
Description of problem:
When beep rpm is updated, it overwrites /etc/modprobe.d/beep.conf with default, disabling pc speaker.
I need beeps for my headless server to signal events like (re)boot. I get worried when it stays silent when I reboot after an upgrade. 

Version-Release number of selected component (if applicable):
Probably all versions since the past year or two.
last tried beep-1.3-7.fc20.i686

How reproducible:
always

Steps to Reproduce:
1. edit /etc/modprobe.d/beep.conf and uncomment the alias line to enable speaker on boot.
2. yum reinstall beep
3. check /etc/modprobe.d/beep.conf

Actual results:
The file reverted back to default.

Expected results:
Should leave beep.conf untouched

Additional info:
There is no error on reinstall, but I remember with one of the previous updates there was. It was something like "unable to read 119 bytes from /etc/modprobe.d/beep.conf", while the actual file was 1 or 2 bytes shorter. I guess this means it assumes the file does not exist and it is recreated.

Comment 1 Fedora End Of Life 2015-05-29 11:34:13 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Joost Ruijsch 2015-05-29 18:16:10 UTC
Likely cause:

In the beep.spec file the line:
%attr(0644,root,root) %{_sysconfdir}/modprobe.d/beep.conf

should probably be changed to:
%config(noreplace) %attr(0644,root,root) %{_sysconfdir}/modprobe.d/beep.conf

Since this has not changed even in Rawhide, I bumped the version.

And maybe change beep-modprobe.conf to have speaker enabled by default?

Comment 3 Jan Kurik 2015-07-15 14:41:22 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23

Comment 4 Fedora Update System 2016-01-17 23:40:12 UTC
beep-1.3-11.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2016-ee8b686332

Comment 5 Fedora Update System 2016-01-20 03:54:24 UTC
beep-1.3-11.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-ee8b686332

Comment 6 Fedora Update System 2016-01-20 03:55:34 UTC
beep-1.3-11.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-3b3aba1c20

Comment 7 Joost Ruijsch 2016-04-20 19:00:31 UTC
Works ok.
It has been in testing for 3 months, perhaps push to stable?
Thanks.

Comment 8 Fedora Update System 2016-05-16 22:25:51 UTC
beep-1.3-11.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2016-05-16 22:28:21 UTC
beep-1.3-11.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.