P.M.F. - 9. Package Usage Problems - Specific Packages

R.: Make sure you have the "eSound Output Plugin" selected in the XMMS preferences. For some strange reason, it selects the disk writer plugin as the default.

If you still get no sound output or XMMS complains that it can't find your sound card try this:

• Make sure you haven't muted sound output in Mac OS X.
• Run esdcat /usr/libexec/config.guess (or any other file of a decent size). If you hear a short noise, eSound works and XMMS should work too if it's configured correctly. If you don't hear anything, esd isn't working for some reason. You can try to start it up manually with esd & and watch the messages.
• If it still doesn't work, check the permissions on /tmp/.esd and /tmp/.esd/socket. Those should have your normal user account as the owner. If they aren't owned by you, kill esd if it's running, remove the directory as root (sudo rm -rf /tmp/.esd), then start esd again (as a normal user, not as root).

Note that esd is designed to be run by a normal user, not by root. It usually communicates via the file system socket /tmp/.esd/socket. You only need the -tcp and -port switches if you want to run esd clients on another machine over the network.

There have also been reports of XMMS crashing or freezing on 10.1. We don't have an analysis or a fix yet.

R.: This is a known problem that occurs with recent versions of nedit and lesstif on all platforms. The workaround is to open a new window with File-->New, then open the next file you want to work on.

This is now fixed in nedit-5.3-6, which depends on openmotif3 rather than lesstif.

R.: First, make sure you are sourcing init.sh in your X startup ~/.xinitrc.

In Jaguar, sometimes all of the xfree86 packages get built, but only xfree86-base and xfree86-base-shlibs are installed. Check whether you have xfree86-rootless and xfree86-rootless-shlibs installed. If not, then fink install xfree86-rootless should do the trick.

If you do have it installed, then try fink rebuild xfree86-rootless. If that doesn't work, verify that you have /usr/bin/X11R6 in your PATH.

R.: Some users have reported that the behavior of the delete key is different between XDarwin and Apple X11. This can be rectified by adding lines to the appropriate X startup files:

.Xmodmap:

keycode 59 = Delete

.Xresources:

xterm*.deleteIsDEL: true 
xterm*.backarrowKey: false
xterm*.ttyModes: erase ^?

.xinitrc

xrdb -load $HOME/.Xresources 
xmodmap $HOME/.Xmodmap

R.: While under GNOME 1.x gnome-session invokes the sawfish window manager automatically, under GNOME 2.x, you'll have to call a window manager in ~/.xinitrc before running gnome-session, e.g.:

... 
exec metacity & exec gnome-session

Note: this is no longer true for GNOME 2.4. Running gnome-session invokes a window manager.

R.: You didn't upgrade X11 to version "X11 1.0 - XFree86 4.3.0" included with Panther. You can install X11 from X11.pkg on Disk 3.

R.: This is caused by an apparent bug in Tiger's dynamic linker (current as of 10.4.1), but looks to be fixed in 10.4.3, and Fink has had a workaround in the guise of base-files-1.9.7-1 or later.

If you haven't updated Tiger and/or base-files yet, you can work around this issue by prefixing the name of the software you want to run as follows:

env DYLD_FALLBACK_LIBRARY_PATH=: 

E.g., if you want to use gnucash, you'd use

env DYLD_FALLBACK_LIBRARY_PATH=: gnucash

This method works for applications that are launched via the Application Menu in Apple's X11 as well as a terminal.

You may find it preferable to set this globally (e.g. in your startup script, and/or in your .xinitrc, which you may need to do to run GNOME). Put

export DYLD_FALLBACK_LIBRARY_PATH=:

in your .xinitrc (regardless of your login shell) or your .profile (or other startup script) for bash users and:

setenv DYLD_FALLBACK_LIBRARY_PATH :

is the corresponding command to use in e.g. your .cshrc file for tcsh users.

Note: this will automatically be done if you install a recent enough base-files.

R.: You need to install the yelp package. This package was not placed within the GNOME bundle because it uses cryptography, and it was decided not to place all of GNOME in the crypto tree just to use the help system.