Some minor annoyances with Xquartz (probably caused by Spaces...)
Some minor annoyances with Xquartz (probably caused by Spaces...)
- Subject: Some minor annoyances with Xquartz (probably caused by Spaces...)
- From: Louis Jones <email@hidden>
- Date: Thu, 10 Apr 2008 16:06:43 +0200
- Resent-date: Thu, 10 Apr 2008 16:10:31 +0200
- Resent-from: Louis Jones <email@hidden>
- Resent-message-id: <email@hidden>
- Resent-to: email@hidden
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.
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.
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.
The following is an excerpt from running 'dtruss' on the xterm command:
The first part below, shows that xterm has opened, read and close it's
defaults file. The file was opened on filedescriptor 4.
1185/0x65a2208: open("/usr/X11/lib/X11/app-defaults/XTerm\0", 0x0,
0x0) = 4 0
1185/0x65a2208: fstat(0x4, 0xBFFFF2F0, 0x0) = 0 0
1185/0x65a2208: read(0x4, "! $XTermId: XTerm.ad,v 1.85 2007/11/26
18:42:37 tom Exp $\n\n*saveLines: 1024\n\n*SimpleMenu*BackingStore:
NotUseful\n*SimpleMenu*menuLabel.font: -adobe-helvetica-bold-r-normal--
*-120-*-*-*-*-iso8859-*\n*SimpleMenu*menuLabel.vertSpace:
\t100\n*SimpleMenu*Horizonta", 0x1AC5) = 6853 0
1185/0x65a2208: close(0x4) = 0 0
1185/0x65a2208: write(0x3, "\020\001\t\0", 0x24) = 36 0
1185/0x65a2208: read(0x3, "f\0", 0x20) = -1 Err#35
1185/0x65a2208: poll(0x403B40, 0x1, 0xFFFFFFFF) = 1 0
.
. ~100 lines of write, read, poll
After some X11 protocol exchanges, xterm does a 'fcntl' system call on
file descriptor 4 and seems to be looping on this call waiting for it
to return without an error (which it won't as fd 4 has been closed
above).....
.
1185/0x65a2208: read(0x3, "\001\204\035\0", 0x20) = 32 0
1185/0x65a2208: writev(0x3, 0xBFFFD758, 0x3) = 20 0
1185/0x65a2208: read(0x3, "\001\204\035\0", 0x20) = -1 Err#35
1185/0x65a2208: ioctl(0x4, 0x20007454, 0x0) = -1 Err#-1
1185/0x65a2208: ioctl(0x4, 0x20007454, 0x0) = -1 Err#-1
1185/0x65a2208: ioctl(0x4, 0x20007454, 0x0) = -1 Err#-1
1185/0x65a2208: ioctl(0x4, 0x20007454, 0x0) = -1 Err#-1
1185/0x65a2208: ioctl(0x4, 0x20007454, 0x0) = -1 Err#-1
1185/0x65a2208: ioctl(0x4, 0x20007454, 0x0) = -1 Err#-1
.
. to infinity
.
I can make the whole trace output available if need be...
Thanks in advance (and sorry for the long post)..
--Louis Jones
--
Louis Jones | Pôle Informatique
<email@hidden> | tel +33 1 4061 3125
Institut Pasteur, 28, rue du Dr. Roux , 75724 Paris CEDEX 15, France
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden