[26001] in Athena Bugs
Re: Problem with gnome-terminal-2.2.2-1 in Athena 9.3.11
daemon@ATHENA.MIT.EDU (Greg Hudson)
Fri Aug 27 00:43:17 2004
From: Greg Hudson <ghudson@mit.edu>
To: Tom Cavin <cavin@mit.edu>
In-Reply-To: <16686.46265.400292.532793@lap1-wccf.mit.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1093581788.19888.22.camel@egyptian-gods.mit.edu>
Mime-Version: 1.0
Date: Fri, 27 Aug 2004 00:43:08 -0400
cc: Athena Bugs list <bugs@mit.edu>
Errors-To: bugs-bounces@mit.edu
Odd.
First, 9.3.8 and 9.3.11 both have a gnome-terminal in /usr/athena/bin,
so the native gnome-terminal-2.2.2-1 package is irrelevant. And neither
the native nor the Athena gnome-terminal RPMs were upgraded in 9.3.11.
The most relevant difference in 9.3.11 is a change to the way we fire up
gnome-settings-daemon, which reads GConf settings and sets X server
settings. Previously, we just fired up gnome-settings-daemon in the
background, which means sometimes gnome-terminal wouldn't get the
benefit of the X settings (and would generally get fonts wrong as a
result). Now, we use bonobo to fire up gnome-settings-daemon, which
ensures that it is running before we move on.
But there are several reasons why this doesn't seem to explain your
problem. First, while gnome-settings-daemon deals with keyboard
settings, they are just the basic ones relating to key repeat rate and
such, not layout. Second, the change in 9.3.11 should make the initial
gnome-terminal process more consistent with later processes, not less
consistent.
On the other hand, it's possible that the change in 9.3.11 affects the
timing of process startup at login, triggering some kind of race
condition in your dotfiles. For instance, is it really only the initial
gnome-terminal process which is affected, or is it any gnome-terminal
process which you start before issuing the setxkbmap command?
