Re: Garbled xterm and gnome-terminal under gnome-session (2.24.2-1) under OSX 10.5.5

On Fri, Dec 19, 2008 at 08:22:05AM -0500, Alexander Hansen wrote:
> 
> On Dec 19, 2008, at 12:38 AM, rbambery wrote:
> 
> >
> >On Dec 18, 2008, at 3:20 AM, Alexander Hansen wrote:
> >
> >>
> >>On Dec 17, 2008, at 8:44 PM, rbambery wrote:
> >>
> >>><<Removed>>
> >
> >>Try the workaround discussed here and in succeeding messages:
> >>
> >>http://thread.gmane.org/gmane.os.macosx.fink.user/27224/focus=2165
> >
> >Thanks for the help.
> >
> >I tried following Martin Costabel's suggested steps.
> >	I suggest therefore the following procedure:
> >
> >	1. Quit X11 and move ~/.xinitrc out of the way. Then run
> >
> >   	xmodmap -pke > ~/.Xmodmap
> >
> >  	 (This will start X11 again.)
> >
> >	2. Clean your config files:
> >
> >   	rm -rf ~/.gconf* ~/.gnome2*
> >
> >	3. Run the gnome-settings-daemon:
> >
> >   	/sw/lib/control-center/gnome-settings-daemon
> >
> >	This will open a window where you can choose .Xmodmap, click on  
> >"+Load"
> >	and then "OK".
> >
> >	 From then on, your gnome keymap should be OK.
> >Steps 1 and 2 worked but step 3 doesn't since /sw/lib/control-center  
> >doesn't
> >exist, both on the PowerPC G5 and Intel versions.
> The Intel and PowerPC versions _should_ be the same, so that's not  
> unexpected.
> >Consequently, I performed his "uglier step":
> >	The ugly hack is to prevent the loading of the garbled keymaps by  
> >simply
> >	moving the whole directory /sw/share/xmodmap out of the way. There   
> >may
> >	then be an error message about not finding some file, but at least  
> >the
> >	keymap is not destroyed.
> >I copied the xmodmap.us-mac from the old gnome (on MacOSX 10.4.11) / 
> >sw/share/xmodmap
> >into the empty /sw/share/xmodmap directory on my new 10.5.5 tree.
> >
> >Finally I discovered the settings daemon under:
> >/sw/lib/gnome-settings-daemon/gnome-settings-daemon
> >When I ran it, no window opened as he described in step 3, but the  
> >gnome-session started up
> >as it always did before and the terminal keys worked properly.  
> >That's when I realized that
> >I did not get my .xinitrc out of the way.
> >
> >But now everything works correctly. I'm not sure whether the sole  
> >entry in
> >/sw/share/xmodmap/xmodap.us-mac is working or if the local .Xmodmap
> >is working but I'm leaving it alone for now.
> >
> >I've backed up both of the xmodmaps so that if somehow I forget and  
> >update
> >the control-center later on and it blows away my fixes I should be  
> >able to get
> >back up quickly with this procedure.
> >
> >Ray
> >
> >
> 
> 
> I'll put this back on the list, to provide another reference for this  
> issue.
> 
> Item 3 in Martin's steps should be amended to
> 
> /sw/lib/gnome-settings-daemon/gnome-settings-daemon
> 
> for the GNOME packages in unstable.

Now that I think that whole section of packages has come up to
consistent GNOME2.24, let's see if we can fix this mess. If there are
files that are totally useless and cause problems if used, let's kill
them. If there's a file that should replace them or a default that
should be set, let's get that into the package. If things work but
then there's a best-practices to make things work well or a weird
corner case to avoid, let's get it into DescUsage or Fink FAQ.

dan

-- 
Daniel Macks
[email protected]
http://www.netspace.org/~dmacks


------------------------------------------------------------------------------