|
|
#41 |
|
Moderator
Join Date: Jan 2002
Location: Singapore
Posts: 4,237
|
40- To disable launchd support for launching X11
If you don't like launchd support:
Running /usr/X11/X11.app instead of /Apps/Utils/X11.app will give you a simple, normal X server. You might even move the former to the latter. The next two steps are optional: * Adding xterm back to /usr/X11/lib/X11/xinit/xinitrc (or adding it to ~/.xinitrc) will give you an xterm when you run /usr/X11/X11.app * 'sudo launchctl unload -w /System/Library/LaunchAgents/ org.x.X11.plist' will prevent launchd from setting $DISPLAY. . Last edited by sao; 11-14-2007 at 03:59 AM. |
|
|
|
|
#42 |
|
Moderator
Join Date: Jan 2002
Location: Singapore
Posts: 4,237
|
41- Apple Installer Bug
Did you do an upgrade install of Leopard? Then you are perhaps bitten by the Leopard Installer bug.
Check if you have the Tiger man pages still sitting in /usr/share/man/ manX side by side with the Leopard man pages. Please, run: ls -l /usr/share/man/man1/man* To see if you get a result similar to the following: -rw-r--r-- 1 root wheel 10981 Jan 13 2006 /usr/share/man/man1/man.1 -r--r--r-- 1 root wheel 4821 Sep 23 21:54 /usr/share/man/man1/man. 1.gz lrwxr-xr-x 1 root wheel 5 Jul 24 2006 /usr/share/man/man1/ manpath.1 -> man.1 lrwxr-xr-x 1 root wheel 8 Oct 27 15:54 /usr/share/man/man1/ manpath.1.gz -> man.1.gz The gzipped man pages are from Leopard, the others from Tiger. And the man command chooses the old ones over the new ones every time. Hopefully a future Apple OS installer will get this right from the beginning (it doesn't happen if you did an archive and install of Leopard). Dave Vasilevsky (Thanks!) wrote a little script to fix the duplicate man pages problem. It looks for all duplicate man pages in /usr/share/man and deletes all but the newest one. Just put it in a file 'manpages.rb' and run with: Code:
sudo ruby manpages.rb Code:
#!/usr/bin/ruby
require 'find'
pages = Hash.new { |h, k| h[k] = [] }
Find.find('/usr/share/man') do |path|
stat = File.lstat(path)
next unless stat.file?
base = File.basename(path)
base.sub!(/\.gz$/,'')
base.sub!(/(\.\d)[^\.]*$/, '\1')
pages[base] << { :path => path, :mtime => stat.mtime }
end
pages.each do |base, files|
next if files.size == 1
ordered = files.sort_by { |f| f[:mtime] }
ordered.pop
ordered.each { |f| File.unlink(f[:path]) }
end
. Last edited by sao; 11-24-2007 at 12:01 AM. |
|
|
|
|
#43 |
|
Moderator
Join Date: Jan 2002
Location: Singapore
Posts: 4,237
|
42- Last.fm focus stealing bug
If you have the Last.fm AudioScrobbler plugin installed, for some reason every two seconds it steals focus from X11, which makes it unusable. It's probably something to do with sending (or trying to send) AppleScript events to iTunes to get the currently playing track info. I couldn't tell you why this is now a problem on Leopard, yet not on Tiger.
. |
|
|
|
|
#44 |
|
Moderator
Join Date: Jan 2002
Location: Singapore
Posts: 4,237
|
43- What to do after you messed up your X11 installation?
Messed it up, got confused, want to start over?
Before you start deleting anything, make sure you have a Leopard's installation DVD available and downloaded the latest X11 package from the Xquartz Project. * Delete pretty much all X11 from you system, and let it forget its receipts: Code:
sudo rm -rf /usr/X11 /usr/X11R6 sudo pkgutil --forget com.apple.pkg.X11DocumentationLeo sudo pkgutil --forget com.apple.pkg.X11User sudo pkgutil --forget com.apple.pkg.X11SDKLeo sudo pkgutil --forget org.x.X11.pkg * Install X11SDK.pkg from Leopard's installation DVD, which is in /Volumes/Mac OS X Install DVD/Optional Installs/Xcode Tools/Packages/ * Install the latest X11 package release from the Xquartz Project. . Last edited by sao; 05-07-2008 at 01:50 PM. |
|
|
|
|
#45 |
|
Moderator
Join Date: Jan 2002
Location: Singapore
Posts: 4,237
|
44- X11.app/xterm does not launch
Code:
01.03.08 11:44:22 org.x.X11[638] xterm: bad command line option "xterm" 01.03.08 11:44:22 org.x.X11[638] usage: xterm [-/+132] [-C] [-Sccn] [- T string] [-/+ah] [-/+ai] [-/+aw] For example: "set history = 1000" in ~/.bash_profile. "set bell-style visible" in ~/.bash_profile "set noclobber" in ~/.bashrc which had a similar effect. . |
|
|
|
|
#46 |
|
Moderator
Join Date: Jan 2002
Location: Singapore
Posts: 4,237
|
45- If you get the error "failed to bind to surface"
If you get the error "failed to bind to surface" when you run remotely certain X11 applications (for example, tecplot, vapor), setting the environment variable LIBGL_ALWAYS_INDIRECT (on the remote machine) should get rid of this.
In a tcsh startup script, this can be done as follows: Code:
if ( $?SSH_TTY ) then
setenv LIBGL_ALWAYS_INDIRECT 1
endif
|
|
|
|
|
#47 |
|
Moderator
Join Date: Jan 2002
Location: Singapore
Posts: 4,237
|
46- Font size in GnuCash, Inkscape, and Gimp
If the fonts are too small in the menus, menubar, etc. of GnuCash, Inkscape, and Gimp, remember that they all use the GTK2 toolkit, so you change font sizes using the GTK2 way:
If you don't have ~/.gtkrc-2.0, create it, containing the single line: Code:
gtk-font-name = "geneva 12" . |
|
|
|
|
#48 |
|
Moderator
Join Date: Jan 2002
Location: Singapore
Posts: 4,237
|
47- Running MATLAB from remote machine
Almost all the matlab GUI runs under Java which uses aqua windows. Only the graphics windows run under X11. The only way you can have a 'true' X11 version of matlab is by starting it with the -nojvm option from the command line. Try:
ssh -Y server.name and then matlab -nojvm The "-nojvm" option allow you to run a command-line version of Matlab on a Mac and have the display on a remote machine. It runs fine, but It doesn't provide the nice GUI with the editor, variable list, command history, etc. . |
|
|
|
|
#49 |
|
Moderator
Join Date: Jan 2002
Location: Singapore
Posts: 4,237
|
48- Change the default X server DPI setting
Copied from a great tip posted by "steeb" at Macosxhints main site:
http://www.macosxhints.com/article.p...80621201901244 "....I read a thread on MacOS Forge that stated that the launchd auto-starter included in their community-supported Xserver releases actually just runs the startx command." "This is great news, because startx is a script that can be edited. So I installed the latest packaged build available from their website, then opened a Terminal window, and pulled up the startx script in a text editor: sudo nano -w `which startx`. Then I pressed Control-W and located the string defaultserverargs, and changed the first occurrence in the file from this... defaultserverargs="" ... to this ... defaultserverargs="-dpi 96" Then I pressed Control-X to exit, and telling nano to save the changes when prompted. Now the next time I started X11, my display reported a resolution of 96x96 dpi. You can check what X11 thinks your screen resolution is with the following command: xdpyinfo | grep -i resolution Note that the dpi change will have to be re-applied each time you install a new build of X11 from MacOSforge. You may also find that this tip doesn't work if you replace the community supported builds with an Apple-supported build of X11." . |
|
|
![]() |
|
|