Bug 25801 - Switching VT re-enables XBell(), ignoring 'xset b off'
Summary: Switching VT re-enables XBell(), ignoring 'xset b off'
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: 7.5 (2009.10)
Hardware: x86 (IA32) Linux (All)
: low normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
Whiteboard: 2012BRB_Reviewed
Depends on:
Blocks: xserver-1.13
  Show dependency treegraph
Reported: 2009-12-26 09:34 UTC by mark-freedesktop
Modified: 2018-06-12 18:43 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

xorg.conf (1.98 KB, text/plain)
2009-12-26 09:34 UTC, mark-freedesktop
no flags Details

Description mark-freedesktop 2009-12-26 09:34:58 UTC
Created attachment 32302 [details]

I disable beep using 'xset b off' command. When I switch to a console (using Ctrl-Alt-F1) and then switch back to X, the beep is re-enabled. It can be disabled again.

Also, potentially related, 'xet b off' in .xinitrc does not have any effect. It works if run at a later time.

I first noticed this problem around the update to xorg-server-1.7, and tested using the twm and fvwm window managers.


  xset b off
  exec twm
Comment 1 mark-freedesktop 2010-04-04 08:22:04 UTC
An update on this issue (updated to xorg-server-

Having looked into the problem in more detail, it is the bell generated using XBell() which is affected.

When 'xset b off' is issued, XBell() is silent. Switching to a console and back to results in XBell() making sound again.

Also, 'xset b off' in .xinitrc has no effect, but works at a later time.

I had some recent confusion using a recent xterm which used XKbBell(). Now ruling this out by calling XBell() directly.
Comment 3 Bryan Henderson 2011-03-23 20:09:36 UTC
I tracked this down far enough to know that the posting by Mark Hills mentioned above is in fact about this problem.  I too worked around it myself by cutting out the copy of the kbdfeed.ctrl, but this is almost certainly not the proper fix.

The posting by Alan Coopersmith is about a different problem, but both signify something fundamentally wrong with the keyboard master/slave and virtual core keyboard implementation.  But as I don't understand either of those concepts, I have no idea just what is wrong.
Comment 4 Adam Jackson 2018-06-12 18:43:22 UTC
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please file a new report if you continue to experience issues with a current server.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.