From: Richard C. <rc...@gm...> - 2008-07-31 14:30:34
|
On Wed, Jul 23, 2008 at 10:15 PM, Richard Cobbe <rc...@gm...> wrote: > On Wed, Jul 23, 2008 at 3:48 PM, Richard Cobbe <rc...@gm...> wrote: >> After updating the Gnome packages over the weekend, I'm now having >> severe difficulty with gnome-control-center 2.20.3-2. > > Ok. After an extraordinarily frustrating evening, I believe I have a > workaround. > > For some reason I don't understand, the version of > gnome-settings-daemon that I got in my last "fink update-all" replaces > the X keyboard mapping automatically on startup, and the one it > installs has no relationship to reality. Well, my workaround mostly solves the problem, but it's not perfect. Essentially, I have X11.app run a script on startup, which contains in part the following commands: /sw/lib/control-center/gnome-settings-daemon & sleep 8 /usr/X11/bin/xmodmap ~/.xmodmaprc /usr/X11/bin/uxterm & The problem, of course, is that the 8-second delay on the second line is just a guess. Because gnome-settings-daemon runs in the background, and because it doesn't install the keymap immediately upon starting up, there's no way for me to tell exactly when it installs the bogus keymap. So I have to wait, and I have to guess how long to wait. 8 seconds, as above, is *usually* enough, but not always, and I've had to add an entry to X11's Applications menu to reload the keymap. So X11 is usable, but I have to go through this song-and-dance every time I start the server. I could make sleep's argument larger, but then it would take that much longer to start the X server, and I'd prefer to avoid that. Ideally, I shouldn't have to do any of this. There really ought to be some way to tell gnome-settings-daemon *not* to load a keymap on startup, but I can't find it. I've even moved all my gnome configuration files---or at least, all the ones I know about---out of the way and restarted X, but I still get this behavior. Has anyone else seen this behavior? Does anyone have any ideas about how to fix this at the source, rather than slapping an imperfect band-aid on the problem? I've tried googling for other problems with gnome and keyboards, but I haven't found anything related to my problem. Is it worth posting to a Gnome discussion forum about this? Or are they likely to say "we don't support Fink builds"? I'd *really* like to fix this problem at its source, if at all possible. Thanks, Richard |