X11 - public beta v0.2

[Jacques]

New X11 (http://www.apple.com/macosx/x11/) version out today, any comments?

[bluehz]

Suuposedly copy/paste between Aqua and X11 (inlucing other WM) was fixed. No luck here. Just tried to copy from Aqua and paste into Xterm window with no luck...

Ooops - I take that back...

opt+click to paste...

[maousse]

foreign keyboards are fully supported (french at least , | is now easy to reach !) Fine !

[Phil St. Romain]

Anything we should know about installing this, sao. Should we uninstall the old one first?

Maybe I should make this one a sticky thread for awhile?

[AKcrab]

I had to do a custom install, checking the "overwrite prefs" or some such (in the customize install there is only one box not checked by default) in order to get the new version working properly.
Windows and widgets were not aqua, but teal and crappy looking. Apparently you can edit a config in VI, but a reinstall was painless for me.

[wgscott]

you can type:

defaults write com.apple.x11 wm_ffm true

to set autofocus to follow the mouse in x11 apps

[sao]

Phil,

Just download the new beta and install it on top of your previous beta.

If you don't have a ~/.xinitrc file, X11 will now read /etc/X11/xinit/xinitrc, and you will probably get "twm" for a window manager (the XFree86 default window manager).

If you do not install the X11 Config package while installing X11 (which is the current default) then it will not install /etc/X11 (with the new xinitrc).

Apple said this is a bug and should be fixed in the next version. Unfortunately lot's of people are going to run into this.

Important:

If you want to compile from source reinstall also the 'X11 for Mac OS X Public Beta SDK' (3.9 MB) as it was also updated.

[richardjpratt]

Most of this is from another post but I thought it might be helpful here too.

The update fixes a "bug" that had the quartz window manager start automaticly if it didn't find an .xintric file. Instead it now starts the TWM window manager if it does not find the file. I heard that this what should happen though my source isn't any better than anyone elses.

If you install v0.2 over an existing install it assumes you already have an .xintric file and does not write the needed file. If you custom install and select the overwrite prefs (or something like that, I can't remember the exact option) it will make the file for you.

If you don't want to reinstall just open a new terminal window and type in it:

echo "exec quartz-wm" > .xinitrc

This will create the file called .xinitrc in your home directory with the command "exec quartz-wm" as its only line.

The next time you start X11 it should start the Quartz window manager instead of TWM.

Hope this helps,

Richard

PS (or add "exec quartz-wm" to an existing .xinitrc file)

[bluehz]

I am a little confused here. I already have the first beta installed, I also had previous .xinitrc from running Xfree. By default when I installed this latest X11-beta - the config was turned off as an install. So I left it at that and continued. Is that correct, or should I custom install the configs only, or just do the line above?

Also - I have a few other customizations in my .xinitrc - like:userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/usr/X11R6/lib/X11/xinit/.Xresources
sysmodmap=/usr/X11R6/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

# autocutsel &

# start some nice programs
source /sw/bin/init.sh
#/sw/bin/blackbox &
#/sw/bin/worker
#/sw/bin/wmaker
#xclock -geometry 50x50-1+1 &
#xterm -geometry 80x35+494+51 &
xterm -j -rightbar -sb -sl 1000 -bg black -fg green -geometry 80x35+584+20 &
xcutsel -geometry 58x68-3+20 &
Should i just dump those or transfer over to any new .xinitrc? I must admit I know very little about what most of that does, except the wm section where I switch wm occasionally - manually editing the file to taste.

One interesting note - using only the "exec quartz-wm" in my .xinitrc file, I launched X11 to try it out and lo and behold - my $PATH is now correct! It never was transcribed over from my normal OS X environ properly - I still use the old style - pre-Jaguar tcsh method. I just checked though and the $PATH is correct. Not sure if this is a function of the new beta or the .xinitrc.

[sao]

When you upgrade your old X11 PB installation and install X11 beta 2 now a window manager starts up by default (twm) like it should be.

And of course all of the windows will be using 'twm' window manager frames instead of the aqua frames like before.

So, make a ~/.xinitrc file to establish your own start-up applications and window manager like before.

If you want quartz-wm then write in your ~/.xinitrc file:

exec /usr/X11R6/bin/quartz-wm

[sao]

Bluehz,

You can use your own ~/.xinitrc file, that's fine.

Only the people that didn't have a previous ~/.xinitrc file, will see 'twm' (the default XFree86 window manager) coming up instead of 'quartz-wm' when starting the X11.app.

[bluehz]

This is nuts - just quit X11 and restarted - did nothing to the .xinitrc ... still contains only "Exec quartz-wm" only now... my $PATH is screwed again... only bare minimum /usr/bin, etc..

[bluehz]

Thats odd - why did Apple set it so wm woudl start up by default instead of quartz-wm?

No matter what I do now - I can not get my $PATH back... its like it was a fluke the first time I did it. Also - the copy/paste (even cmd+click_ is no longer working between Aqua and X11.

[sao]

bluehz,

The default standart for starting XFree86 is now implemented by Apple, which calls for 'twm', the default wm, if you don't have a ~/.xinitrc file which says otherwise.

You will find xinitrc default file in:

/etc/X11/xinit/xinitrc which uses twm.

To make your own .xinitrc file, copy this file to your home directory:

cp /etc/X11/xinit/xinitrc ~/.xinitrc

Then, you can edit it with your own choices.

changing the twm for quartz-wm,

source /sw/bin/init.sh

/usr/X11R6/bin/xterm -j -rightbar -sb -sl 1000 -bg black -fg green -geometry 80x35+584+20 &

exec /usr/X11R6/bin/quartz-wm

[cradom]

Do you still need to run the script to fix the libs for Fink?

[sao]

cradom wrote:
Do you still need to run the script to fix the libs for Fink?
I think it's already fixed in this release, so the library-name patch script won't be needed anymore.

[Jacques]

Here's the link (http://www.apple.com/macosx/x11/) again, another update came out yesterday.

[bluehz]

If I am not mistaken - the only difference in the 0.2 and 0.21 versions is in the installer. In 0.2 the default for installing the Configs was OFF... in the 0.21 the default is ON. Seems like I read that in the 0.21 README.

[wgscott]

As of the 0.2.x update, compiling will fail with libGL if you have a -force_flat_namespace flag.

I found out the hard way.

[sao]

wgscott wrote:
compiling will fail with libGL if you have a -force_flat_namespace flag
I read a possible solution to your problem posted at the x11-users lists:

"it might work to use nmedit to turn the duplicate symbols into static symbols. Create a file foo containing:

_glGetColorTableEXT
_glGetColorTableParameterfvEXT
_glGetColorTableParameterivEXT

then execute

"sudo nmedit -R foo /usr/X11R6/lib/libGL.1.2.dylib"

The post says this works.

[sao]

bluehz wrote:
If I am not mistaken - the only difference in the 0.2 and 0.21 versions is in the installer. In 0.2 the default for installing the Configs was OFF... in the 0.21 the default is ON.
That is correct!

The only difference in the latest version, is that they changed the default settings, because many people (beginners) were having problems dealing with the XFree86 default window manager (twm).

>>>>
"the problem where people were seeing the twm window manager instead of the quartz-wm window manager after a default installation. Even though there have been workarounds and explanations posted, a lot of users were unaware of the reason why they were not seeing the quartz-wm window manager with the default install.

Advanced users (those that have made changes to /etc/X11) can either deselect the "X11 Config" package during install or restore their /etc/X11 directory from /etc/X11.AppleBackup".
<<<<