Bug 607051 - Keyboard bell settings don't apply to keyboards.
Summary: Keyboard bell settings don't apply to keyboards.
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: xorg-x11-server   
(Show other bugs)
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Peter Hutterer
QA Contact: desktop-bugs@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-23 03:24 UTC by Peter Hutterer
Modified: 2010-11-15 13:46 UTC (History)
1 user (show)

Fixed In Version: xorg-x11-server-1.7.7-16.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-15 13:46:43 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Peter Hutterer 2010-06-23 03:24:57 UTC
Description of problem:
Typo in ProcChangeKeyboardControl prevents a changed bell from actually feeding down to the slave devices. Result is that the settings never apply to the actual keyboards.

Version-Release number of selected component (if applicable):

How reproducible:
See http://bugs.freedesktop.org/show_bug.cgi?id=27926

Additional info:

Comment 1 RHEL Product and Program Management 2010-06-23 03:42:51 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for

Comment 2 Peter Hutterer 2010-06-29 00:30:58 UTC

xorg-x11-server-1.7.7-16.el6 is available in brew.

Comment 4 Vladimir Benes 2010-11-12 16:12:56 UTC
  1. Start a fresh X.org server:

  xinit /usr/bin/xterm -- :1

  2. Play the bell:

  xset b 50 400; printf '\a'

  3. Repeat with 800 instead of 400.

those frequencies are different now.

Comment 5 releng-rhel@redhat.com 2010-11-15 13:46:43 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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