> On Apr 6, 2017, at 10:39, Langer, Stephen A. (Fed) <[email protected]> > wrote: > > Hi Jeremy -- > > If I don't use -N, openmotif (installed as a dependency of grace) insists > that that xorg-libXt needs to be installed with +flat_namespace. The > installation will pause at that point so that xorg-libXt can be installed > with the explicit variant.
All -N does is skip the prompt. > When I used -N, I listed the previously requested ports, but I forgot to > select the flat_namespace variant. I generated the list with "port echo > requested | cut -d ' ' -f 1" (which was a mistake), and then uninstalled and > ran "sudo port -N install `cat listofports`". During that process, there was > no message about flat_namespace and the wrong variant was installed. After > that, X11 wouldn't work no matter what I did, until I installed > xorg-server-devel. > > Anyway, that's the reason that I thought that -N might have had an effect. I > can't propose a mechanism, but there's some circumstantial evidence. > > -- Steve > > From: <[email protected]> on behalf of Jeremy Huddleston Sequoia > <[email protected]> > Date: Thursday, April 6, 2017 at 12:56 PM > To: "Langer, Stephen A. (Fed)" <[email protected]> > Cc: "[email protected]" <[email protected]> > Subject: Re: X11 won't start > > -N really has no effect on the build process. > > Ok, I'll take a look at the sysdiagnose. Send me the link offline, and I'll > look at it as soon as I can. > >> On Apr 6, 2017, at 07:29, Langer, Stephen A. (Fed) <[email protected]> >> wrote: >> Hi Jeremy -- >> Thanks for getting back to me. >> The init scripts aren’t the problem. I haven’t changed them in years, and >> I don’t have the same problem on a different Mac. Just to be sure, I did >> the test with a new user, and X11 crashes in the same way. The obvious >> difference between the broken Mac and the working one is that on the >> broken one I tried to reinstall all of the ports at once, using -N, and on >> the working Mac I didn’t use -N. I don’t remember the order in which I >> did the installation, though. >> I’ll put the sysdiagnose output on NIST’s secure file transfer site and >> send you a link to it. I think it’ll choke our e-mail server. >> -- Steve >> On 4/6/17, 12:35 AM, "Jeremy Huddleston Sequoia" <[email protected]> >> wrote: >>> You likely have an issue with one of your shell init scripts or a bad >>> ~/.xinitrc present. That's what is the cause of almost all such issues. >>> Try creating a new user on your computer, logging in as that user, and >>> launching X11. If it works, then it's almost certainly ~/.xinitrc, >>> ~/.profile, ~/.bashrc, ~/.bash_profile, etc. >>> If it's not that, please take a sysdiagnose while X11 is restarting, and >>> send it to me. >>> --Jeremy >>>> On Apr 5, 2017, at 07:23, Langer, Stephen A. (Fed) >>>> <[email protected]> wrote: >>>> Hi -- >>>> I posted this note to macports-users, but didn't get a helpful >>>> response, so I'm trying again here: >>>> I just updated my computer to Sierra, and now X11 won't start. I >>>> presumed that I had messed up the macports migration, so I just >>>> uninstalled everything and installed only xorg-server and xterm, but I'm >>>> still getting the same error. There's an "X11 quit unexpectedly" >>>> dialog, which keeps reappearing when dismissed. I have to log out to >>>> get it to go away. >>>> System.log is filled with lines like "X[6012]: no path for address >>>> 0x1234567" >>>> In case it's relevant, what I might have screwed up in the first >>>> migration was that I tried to install only the requested ports, which >>>> has worked for me in the past. But this time I put them all on one >>>> line, and used -N so that port wouldn't ask me for permission to install >>>> the dependencies, and I could leave it to work on its own. That ran >>>> into problems caused by https://trac.macports.org/ticket/49379. It >>>> seemed to have installed xorg-libXt with +flat_namespace and then >>>> reinstalled it without it, or vice versa (both were installed but I >>>> forget which was active). In any case, I uninstalled everything, >>>> installed xorg-libXt first, using +flat_namespace, and then installed >>>> all the other requested ports without -N so that I'd see if anything >>>> went wrong. I didn't see any errors, but X11 wouldn't start. This >>>> morning I tried installing only xorg-server and xterm, and it still >>>> won't start. >>>> Why is X11 failing to start? How can I keep it from attempting to >>>> start repeatedly, even after I've killed xterm or whatever other X11 app >>>> I'm using? What might have I done wrong in the installation and how can >>>> I fix it? >>>> Since that post, I have tried completely uninstalling macports, >>>> reinstalling just xorg-server and xterm, and rebooting, but I'm still >>>> seeing the same behavior. Just to be sure that it's not a xterm >>>> problem, I tried xeyes, which fails the same way. >>>> Any suggestions would be appreciated! Thank you. >>>> -- Steve >>>> _______________________________________________ >>>> Do not post admin requests to the list. They will be ignored. >>>> X11-users mailing list ([email protected]) >>>> Help/Unsubscribe/Update your Subscription: >>>> https://lists.apple.com/mailman/options/x11-users/jeremyhu%40freedesktop. >>>> org >>>> This email sent to [email protected] >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> X11-users mailing list ([email protected]) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/x11-users/jeremyhu%40freedesktop.org >> This email sent to [email protected] > >
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. X11-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/x11-users/archive%40mail-archive.com This email sent to [email protected]
