Bug#230160: marked as done (~/.gtkrc-2.0 no longer honored?)
Debian Bug Tracking System
owner@bugs.debian.org
Thu, 04 Mar 2004 09:18:06 -0800
Your message dated Fri, 05 Mar 2004 02:04:20 +0900 (JST)
with message-id <20040305.020420.78701097.tagoh@debian.org>
and subject line Bug#230160: ~/.gtkrc-2.0 no longer honored?
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 28 Jan 2004 23:11:06 +0000
>From mdz@alcor.net Wed Jan 28 15:11:06 2004
Return-path: <mdz@alcor.net>
Received: from mta10.adelphia.net [68.168.78.202]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Alypu-00023G-00; Wed, 28 Jan 2004 15:11:06 -0800
Received: from mizar.alcor.net ([68.64.159.24]) by mta10.adelphia.net
(InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP
id <20040128231037.LNOM9070.mta10.adelphia.net@mizar.alcor.net>
for <submit@bugs.debian.org>; Wed, 28 Jan 2004 18:10:37 -0500
Received: from mdz by mizar.alcor.net with local (Exim 4.30)
id 1AlypH-0008Nr-OQ
for submit@bugs.debian.org; Wed, 28 Jan 2004 15:10:27 -0800
Date: Wed, 28 Jan 2004 15:10:27 -0800
From: Matt Zimmerman <mdz@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: ~/.gtkrc-2.0 no longer honored?
Message-ID: <20040128231027.GA32078@alcor.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Reportbug-Version: 2.39
User-Agent: Mutt/1.5.5.1+cvs20040105i
Sender: Matt Zimmerman <mdz@alcor.net>
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_01_27
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no
version=2.60-bugs.debian.org_2004_01_27
X-Spam-Level:
Package: libgtk2.0-0
Version: 2.2.4-3
Severity: normal
I do not know whether gtk+ itself is at fault, but this seems like a good
starting point. For some time now I have had:
mizar:[~] cat ~/.gtkrc-2.0
gtk-key-theme-name = "Emacs"
gtk-cursor-blink = 0
gtk-can-change-accels = 1
as documented in the README (release notes), and this made life livable.
Sometime recently in unstable, these settings stopped being honored, and now
gtk applications do not give me Emacs keybindings, do not allow me to change
keyboard accelerators using drop-down menus, and the cursor blinks.
strace tells me that the file is still read, but apparently these settings
are not taking effect.
I see a note about key bindings (but not the other two items) in
README.Debian, but it only refers to GNOME 2, and I don't run any version of
GNOME. Furthermore, that note has been there for most of the past year, and
this problem only surfaced recently.
-- System Information:
Debian Release: unstable
Architecture: i386
Kernel: Linux mizar 2.4.24-deb1-skas3-1 #1 Thu Jan 8 11:19:59 PST 2004 i686
Locale: LANG=en_US, LC_CTYPE=en_US
Versions of packages libgtk2.0-0 depends on:
ii libatk1.0-0 1.4.1-1 The ATK accessibility toolkit
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
ii libfontconfig1 2.2.1-13 generic font configuration library
ii libfreetype6 2.1.7-2 FreeType 2 font engine, shared lib
ii libglib2.0-0 2.2.3-1 The GLib library of C routines
ii libgtk2.0-common 2.2.4-3 Common files for the GTK+ graphica
ii libjpeg62 6b-9 The Independent JPEG Group's JPEG
ii libpango1.0-0 1.2.5-2.1 Layout and rendering of internatio
ii libpng12-0 1.2.5.0-4 PNG library - runtime
ii libtiff3g 3.5.7-2 Tag Image File Format library
ii libxft2 2.1.2-5 FreeType-based font drawing librar
ii libxrender1 0.8.3-5 X Rendering Extension client libra
ii xlibs 4.2.1-15 X Window System client libraries
ii zlib1g 1:1.2.1-3 compression library - runtime
-- no debconf information
--
- mdz
---------------------------------------
Received: (at 230160-done) by bugs.debian.org; 4 Mar 2004 17:04:24 +0000
>From tagoh@debian.org Thu Mar 04 09:04:24 2004
Return-path: <tagoh@debian.org>
Received: from 37.1.111.219.st.bbexcite.jp (mail.gclab.org) [219.111.1.37] (postfix)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AywGm-0000M6-00; Thu, 04 Mar 2004 09:04:24 -0800
Received: from localhost (chulip [127.0.0.1])
by mail.gclab.org (Postfix) with ESMTP
id 0223F11285E; Fri, 5 Mar 2004 02:02:52 +0900 (JST)
Date: Fri, 05 Mar 2004 02:04:20 +0900 (JST)
Message-Id: <20040305.020420.78701097.tagoh@debian.org>
To: mdz@debian.org
Cc: 230160-done@bugs.debian.org
Subject: Re: Bug#230160: ~/.gtkrc-2.0 no longer honored?
From: Akira TAGOH <tagoh@debian.org>
In-Reply-To: <20040304162547.GX28592@alcor.net>
References: <20040128231027.GA32078@alcor.net>
<20040304.180451.39156457.tagoh@debian.org>
<20040304162547.GX28592@alcor.net>
Organization: Debian Project
X-PGP-key-URL: http://keyring.debian.org:11371/pks/lookup?op=get&search=0x39CCF0C7
X-fingerprint: 2963 D60B 2CBA 075C 9BCC 8376 FCF6 DD45 39CC F0C7
X-URL: http://tagoh.jp/
X-Attribution: AT
X-Mailer: Mew version 4.0.63 on Emacs 21.3.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Delivered-To: 230160-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_01
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=HAS_BUG_NUMBER autolearn=no
version=2.60-bugs.debian.org_2004_03_01
X-Spam-Level:
>>>>> On Thu, 4 Mar 2004 08:25:47 -0800,
>>>>> "MZ" == Matt Zimmerman <mdz@debian.org> wrote:
MZ> The problem has come and gone a few times since I filed this bug. I haven't
MZ> noticed whether it coincided with software upgrades, running programs, or
MZ> anything else.
MZ> I guess close this bug, and if I see it again before it is archived, I will
MZ> reopen it. Is there anything I should look for if it happens again?
Ok. closing this now. well, if you see this again, please
make sure that gnome-settings-daemon isn't running. if it
still appears then, please give me how to reproduce like I
mentioned in previous mail if theare are the steps, and let
me know which application it happens on.
Thanks,
--
Akira TAGOH