Re: Problem with x11 windows popping in from Chrome and other apps
Re: Problem with x11 windows popping in from Chrome and other apps
- Subject: Re: Problem with x11 windows popping in from Chrome and other apps
- From: Cheng-Yang Tan <email@hidden>
- Date: Sat, 24 Mar 2018 14:00:09 +0000 (UTC)
Hi Rene, Problem remains!
I used the following: launchctl unload -w
/Library/LaunchDaemons/org.macosforge.xquartz.privileged_startx.plist
launchctl unload -w /Library/LaunchAgents/org.macosforge.xquartz.startx.plist
and then renamed those files to bak (just in case :) )
Restarted xquartz and the problem remains.
Here's my display variable:
/private/tmp/com.apple.launchd.8uE6YvWF2M/org.macosforge.xquartz:0
Any other pointers?
cytan
On Saturday, March 24, 2018, 8:46:42 AM CDT, Cheng-Yang Tan
<email@hidden> wrote:
Hi Rene,
Do I unload the following plists?
org.macosforge.xquartz.startx.plist
org.macosforge.xquartz.privileged_startx.plist
Here's what they contain:
/Library/LaunchAgents/org.macosforge.xquartz.startx.plist:
<string>org.macosforge.xquartz.startx</string>
/Library/LaunchAgents/org.macosforge.xquartz.startx.plist:
<key>org.macosforge.xquartz:0</key>/Library/LaunchDaemons/org.macosforge.xquartz.privileged_startx.plist:
<string>org.macosforge.xquartz.privileged_startx</string>/Library/LaunchDaemons/org.macosforge.xquartz.privileged_startx.plist:
<key>org.macosforge.xquartz.privileged_startx</key>
cytan
On Saturday, March 24, 2018, 5:21:41 AM CDT, René J.V. Bertin
<email@hidden> wrote:
On Friday March 23 2018 18:40:26 email@hidden wrote:
>Hi,=C2=A0 =C2=A0This is the problem that I have and I'm wondering whether t=
>here is a fix:
>=C2=A0 =C2=A0 I have Chrome on top of an xterm and for some inexplicable re=
>ason, the xterm would start popping in front of Chrome. I believe this also=
> happens when I use other apps.
>
Usually the opposite happens...
I would guess that this is a symptom of *something* activating the XQuartz
application. Do you use any X11-based applications that are launched
periodically or on-demand?
XQuartz comes with a feature to launch it automatically whenever an application
attempts to read the DISPLAY env. variable. This is nice for some users, but
tends to get in the way if you're like me and always have an XQuartz session
running which you prefer to launch manually. (Or if you prefer to have a simple
DISPLAY value like ":0" instead of a random socket name.)
To deactivate the feature, find the launchd plists for XQuartz, unload them
(launchctl unload -w /path/to/the/.plist) and then remove the plists for good
measure. I'm not on my Mac and don't remember the exact name of the file (or
files, there might be 2).
R.
PS: I do get a similar behaviour since a few XQuartz release iterations, but
only when I'm working in an X11 application. It used to be the case that I
could have "native" windows reliably covering all but the active X11 window.
It's still possible, but once every so often some event will occur that brings
all X11 windows to the front (read: onto the same native window stack layer).
Again, that's only when I'm already working in XQuartz so it's not a huge deal.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden