From owner-freebsd-gnome@FreeBSD.ORG Mon Apr 7 15:52:51 2008 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3A91106566C for ; Mon, 7 Apr 2008 15:52:51 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (merlin.alerce.com [64.62.142.94]) by mx1.freebsd.org (Postfix) with ESMTP id AEF5F8FC16 for ; Mon, 7 Apr 2008 15:52:51 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id 5099333C62 for ; Mon, 7 Apr 2008 08:52:51 -0700 (PDT) Received: from postfix.alerce.com (w092.z064001164.sjc-ca.dsl.cnc.net [64.1.164.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by merlin.alerce.com (Postfix) with ESMTP id 2A66D33C5B for ; Mon, 7 Apr 2008 08:52:51 -0700 (PDT) Received: by postfix.alerce.com (Postfix, from userid 501) id 2116440E506; Mon, 7 Apr 2008 08:52:45 -0700 (PDT) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18426.17229.62137.145707@almost.alerce.com> Date: Mon, 7 Apr 2008 08:52:45 -0700 To: freebsd-gnome@freebsd.org X-Mailer: VM 7.19 under Emacs 22.1.50.1 X-Virus-Scanned: ClamAV using ClamSMTP Subject: keyboard setting problem when gnome started via startx X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hartzell@alerce.com List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Apr 2008 15:52:51 -0000 Hi all, There are at least a couple of us that are having a problem where changes that we make in the keyboard options dialog aren't automagically applied when we start our gnome session via startx/.xinitrc. There's an open bug at http://bugzilla.gnome.org/show_bug.cgi?id=483182 I'm curious if anyone else is seeing this, or if anything comes to mind about how our gnome-session or hal or ??? works that might be causing problematic behaviour in FreeBSD. Thanks, g.