On May 13, 2012, at 15:53, Peter Dyballa <Peter_Dyballa@Web.DE> wrote:
Am 13.05.2012 um 23:46 schrieb Jeremy Huddleston:
Move aside ~/.Xmodmap, setup both servers identically, and compare the output of 'xmodmap -pke' on both.
It seems as if the XQuartz 2.7.2_rc2's preferences list was defective. Meanwhile it's repaired. It seems as if my sparse ~/.Xmodmap is not needed.
Ok, so the issue is resolved? Can you give more specifics to cure my curiosity?
XQuartz 2.7.2_rc2 seems to produce a font path setting with the elements /opt/X11/share/fonts/OTF, /Library/Fonts, /System/Library/Fonts not ending with a slash and one element, "built-ins", that causes this report in Console:
May 14 00:19:19 sumac org.macosforge.xquartz.startx[11811]: xset: bad font path element (#17), possible causes are: May 14 00:19:19 sumac org.macosforge.xquartz.startx[11811]: Directory does not exist or has wrong permissions May 14 00:19:19 sumac org.macosforge.xquartz.startx[11811]: Directory missing fonts.dir May 14 00:19:19 sumac org.macosforge.xquartz.startx[11811]: Incorrect font server address or syntax
Which is element 17 in the list? Is that directory missing a fonts.dir?
MacPorts' XQuartz 2.7.2 has only /Library/Fonts and /System/Library/Fonts not ending with a slash, "built-ins" causes no report.
Ok.
But then I have this:
May 14 00:42:48 sumac org.macports.X11.stub[14409]: launch_msg("CheckIn") IPC failure: Operation not permitted
Expected.
May 14 00:43:07 sumac /usr/local/bin/emacs-23.3[14449]: BUG in libdispatch: 10K549 - 1986 - 0x4
Is it something I should report?
That message just indicates that kevent() returned EINTR. This is harmless; just ignore it. I believe Lion's libdispatch no longer prints that message.