> On Jul 24, 2015, at 12:00, Mike Wilkes <mike.wil...@hotmail.com> wrote: > > I have been problem free for over a year, thank you very much, fink > providers. But, I recently destroyed my less than two-year-old MBP with a > glass of kombucha tea (the hard drive survived intact), and was forced to > trade the first-born for a new computer. Yosemite (10.10.4) was > pre-installed on the new MBP, and during the setup I transferred the hard > drive contents from trashed MBP to new one (so not a clean install). After > installation, I moved old /sw to the side, and installed fink 0.38.6 into new > /sw. Also installed full Xcode 6.4 and the CLT. I let fink install several of > my favorite unix programs (xfig, gv, xgraph, grace, and the nedit editor). No > problems whatsoever. I then installed the latest Quartz 2.7.7 (I had been > running 2.7.5 on the now-defunct MBP). Then the problems began. I requested > xterm from Terminal.app and got a window pinned to the upper left corner of > desktop. It could not be moved, and after placing the cursor in that window, > it turned into an X outside the window until I entered the Terminal again and > clicked on it. Called for gv from the Terminal, and it's window also pinned > over the xterm. Same for nedit window. None could be moved, none had a menu > bar at the top.
That appears to indicate that the window manager didn’t start. > Then these windows and X11 crashed, each with an error of the form > > Error from nedit window: XIO: fatal IO error 35 (Resource temporarily > unavailable) on X server > "/private/tmp/com.apple.launchd.hlZVYQFTa4/org.macosforge.xquartz:0" > after 9511 requests (5857 known processed) with 0 events remaining. > That’d be standard for an application starting with no window manager; it’s hanging out waiting for the window manager, and then crashes. > This all began over a week ago, and I am exhausted after trying several > reinstalls of fink and different versions of XQuartz. Reinstalling Fink is totally useless in most circumstances. The build process is intended to be deterministic, so unless you also remove something else that taints your Fink builds, you will just spend extra time getting back to exactly the same place. > The only solution I have found so far is to use XQuartz 2.7.5, which will > start up xterm windows and X application windows. BUT, I cannot start any X > windows from Terminal!! If I call for an xterm from Terminal I get > > xterm: Xt error: Can't open display: > /private/tmp/com.apple.launchd.8XjZmITi2w/org.macosforge.xquartz:0 > > Strangely enough, this same type of error occurred for me a little over a > year ago on Mountain Lion (10.8.5) when I tried to go to XQuartz 2.7.7, and > the only resolution was to go back to Quartz 2.7.5 (Alexander, we had a long > exchange about this, but of course I wouldn't expect you to remember such a > thing after all the things you have had to deal with since). However, at > that time, and afterwards up to this point, the Terminal also worked with X > just fine. > > > Oh, I nearly forgot a very important point...on two occasions at least in the > last week, everything was working together perfectly with 2.7.7, but then > each time a REBOOT of the machine brought it back to the same sorry state > with no working X windows! > > > Thanks for any help you can give me with this very frustrating situation. > > > -Mike Are you doing any customization of your X11 startup, or just using the defaults? What happens if you start X11 before running applications? We’ve found that X11 has gotten kind of flaky about startup starting on 10.9. But, that being said, I don’t reproduce the problem here. -- Alexander Hansen, Ph.D. Fink User Liaison
------------------------------------------------------------------------------
_______________________________________________ Fink-beginners mailing list Fink-beginners@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.beginners Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-beginners
