From owner-freebsd-x11@FreeBSD.ORG Wed Jan 4 09:14:44 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 00F36106566C for ; Wed, 4 Jan 2012 09:14:43 +0000 (UTC) (envelope-from joel@vnode.se) Received: from mail.vnode.se (mail.vnode.se [62.119.52.80]) by mx1.freebsd.org (Postfix) with ESMTP id A238F8FC12 for ; Wed, 4 Jan 2012 09:14:42 +0000 (UTC) Received: from mail.vnode.se (localhost [127.0.0.1]) by mail.vnode.se (Postfix) with ESMTP id 2841EE3F07B; Wed, 4 Jan 2012 09:59:40 +0100 (CET) X-Virus-Scanned: amavisd-new at vnode.se Received: from mail.vnode.se ([127.0.0.1]) by mail.vnode.se (mail.vnode.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qps6-03TDfnm; Wed, 4 Jan 2012 09:59:37 +0100 (CET) Received: from goofy01.vnodelab.local (unknown [212.247.52.12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.vnode.se (Postfix) with ESMTPSA id 61BEFE3F079; Wed, 4 Jan 2012 09:59:37 +0100 (CET) Date: Wed, 4 Jan 2012 09:59:35 +0100 From: Joel Dahl To: Benjamin Kaduk Message-ID: <20120104085935.GE61584@goofy01.vnodelab.local> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-x11@freebsd.org 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 09:14:44 -0000 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). -- Joel