Re: wierd display problem
Re: wierd display problem
- Subject: Re: wierd display problem
- From: Itai Seggev <email@hidden>
- Date: Thu, 19 Apr 2012 22:21:56 -0500
On Wed, Apr 18, 2012 at 09:28:21PM -0700, Jeremy Huddleston wrote:
>
> On Apr 18, 2012, at 20:16, Itai Seggev wrote:
>
> > I copied over my .xinitrc.d directory from my old to new MBP. The old one was
> > running Leopard + XQuartz 2.6.0 (I think, I can double check if necessary).
> > The new one is using stock Lion 10.7.3 X11.app. The total contents of the
> > directory are
> >
> > dcopserver
> > klipper&
> > cd
> > konsole&
> > zsh ~/.open_konsole_shells& #script to add more tabs and resize
> > exec kwin
> >
> > This worked fine on the old machine, but on the new one the konsole shells have
> > a display of :0.
>
> They should also have that DISPLAY on your old system as well. That's inherited from xinit which has never actually used the launchd socket.
>
> > The app which originally caused X11 to laucnh (e.g., xterm&)
> > has the correct display.
>
> Yep, because it inherited it from Terminal.app
>
> > I put in a debugging echo into right into the very
> > start of the first script and the display there is already :0.
> >
> > 1) Why is it only broken on Lion
>
> What is actually broken?
I thought the value of the display was broken, because it was causing gtk emacs
to lock on startup. See below.
> > 2) (More importantly), who can I fix it?
>
> If the only thing is that $DISPLAY isn't the launchd socket, that's not anything new. You're welcome to hack on xinit to figure out a solution, but it's not really worth it, IMO.
You're right, my old MBP had the same behavior. This caused all sorts of small
glitches that I thought were just OSX/Fink, but now I know could be traced to
the display. For some reason, the MacPorts emacs on my new MBP completely
froze when the display was zero, which forced me to investigate and
notice/identify the issue. It seems like some sort of authentication problem,
as 'xhost +' would fix emacs.
At any rate, I fixed this issue by adding the following to the start of my
.xinitrc.d:
DISPLAY=`launchctl getenv DISPLAY`
I don't know if this could be integrated into xinit, but it worked for me!
--
Itai
In 1997 a group of programmers started writing a desktop environment to fix a
travesty they didn't create. Their program promptly found its way onto un*x
systems everywhere. Today, still opposed by a software monopolist, they survive
as soldiers of fortune. If you share their vision, if you know you can help,
and if you can connect to internet, maybe you can join... the K-Team.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden