Re: Some minor annoyances with Xquartz (probably caused by Spaces...)
Re: Some minor annoyances with Xquartz (probably caused by Spaces...)
- Subject: Re: Some minor annoyances with Xquartz (probably caused by Spaces...)
- From: Jeremy Huddleston <email@hidden>
- Date: Thu, 10 Apr 2008 08:57:12 -0700
On Apr 10, 2008, at 07:06, Louis Jones wrote:
Hello all,
I'm currently running X11-2.2.0_rc3 and I'm running 10.5.2 with all
updates on a Mac Pro, MacBook pro and an iMac (August 2007 version).
I've a couple things that happen that I consider as annoyances:
1) If I'm in another application on another Space and I click the
X11 icon in the Dock (I keep all X11 clients in the same space), the
X11 application becomes active (the menu appears) but the Space
doesn't change to my X11 space (no X11 window has focus (I
imagine)..). I have to click a second time so that the X11 space
becomes active.
Someone reported this in the xquartz-dev list as well. Please file a
bug report at http://xquartz.macosforge.org ... include your 'defaults
read org.x.x11' output.
2) When I have two or more overlapping X11 windows, if I click on
one of the windows to make it active (I have the wm_ffm set),
sometimes (not all the time) a window that is hidden behind the
intended window gets focus and pops to the top. Fortunately, since
X11-2.2.0_rc2, I can use Exposé to find the window that I want.
This is most likely related to ffm. I'm not really going to address
ffm issues until I'm satisfied that non-ffm is working properly
first. That's just one extra level of complication. I'm sorry. Can
you trigger this bug without ffm?
3) Since installing RC3, I've the return of an old bug that I was
with the original X11 from 10.5.0. If I launch a xterm, the process
opens a blank window but xterm goes into an infinite loop. I use
an .xinitrc file that launches 3 xterm (or gnome-terminal) in the
background (the commands end in &') and quartz-wm in the foreground.
Sometimes 1, 2 or 3 of the xterms open correctly. The others that
don't open go into an infinite loop (cpu at 100%). After a certain
time, "all becomes normal again" and I can again run my xterms. I
see this mostly from the .xinitrc script and any xterms that I run
from an xterm window or the command menu.
This is a known issue with the kernel. Please file a bug report at http://bugreport.apple.com
to "vote" for getting this addressed in Leopard.
--Jeremy
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden