Gentlepeople, Please forgive the user-ish question, but how do I cleanly revert from 2.3.0-rc4 to 2.2.2? I mistakenly installed the 2.3.0 variant after upgrading to 10.5.3, and have run into various issues (stuck ctrl and lack of .xinitrc invocation in particular). I noticed the file list in the .bom under the Receipts directory ... should I simply remove everything that's a file or an empty directory listed there and do a clean re-install of 2.2.2? Do I need to go back and install the virgin Leopard X11 package first? Is there a script hidden somewhere that can do this easily? Again, my most abject apologies for bugging the developers for such a dumb-user question! Thanks very much! - Jim
Well first of all, please report these issues and help get them fixed. ~/.xinitrc should be getting executed. Can you please tell me what the output of 'ps x | grep xinit' is. The stuck control keys issue exists in 2.2.x as well, unfortunately. You can just install the 2.2.2 package and you should be fine. --Jeremy On Jun 16, 2008, at 21:48, Jim Martin wrote:
Gentlepeople, Please forgive the user-ish question, but how do I cleanly revert from 2.3.0-rc4 to 2.2.2? I mistakenly installed the 2.3.0 variant after upgrading to 10.5.3, and have run into various issues (stuck ctrl and lack of .xinitrc invocation in particular). I noticed the file list in the .bom under the Receipts directory ... should I simply remove everything that's a file or an empty directory listed there and do a clean re-install of 2.2.2? Do I need to go back and install the virgin Leopard X11 package first? Is there a script hidden somewhere that can do this easily?
Again, my most abject apologies for bugging the developers for such a dumb-user question!
Thanks very much!
- Jim
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
On Jun 16, 2008, at 9:55 PM, Jeremy Huddleston wrote:
Well first of all, please report these issues and help get them fixed.
Understood ...
~/.xinitrc should be getting executed. Can you please tell me what the output of 'ps x | grep xinit' is.
dhcp-77% ps x | grep xinit 13525 ?? S 0:00.01 xinit /Users/jim/.xinitrc -- /usr/X11/bin/ X :0 13593 s001 S+ 0:00.00 grep xinit It looks like it's attempting to invoke it, but things aren't starting correctly. Where would errors be logged? The .xinitrc file is: #!/bin/sh userresources=$HOME/.Xresources usermodmap=$HOME/.Xmodmap sysresources=/usr/X11/lib/X11/xinit/.Xresources sysmodmap=/usr/X11/lib/X11/xinit/.Xmodmap # merge in defaults and keymaps if [ -f "$sysresources" ]; then xrdb -merge "$sysresources" fi if [ -f "$sysmodmap" ]; then xmodmap "$sysmodmap" fi if [ -f "$userresources" ]; then xrdb -merge "$userresources" fi if [ -f "$usermodmap" ]; then xmodmap "$usermodmap" fi # start some nice programs if [ -f ~/.Xclients ]; then sh ~/.Xclients fi exec quartz-wm And the .Xclients file reads: # Get some dimensions X11_WIDTH=`xdpyinfo | grep dimensions | sed 's/[^0-9]*//' | sed 's/ pixels.*//' | awk -Fx '{print $1}'` X11_HEIGHT=`xdpyinfo | grep dimensions | sed 's/[^0-9]*//' | sed 's/ pixels.*//' | awk -Fx '{print $2}'` # Ok, are we in our standalone config if [ $X11_WIDTH -eq 1680 -a $X11_HEIGHT -eq 1028 ]; then # Just the standalone MacBook Pro xterm -ls -tn xterm-color -geometry 80x24+0+0 & xterm -ls -tn xterm-color -geometry 80x24+500+0 & xterm -ls -tn xterm-color -geometry 80x24+0+316 & xterm -ls -tn xterm-color -geometry 80x24+500+316 & xterm -ls -tn xterm-color -geometry 163x27+0+632 & /opt/local/bin/emacs -geometry 107x75-1+0 & elif [ $X11_WIDTH -eq 1440 -a $X11_HEIGHT -eq 1924 ]; then # The powerbook plus the Sun LCD in Berlin xterm -ls -tn xterm-color -geometry 80x24+0+1024 & xterm -ls -tn xterm-color -geometry 80x24+421+1024 & xterm -ls -tn xterm-color -geometry 80x24+0+1292 & xterm -ls -tn xterm-color -geometry 80x24+421+1292 & xterm -ls -tn xterm-color -geometry 164x29+0+1560 & /sw/bin/emacs -geometry 112x79-3+1024 & elif [ $X11_WIDTH -eq 1920 -a $X11_HEIGHT -eq 2100 ]; then # The powerbook plus my 23" Cinema Display xterm -ls -tn xterm-color -geometry 80x24+240+1200 & xterm -ls -tn xterm-color -geometry 80x24+661+1200 & xterm -ls -tn xterm-color -geometry 80x24+240+1468 & xterm -ls -tn xterm-color -geometry 80x24+661+1468 & xterm -ls -tn xterm-color -geometry 164x29+240+1736 & /sw/bin/emacs -geometry 112x79-243+1200 & elif [ $X11_WIDTH -eq 1920 -a $X11_HEIGHT -eq 1200 ]; then # My 23" Cinema Display Standalone xterm -ls -tn xterm-color -geometry 80x24+0+22 & xterm -ls -tn xterm-color -geometry 80x24+421+22 & xterm -ls -tn xterm-color -geometry 80x24+842+22 & xterm -ls -tn xterm-color -geometry 80x24+0+290 & xterm -ls -tn xterm-color -geometry 80x24+421+290 & xterm -ls -tn xterm-color -geometry 80x24+842+290 & xterm -ls -tn xterm-color -geometry 80x24+0+558 & xterm -ls -tn xterm-color -geometry 80x24+421+558 & xterm -ls -tn xterm-color -geometry 80x24+842+558 & xterm -ls -tn xterm-color -geometry 248x30+0+826 & /sw/bin/emacs -geometry 122x108-3+22 & else xterm -ls -tn xterm-color -geometry 80x24+0+22 & fi
The stuck control keys issue exists in 2.2.x as well, unfortunately.
Bummer ... where does the fix for this fit into the ToDo list?
You can just install the 2.2.2 package and you should be fine.
Thanks! - Jim
I'd just delete your ~/.xinitrc file and let use the system-wide one since it looks like you're not doing anything special. You can get your ~/.Xclients stuff by doing the following: sudo cat > /usr/X11/lib/X11/xinit/xinitrc.d/95-xclients << EOF if [ -f $HOME/.Xclients ] ; then sh $HOME/.Xclients fi EOF I think your problem might be using ~ instead of $HOME ... I forget the parsing behind ~, but I remember it doesn't always get substituted (like in crontab for example)... it might only get substituted in interactive shells. I never use it when writing scripts. --Jeremy On Jun 16, 2008, at 22:09, Jim Martin wrote:
On Jun 16, 2008, at 9:55 PM, Jeremy Huddleston wrote:
Well first of all, please report these issues and help get them fixed.
Understood ...
~/.xinitrc should be getting executed. Can you please tell me what the output of 'ps x | grep xinit' is.
dhcp-77% ps x | grep xinit 13525 ?? S 0:00.01 xinit /Users/jim/.xinitrc -- /usr/X11/bin/ X :0 13593 s001 S+ 0:00.00 grep xinit
It looks like it's attempting to invoke it, but things aren't starting correctly. Where would errors be logged?
The .xinitrc file is:
#!/bin/sh
userresources=$HOME/.Xresources usermodmap=$HOME/.Xmodmap sysresources=/usr/X11/lib/X11/xinit/.Xresources sysmodmap=/usr/X11/lib/X11/xinit/.Xmodmap
# merge in defaults and keymaps
if [ -f "$sysresources" ]; then xrdb -merge "$sysresources" fi
if [ -f "$sysmodmap" ]; then xmodmap "$sysmodmap" fi
if [ -f "$userresources" ]; then xrdb -merge "$userresources" fi
if [ -f "$usermodmap" ]; then xmodmap "$usermodmap" fi
# start some nice programs
if [ -f ~/.Xclients ]; then sh ~/.Xclients fi
exec quartz-wm
And the .Xclients file reads:
# Get some dimensions X11_WIDTH=`xdpyinfo | grep dimensions | sed 's/[^0-9]*//' | sed 's/ pixels.*//' | awk -Fx '{print $1}'` X11_HEIGHT=`xdpyinfo | grep dimensions | sed 's/[^0-9]*//' | sed 's/ pixels.*//' | awk -Fx '{print $2}'`
# Ok, are we in our standalone config if [ $X11_WIDTH -eq 1680 -a $X11_HEIGHT -eq 1028 ]; then # Just the standalone MacBook Pro xterm -ls -tn xterm-color -geometry 80x24+0+0 & xterm -ls -tn xterm-color -geometry 80x24+500+0 & xterm -ls -tn xterm-color -geometry 80x24+0+316 & xterm -ls -tn xterm-color -geometry 80x24+500+316 & xterm -ls -tn xterm-color -geometry 163x27+0+632 & /opt/local/bin/emacs -geometry 107x75-1+0 & elif [ $X11_WIDTH -eq 1440 -a $X11_HEIGHT -eq 1924 ]; then # The powerbook plus the Sun LCD in Berlin xterm -ls -tn xterm-color -geometry 80x24+0+1024 & xterm -ls -tn xterm-color -geometry 80x24+421+1024 & xterm -ls -tn xterm-color -geometry 80x24+0+1292 & xterm -ls -tn xterm-color -geometry 80x24+421+1292 & xterm -ls -tn xterm-color -geometry 164x29+0+1560 & /sw/bin/emacs -geometry 112x79-3+1024 & elif [ $X11_WIDTH -eq 1920 -a $X11_HEIGHT -eq 2100 ]; then # The powerbook plus my 23" Cinema Display xterm -ls -tn xterm-color -geometry 80x24+240+1200 & xterm -ls -tn xterm-color -geometry 80x24+661+1200 & xterm -ls -tn xterm-color -geometry 80x24+240+1468 & xterm -ls -tn xterm-color -geometry 80x24+661+1468 & xterm -ls -tn xterm-color -geometry 164x29+240+1736 & /sw/bin/emacs -geometry 112x79-243+1200 & elif [ $X11_WIDTH -eq 1920 -a $X11_HEIGHT -eq 1200 ]; then # My 23" Cinema Display Standalone xterm -ls -tn xterm-color -geometry 80x24+0+22 & xterm -ls -tn xterm-color -geometry 80x24+421+22 & xterm -ls -tn xterm-color -geometry 80x24+842+22 & xterm -ls -tn xterm-color -geometry 80x24+0+290 & xterm -ls -tn xterm-color -geometry 80x24+421+290 & xterm -ls -tn xterm-color -geometry 80x24+842+290 & xterm -ls -tn xterm-color -geometry 80x24+0+558 & xterm -ls -tn xterm-color -geometry 80x24+421+558 & xterm -ls -tn xterm-color -geometry 80x24+842+558 & xterm -ls -tn xterm-color -geometry 248x30+0+826 & /sw/bin/emacs -geometry 122x108-3+22 & else xterm -ls -tn xterm-color -geometry 80x24+0+22 & fi
The stuck control keys issue exists in 2.2.x as well, unfortunately.
Bummer ... where does the fix for this fit into the ToDo list?
You can just install the 2.2.2 package and you should be fine.
Thanks!
- Jim
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
participants (2)
-
Jeremy Huddleston
-
Jim Martin