Hide Forgot
Description of problem: The default install of FC6 pre-release (https://www.redhat.com/archives/fedora-devel-list/2006-September/msg00921.html) specifies that gdm should play a sound when launching. However, the actual sound file field is left blank. This results in the default system bell being played instead, which on my particular notebook (Dell Latitude D620) is so loud you jump out of your seat. Steps to Reproduce: 1. Install the FC6Pre i386 on a Dell notebook (or any computer I would assume). 2. Proceed to the graphical login (gdm) 3. Jump out of your seat. Actual results: BEEP! Expected results: Silence or a themed .wav/.ogg sound. Additional info: This bug report was filed because Rahul Sundaram asked me to in a response to my FC6 vs Ubuntu 6.10 review: http://djst.org/blog/2006/10/03/fedora-core-6-vs-ubuntu-610/#comment-412
Other steps to verify this bug: 1. Install FC6Pre. 2. Select System > Administration > Login Screen. 3. Click the Accessibility tab 4. Notice how the "Login screen ready" checkbox is checked, but the file chosen is "(None)".
If you su to root, edit your modproble.conf file and then add the following line install pcspkr /bin/true and reboot, the noise will stop and you can sit quietly in your seat.
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer test releases. We're cleaning up the bug database and making sure important bug reports filed against these test releases don't get lost. It would be helpful if you could test this issue with a released version of Fedora or with the latest development / test release. Thanks for your help and for your patience. [This is a bulk message for all open FC5/FC6 test release bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
The information we've requested above is required in order to review this problem report further and diagnose/fix the issue if it is still present. Since there haven't been any updates to the report in quite a long time now after we've requested additional information, we're assuming the problem is either no longer present in our current OS release, or that there is no longer any interest in tracking the problem. Setting status to CANTFIX, however if you still experience this problem after updating to our latest Fedora Core release and are still interested in Red Hat tracking the issue, and assisting in troubleshooting the problem, please feel free to provide the information requested above, and reopen the report. Thank you in advance. (this message is mass message)