From owner-freebsd-x11@FreeBSD.ORG Wed Jan 4 14:01:54 2012 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7ACFF106566B for ; Wed, 4 Jan 2012 14:01:54 +0000 (UTC) (envelope-from stephen@missouri.edu) Received: from wilberforce.math.missouri.edu (wilberforce.math.missouri.edu [128.206.184.213]) by mx1.freebsd.org (Postfix) with ESMTP id 382EC8FC1A for ; Wed, 4 Jan 2012 14:01:54 +0000 (UTC) Received: from [127.0.0.1] (wilberforce.math.missouri.edu [128.206.184.213]) by wilberforce.math.missouri.edu (8.14.5/8.14.5) with ESMTP id q04DdxTi012881; Wed, 4 Jan 2012 07:40:00 -0600 (CST) (envelope-from stephen@missouri.edu) Message-ID: <4F0456AF.40301@missouri.edu> Date: Wed, 04 Jan 2012 07:39:59 -0600 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.24) Gecko/20111108 Thunderbird/3.1.16 MIME-Version: 1.0 To: Joel Dahl References: <20120104085935.GE61584@goofy01.vnodelab.local> In-Reply-To: <20120104085935.GE61584@goofy01.vnodelab.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-x11@freebsd.org, Benjamin Kaduk Subject: Re: xset cannot disable bell? X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2012 14:01:54 -0000 On 01/04/2012 02:59 AM, Joel Dahl wrote: > On 04-01-2012 1:43, Benjamin Kaduk wrote: >> Hi all, >> >> I took a (long-overdue) ports upgrade a few days ago, and after rebuilding >> everything from scratch, I find that I can no longer disable the X bell >> with 'xset -b', either in my .xinitrc or from an xterm. Other >> permutations such as 'xset b off' and 'xset b 0 0 0' also have no effect. >> >> This is with: >> xset-1.2.2_1 User preference utility for X >> xterm-276_1 Terminal emulator for the X Window System >> xorg-7.5.1 X.Org complete distribution metaport >> xorg-apps-7.5.1 X.org apps meta-port >> xorg-cf-files-1.0.4 X.org cf files for use with imake builds >> xorg-docs-1.6,1 X.org documentation files >> xorg-drivers-7.5.1 X.org drivers meta-port >> xorg-fonts-100dpi-7.5.1 X.Org 100dpi bitmap fonts >> xorg-fonts-7.5.1 X.org fonts meta-port >> xorg-fonts-75dpi-7.5.1 X.Org 75dpi bitmap fonts >> xorg-fonts-cyrillic-7.5.1 X.Org Cyrillic bitmap fonts >> xorg-fonts-miscbitmaps-7.5.1 X.Org miscellaneous bitmap fonts >> xorg-fonts-truetype-7.5.1 X.Org TrueType fonts >> xorg-fonts-type1-7.5.1 X.Org Type1 fonts >> xorg-libraries-7.5.1 X.org libraries meta-port >> xorg-macros-1.15.0 X.Org development aclocal macros >> xorg-server-1.7.7_3,1 X.Org X server and related programs >> >> The base system is: >> FreeBSD hysteresis.mit.edu 9.0-CURRENT FreeBSD 9.0-CURRENT #29: Thu May 12 >> 23:38:56 EDT 2011 kaduk@hysteresis.mit.edu:/usr/obj/usr/src/sys/GENERIC >> amd64 >> from sources of 19 February (crikey, that's almost a year old!). >> >> Thoughts on whether updating the base system is likely to help, or further >> diagnostics to take? > > FWIW, I have the same problem with a more up-to-date current (rebuilt two > days ago). > This is a long shot. But did you try xkbset? (It is in the ports.)