Hi,
This just happened to me again. This time I can't seem to unstick it with
Activity monitor, however going elsewhere (Safari, Mail, Activity monitor) did
seem to unstick it. The main consistent thing here is that I'm using xemacs.
Is nobody else seeing this stuck quartz-wm issue?
Jamie
On
Actually I found it quicker than I thought. There's mention of the "Activity
Monitor Trick" for un-hanging X11 in this Apple Discussion Forum thread:
http://discussions.apple.com/thread.jspa?threadID=1049889&start=0&tstart=0
Cheers,
Jamie
On Mar 31, 2011, at 8:30 AM, Jamie Kennea wrote:
> I s
I see this message:
[mi] EQ overflowing. The server is probably stuck in an infinite loop.
FYI, I'm working off hazy memories, and somewhat anecdotal evidence, but I
remember that the old hang in X11 used to be fixed by something odd like using
Activity Monitor. I'll have to Google at some poin
Hmm... so the sample just shows quartz-wm waiting for events (ie: idle).
It's odd that sampling quartz-wm would fix the issue for you. Are there any
messages like "quartz-wm: caught exception: ..." in /var/log/system.log?
On Mar 30, 2011, at 8:33 AM, Jamie Kennea wrote:
> Hi Jeremy,
>
> It ha
Hi Jeremy,
It happened again. This time with 2.6.1 final version.
I've attached the sample of quartz-wm. I verified that /opt/X11/bin/quartz-wm
is the version running.
Both times I was using xemacs. I remember xemacs in the past used to cause
hangs in X11 (back in the pre-you days), especiall
On Mar 24, 2011, at 3:55 PM, Peter Dyballa wrote:
>
> Am 24.03.2011 um 21:01 schrieb Jeremy Huddleston:
>
>> If you start X11 by launching an application from Terminal.app (or otherwise
>> trigger the launchd mechanism), X11.app won't run the initial xterm.
>
> What is "launching an applicati
Am 24.03.2011 um 21:01 schrieb Jeremy Huddleston:
If you start X11 by launching an application from Terminal.app (or
otherwise trigger the launchd mechanism), X11.app won't run the
initial xterm.
What is "launching an application from Terminal.app" and what is
"otherwise trigger the laun
On Mar 24, 2011, at 12:40 PM, Peter Dyballa wrote:
> Am 24.03.2011 um 20:37 schrieb Jeremy Huddleston:
>
>>> Then all X servers on Leopard were faulty until X11-2.6.1 was released...
>>
>> I don't think so...
>
> Before a week ago, or such, I never had this xterm...
If you start X11 by launch
Am 24.03.2011 um 20:37 schrieb Jeremy Huddleston:
Then all X servers on Leopard were faulty until X11-2.6.1 was
released...
I don't think so...
Before a week ago, or such, I never had this xterm...
--
Greetings
Pete
Isn't vi that text editor with two modes... one that beeps and one
On Mar 24, 2011, at 10:35 AM, Peter Dyballa wrote:
>
> Am 24.03.2011 um 17:57 schrieb Jeremy Huddleston:
>
>> Those are the default values (and have been the default values) since
>> Leopard 10.5.0 shipped.
>
>
> Then all X servers on Leopard were faulty until X11-2.6.1 was released...
I do
Am 24.03.2011 um 17:57 schrieb Jeremy Huddleston:
Those are the default values (and have been the default values)
since Leopard 10.5.0 shipped.
Then all X servers on Leopard were faulty until X11-2.6.1 was
released...
--
Greetings
Pete (:
_/ __--
_/ \_
On Mar 24, 2011, at 3:20 AM, Peter Dyballa wrote:
>
> Am 24.03.2011 um 02:00 schrieb Jeremy Huddleston:
>
>> There was certainly nothing intentional done to "reset" preferences or
>> anything like that...
>
>
> It has an entry
>
>"app_to_run" = "/usr/X11/bin/xterm";
>
> The entry
>
>
Am 24.03.2011 um 02:00 schrieb Jeremy Huddleston:
There was certainly nothing intentional done to "reset" preferences
or anything like that...
It has an entry
"app_to_run" = "/usr/X11/bin/xterm";
The entry
"app_to_run" = "/opt/local/bin/xterm";
appears in org.macports.X11.plist.
On Mar 23, 2011, at 17:27, Dave Ray wrote:
> Peter Dyballa wrote:
>
>> The final release has a strange habit: it launches an extra xterm! How
>> can I stop it doing so?...
>
> I'm not sure if this is related to your extra xterm. I noticed in 2.6.1_final
> seems to reset my plist, it reverted
Peter Dyballa wrote:
> The final release has a strange habit: it launches an extra xterm! How
> can I stop it doing so?...
I'm not sure if this is related to your extra xterm. I noticed in 2.6.1_final
seems to reset my plist, it reverted to the default which opens an xterm from
launchd. I fol
Am 19.03.2011 um 18:41 schrieb Jeremy Huddleston:
You might as well try the final release (2.6.1).
The final release has a strange habit: it launches an extra xterm! How
can I stop it doing so? I really don't need it, the *shell* buffer in
GNU Emacs is much better (and now even quite ANSI
Am 22.03.2011 um 17:28 schrieb Jeremy Huddleston:
So X11_Legacy shows your emacs issue still? If that's the case,
then it definitely sounds like this is a client issue and not a
server issue.
The same client, i.e., the same C and ELisp code, when linked with
libraries from Fink and /usr
On Mar 22, 2011, at 04:56, Peter Dyballa wrote:
>
> Am 22.03.2011 um 01:06 schrieb Jeremy Huddleston:
>
>> 1) sudo rm -rf /usr/X11* /Applications/Utilities/X11.app
>> /System/LuanchAgents/org.*.startx.plist
>> 2) Install 2.2.0
>> 3) Logout
>
>
> I found only 2.2.0.1 – and it shows the effect
On Mar 22, 2011, at 04:51, Peter Dyballa wrote:
>
> Am 22.03.2011 um 01:01 schrieb Jeremy Huddleston:
>
>> which is why I told you to keep /usr/X11 from 2.6.1 if you want to use
>> X11_Legacy, so your fink and quartz-wm will resolve right ...
>
> I did save these files, but I did not understa
Am 22.03.2011 um 01:06 schrieb Jeremy Huddleston:
1) sudo rm -rf /usr/X11* /Applications/Utilities/X11.app /System/
LuanchAgents/org.*.startx.plist
2) Install 2.2.0
3) Logout
I found only 2.2.0.1 – and it shows the effect. And much more!
X11-2.2.0.1.pkg: X.org Release 7.2, X.Org X Server 1
Am 22.03.2011 um 01:01 schrieb Jeremy Huddleston:
which is why I told you to keep /usr/X11 from 2.6.1 if you want to
use X11_Legacy, so your fink and quartz-wm will resolve right ...
I did save these files, but I did not understand that this X11_Legacy
package is not complete and needs oth
> For download available are these early packages:
>
> • X11-2.1.0.1.pkg
> • X11-2.1.2.pkg
> • X11-2.1.3.pkg
> • X11-2.1.4.pkg
Those you don't want. Those are installs that go over the original 2.0.0 from
Apple and are not full releases. They won't work with your instal
On Mar 21, 2011, at 10:20, Peter Dyballa wrote:
>
> Am 21.03.2011 um 17:16 schrieb Jeremy Huddleston:
>
>> 2) Apple's Leopard X11.app
>> Install X11User.pkg from your install DVD.
>
> After this some X clients launch, but
>
> -rwxr-xr-x 1 root wheel 189432 18 Mai 2009 /usr/bin/quartz-wm
>
Am 21.03.2011 um 17:16 schrieb Jeremy Huddleston:
2) Apple's Leopard X11.app
Install X11User.pkg from your install DVD. Then install the 10.5.8
Combo update. Since you have 10.5.4, my guess is that this is where
you got your working 1.3.0-apple5 version from.
I have now X.Org X Server 1
Am 21.03.2011 um 17:16 schrieb Jeremy Huddleston:
2) Apple's Leopard X11.app
Install X11User.pkg from your install DVD.
After this some X clients launch, but
-rwxr-xr-x 1 root wheel 189432 18 Mai 2009 /usr/bin/quartz-wm
fails. System.log starts with:
Mar 21 17:58:48 localhost org.x.X11
On Mar 21, 2011, at 10:12, Peter Dyballa wrote:
>> I only mentioned 2.1.1 after you mentioned the 1.3.0-apple5 server. I'm
>> just saying you should figure out when the problem was introduced. YOU
>> mentioned that it worked in 1.3.0-apple5. 1.3.0-apple5 comes with either
>> 2.1.1, or Mac O
Am 21.03.2011 um 17:00 schrieb Jeremy Huddleston:
Are you saying that your rendering issue is ok in 1.3.0-apple5
and present in 1.5.3-apple14?
Exactly! The XFree86 Version 4.4.0 X server is top!
? What do you mean by that? X11_Legacy.pkg, or 1.3.0-apple5?
Where are you getting 1.3.0-
On Mar 21, 2011, at 02:54, Peter Dyballa wrote:
>
> Am 21.03.2011 um 05:44 schrieb Jeremy Huddleston:
>
>>> XQuartz 2.3.1 (xorg-server 1.4.2-apple17), Build Date: 20080905, from
>>> X11-2.3.1.pkg: unreadable Emacsen frames/windows. Uses files from
>>> ~/.xinitrc.d; has a lot of problems (dyld
On Mar 21, 2011, at 02:44, Peter Dyballa wrote:
>
> Am 21.03.2011 um 05:43 schrieb Jeremy Huddleston:
>
Are you saying that your rendering issue is ok in 1.3.0-apple5 and present
in 1.5.3-apple14?
>>>
>>>
>>> Exactly! The XFree86 Version 4.4.0 X server is top!
>>
>> ? What do you
Am 21.03.2011 um 05:44 schrieb Jeremy Huddleston:
XQuartz 2.3.1 (xorg-server 1.4.2-apple17), Build Date: 20080905,
from X11-2.3.1.pkg: unreadable Emacsen frames/windows. Uses files
from ~/.xinitrc.d; has a lot of problems (dyld: Symbol not found
_xp_set_), because I did not sudo cp /usr/li
Am 21.03.2011 um 05:43 schrieb Jeremy Huddleston:
Are you saying that your rendering issue is ok in 1.3.0-apple5 and
present in 1.5.3-apple14?
Exactly! The XFree86 Version 4.4.0 X server is top!
? What do you mean by that? X11_Legacy.pkg, or 1.3.0-apple5?
Where are you getting 1.3.0-
If you're going to try older servers via the pkg installer, please remove the
existing install first (information detailed in an earlier email or in the
FAQ)... The Leopard package maker had a bug for a few versions that didn't work
well with downgrades.
On Mar 20, 2011, at 16:31, Peter Dyballa
On Mar 20, 2011, at 13:50, Peter Dyballa wrote:
>
> Am 20.03.2011 um 18:06 schrieb Jeremy Huddleston:
>
>> Please try the latest 1.4.x server as it should work with the new model and
>> will tell me if your issue came between 1.3.x and 1.4.x or between 1.4.x and
>> 1.5.x
>
>
> XQuartz 2.3.1
On Mar 20, 2011, at 12:44, Peter Dyballa wrote:
>
> Am 20.03.2011 um 18:06 schrieb Jeremy Huddleston:
>
>> Are you saying that your rendering issue is ok in 1.3.0-apple5 and present
>> in 1.5.3-apple14?
>
>
> Exactly! The XFree86 Version 4.4.0 X server is top!
? What do you mean by that?
Am 20.03.2011 um 18:06 schrieb Jeremy Huddleston:
Please try the latest 1.4.x server as it should work with the new
model and will tell me if your issue came between 1.3.x and 1.4.x or
between 1.4.x and 1.5.x
X11-2.3.1.pkg does not work! Even after re-installation. I see a
second X serv
Am 20.03.2011 um 18:06 schrieb Jeremy Huddleston:
Please try the latest 1.4.x server as it should work with the new
model and will tell me if your issue came between 1.3.x and 1.4.x or
between 1.4.x and 1.5.x
There seems to be something wrong with X11-2.3.1.pkg: It launches
XQuartz 2.6.
Am 20.03.2011 um 18:06 schrieb Jeremy Huddleston:
Please try the latest 1.4.x server as it should work with the new
model and will tell me if your issue came between 1.3.x and 1.4.x or
between 1.4.x and 1.5.x
XQuartz 2.3.1 (xorg-server 1.4.2-apple17), Build Date: 20080905, from
X11-2.3.
Am 20.03.2011 um 18:06 schrieb Jeremy Huddleston:
Are you saying that your rendering issue is ok in 1.3.0-apple5 and
present in 1.5.3-apple14?
Exactly! The XFree86 Version 4.4.0 X server is top! (The whole week,
since last weekend, I booted at night into Tiger to work, mostly
automatic,
I'm having trouble picking through what you've written here...
Are you saying that your rendering issue is ok in 1.3.0-apple5 and present in
1.5.3-apple14?
Some of the intermediate builds will be difficult to try since the startup
process changed a bit around 2.4.0 in order to allow different
On Mar 20, 2011, at 03:46, Peter Dyballa wrote:
>> The MacPorts X server does not set anything as $HOME.
>
> OK! Instead of at $HOME I land (get logged) in /.
Switch xterm to use login shells to work around this. Put this in
~/.Xresources:
XTerm*loginShell: True
>> The startup models
Am 19.03.2011 um 22:19 schrieb Jeremy Huddleston:
You can always install the Tiger version of X11 on Leopard from:
http://static.macosforge.org/xquartz/downloads/Leopard/X11_Legacy-1.1.4.1.pkg
Using /opt/local/bin/quartz-wm, which is obviously used by default,
without ~/.xinitrc file, ever
Am 19.03.2011 um 22:19 schrieb Jeremy Huddleston:
As I described: The MacPorts X server sets / as $HOME and blackbox
crashes when LC_CTYPE or LANG have a value with UTF-8, the /usr/X11
or XQuartz server works correctly, follows ~/.MacOSX/
environment.plist and keeps blackbox from crashing a
On Mar 19, 2011, at 13:52, Peter Dyballa wrote:
>>> The good news: blackbox 0.71 accepts, i.e. does not crash, when LC_CTYPE
>>> and/or LANG are set to some UTF-8 value:
>>
>> Well, I'm glad blackbox got a bugfix, you should mention this in your
>> MacPorts ticket.
>
> There is *no* bugfix, j
Am 19.03.2011 um 18:41 schrieb Jeremy Huddleston:
As before the fonts in text panes or widgets in GNU Emacs become
unreadable in the end. This means: GNU Emacs 23.3 (stable) and GNU
Emacs 24.0.50 (unstable) start in some default mode. Then they
reset themselves to using whatever X resource
On Mar 18, 2011, at 14:16, Peter Dyballa wrote:
>
> Am 06.03.2011 um 03:59 schrieb Jeremy Huddleston:
>
>> I've just uploaded 2.6.1_rc1 for both Leopard and Snow Leopard.
>
>
> I am trying it right now.
You might as well try the final release (2.6.1).
> As before the fonts in text panes or
Am 06.03.2011 um 03:59 schrieb Jeremy Huddleston:
I've just uploaded 2.6.1_rc1 for both Leopard and Snow Leopard.
I am trying it right now. As before the fonts in text panes or widgets
in GNU Emacs become unreadable in the end. This means: GNU Emacs 23.3
(stable) and GNU Emacs 24.0.50 (u
Weird. If it happens again, please also get a sample of the quartz-wm process.
Thanks,
Jeremy
On Mar 18, 2011, at 11:12, Jamie Kennea wrote:
>
> On Mar 18, 2011, at 12:09 PM, Jeremy Huddleston wrote:
>
>> Yeah. This sounds a lot like quartz-wm has grabbed the pointer and not
>> released it.
On Mar 18, 2011, at 12:09 PM, Jeremy Huddleston wrote:
> Yeah. This sounds a lot like quartz-wm has grabbed the pointer and not
> released it. This was a problem in the past but should be fixed with recent
> versions. Can you verify that the correct quartz-wm is being run? 'ps aux |
> grep
On Mar 18, 2011, at 07:19, Jamie Kennea wrote:
> Perhaps I should point out at this point that I can't move the windows.
> Clicking on them just seems to have no effect, either focus, closing or
> dragging. I guess this probably means the bug is in quartz-wm?
Yeah. This sounds a lot like quar
On Mar 17, 2011, at 6:53 PM, Jeremy Huddleston wrote:
> Hey Jamie,
>
> Can you run these (from Terminal.app, since you obviously can't access your
> X11 windows):
> xinput test pointer
> xeyes
> xev
Actually running from an xterm isn't a problem as I can get focus on it with
Expose. ;)
> Try
Hey Jamie,
Can you run these (from Terminal.app, since you obviously can't access your X11
windows):
xinput test pointer
xeyes
xev
Try interacting with the xev window. Does it respond to mouse/kbd input? Does
xeyes follow your pointer? Does xinput print out mouse clicks?
Are you able to cyc
Hi Jeremy,
I'm currently having a focus issue with 2.6.1_rc1 on Snow Leopard. I can only
focus on the most recently opened window, trying to click on other windows does
not result in them gaining focus. I don't have focus-follows-mouse enabled. I
note that I can get window focus by using select
Yep, I'm still including the workaround and probably will until I am able to
reproduce your problem (if ever).
On Mar 10, 2011, at 09:46, Christof Wolf wrote:
> Jeremy,
>
> I just installed 2.6.1 rc1 on my macbook air - everything looks fine and is
> working :-)
>
> ciao
> christof
> --
> p
Jeremy,
I just installed 2.6.1 rc1 on my macbook air - everything looks fine and is
working :-)
ciao
christof
--
public key www.hfph.mwn.de/~chwolf/ch.wolf.asc
Please respect my privacy and do not make my contact information
available to third parties.
This email is UNCLASSIFIED.
___
I've just uploaded 2.6.1_rc1 for both Leopard and Snow Leopard. This pulls in
a few more fixes for RandR and should address the "xterm changes background
color" issue that cropped up a few releases ago. There are still a couple
RandR related issues that I want to tackle before the final releas
55 matches
Mail list logo
