I just uploaded XQuartz-2.7.1_rc2 to the servers for download. There have been a few minor changes since the previous rc, but most importantly have been bugfixes to quartz-wm and some changes made to how quartz-wm activates windows. I'm hoping that this change might work around the "X11 looses focus" bug that I've never been able to reproduce. If you are able to reproduce this issue (http://xquartz.macosforge.org/trac/ticket/58), please try out this release and let me know if the issue is still present. Thanks, Jeremy http://static.macosforge.org/xquartz/downloads/SL/XQuartz-2.7.1_rc2.dmg
Jeremy Huddleston <jeremyhu@apple.com> writes:
I just uploaded XQuartz-2.7.1_rc2 to the servers for download.
In light usage I've seen it crash twice since downloading it (all windows suddenly close, xquartz isn't running anymore according to the dock). No such problem observed with rc1, or indeed any previous release. The case just now seemed to be triggered by hitting command-3 to open a previously-minimized window, but AFAIR that was not what I was doing the first time. How would I go about gathering info for a useful bug report? I see nothing in the system log for instance. regards, tom lane
On Jan 29, 2012, at 09:25, Tom Lane wrote:
Jeremy Huddleston <jeremyhu@apple.com> writes:
I just uploaded XQuartz-2.7.1_rc2 to the servers for download.
In light usage I've seen it crash twice since downloading it (all windows suddenly close, xquartz isn't running anymore according to the dock). No such problem observed with rc1, or indeed any previous release. The case just now seemed to be triggered by hitting command-3 to open a previously-minimized window, but AFAIR that was not what I was doing the first time.
How would I go about gathering info for a useful bug report? I see nothing in the system log for instance.
Please open a new bug report with the following attached: /var/log/system.log ~/Library/Log/org.macosforge.xquartz.X11.log ~/Library/Logs/DiagnosticReports/X11* ~/Library/Logs/DiagnosticReports/quartz-wm* Did a crash report appear on your screen? If not, it's possible that quartz-wm crashed rather than X11 itself (you should see a quartz-wm crash report in ~/Library/Logs/DiagnosticReports/ if that was the case).
Jeremy Huddleston <jeremyhu@apple.com> writes:
On Jan 29, 2012, at 09:25, Tom Lane wrote:
How would I go about gathering info for a useful bug report? I see nothing in the system log for instance.
Please open a new bug report with the following attached: /var/log/system.log ~/Library/Log/org.macosforge.xquartz.X11.log ~/Library/Logs/DiagnosticReports/X11* ~/Library/Logs/DiagnosticReports/quartz-wm*
Done at tickets 538 and 539, though by the time I got this I no longer had anything relevant in X11.org.macosforge.xquartz.log due to multiple restarts.
Did a crash report appear on your screen?
Nope.
If not, it's possible that quartz-wm crashed rather than X11 itself (you should see a quartz-wm crash report in ~/Library/Logs/DiagnosticReports/ if that was the case).
Yeah, looks like quartz-wm is the problem. regards, tom lane
Ok, thanks. I'll take a look at this and try to get a 2.7.1_rc3 out this week some time with the fix. I also have some other server fixes for some minor annoyances which I'd like to get tested before the final release, so another rc seems in order. Thanks for reporting. I think I have what I need. On Jan 29, 2012, at 12:20, Tom Lane wrote:
Jeremy Huddleston <jeremyhu@apple.com> writes:
On Jan 29, 2012, at 09:25, Tom Lane wrote:
How would I go about gathering info for a useful bug report? I see nothing in the system log for instance.
Please open a new bug report with the following attached: /var/log/system.log ~/Library/Log/org.macosforge.xquartz.X11.log ~/Library/Logs/DiagnosticReports/X11* ~/Library/Logs/DiagnosticReports/quartz-wm*
Done at tickets 538 and 539, though by the time I got this I no longer had anything relevant in X11.org.macosforge.xquartz.log due to multiple restarts.
Did a crash report appear on your screen?
Nope.
If not, it's possible that quartz-wm crashed rather than X11 itself (you should see a quartz-wm crash report in ~/Library/Logs/DiagnosticReports/ if that was the case).
Yeah, looks like quartz-wm is the problem.
regards, tom lane
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
I see the following in /var/log/system.log when I have Safari running and multiple X11 windows open: Jan 29 13:49:15 grendal quartz-wm[61966]: kCGErrorIllegalArgument: CGSOrderWindowList Jan 29 13:49:15 grendal org.macosforge.xquartz.startx[61795]: Sun Jan 29 13:49:15 grendal.frinabulax.org quartz-wm[61966] <Error>: kCGErrorIllegalArgument: CGSOrderWindowList Jan 29 14:56:21 grendal quartz-wm[61966]: kCGErrorIllegalArgument: CGSOrderWindowList Jan 29 14:56:21 grendal org.macosforge.xquartz.startx[61795]: Sun Jan 29 14:56:21 grendal.frinabulax.org quartz-wm[61966] <Error>: kCGErrorIllegalArgument: CGSOrderWindowList Also, I still see the loss of focus, but now I have to click to get focus back to the formerly active X11 window I have all three Preferences "On" in the Windows Tab of X11 Preferences (click-through, focus-follows-mouse, and focus on new windows). Sun, 29 Jan 2012 (12:25 -0500 UTC) Tom Lane wrote:
Jeremy Huddleston <jeremyhu@apple.com> writes:
I just uploaded XQuartz-2.7.1_rc2 to the servers for download.
In light usage I've seen it crash twice since downloading it (all windows suddenly close, xquartz isn't running anymore according to the dock). No such problem observed with rc1, or indeed any previous release. The case just now seemed to be triggered by hitting command-3 to open a previously-minimized window, but AFAIR that was not what I was doing the first time.
How would I go about gathering info for a useful bug report? I see nothing in the system log for instance.
regards, tom lane
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
-- The 10,000 things have 10,000 different states, all in motion as if there were a True Lord to move them--but if we search for evidence of this Lord we fail to find any. -Kuo Hsiang 18:18 up 60 days, 11:20, 1 user, load averages: 0.27 0.23 0.19
Am 28.1.2012 um 20:37 schrieb Jeremy Huddleston:
I'm hoping that this change might work around the "X11 looses focus" bug that I've never been able to reproduce.
I seem to have had this bug. For me other X clients received the focus (a timing problem?) maybe because the non-X cursor was hovering over some X client when I was working with non-X tools. I usually could normalise this by clicking into the X title bar (provided by blackboxwm) of gkrellm. The only effect I see is that one X client, the rather rarely used GNU Emacs 23.3 from MacPorts with Motif widgets, gets pushed on top of all the non-X windows. This is a piece of progress. Thank you, Jeremy! -- Greetings Pete For some reason, this fortune reminds everyone of Marvin Zelkowitz.
Am 28.1.2012 um 20:37 schrieb Jeremy Huddleston:
I'm hoping that this change might work around the "X11 looses focus" bug that I've never been able to reproduce.
I have to correct my previous post: this focus bug still exists. I would have needed to wait (and work) a bit more (five days running time, ten or more times sending the Mac to sleep and awakening it from sleep) to encounter it again. On a mixed spaces desktop with native Mac OS X applications and X11 windows when I click on an X client's window with the mouse this event goes through the X client and hits a native application. Then it's not possible to select any GNU Emacs window. In this situation it can happen that I start a text selection in an X window lying under the top most one. The situation can be made normal when I select the title bar of gkrellm. -- Greetings Pete Only useless documentation transcends the first two laws. – Arnold's Third Law of Documentation
If clicking on an X11 window results in the click being sent to another X11 window, that is an issue in X11. I remember that bug existed back in the early Leopard days, but I haven't heard of it since then. This sounds different. You're clicking on an X11 window, and the click is being sent to a window in another application. That is certainly wrong, but different than the issue I was remembering. Can you please create a screencapture of this happening using Quicktime X? FWIW, I don't think this is an X11 issue because that button press is never sent to X11 for us to redirect it elsewhere... On Feb 4, 2012, at 04:20, Peter Dyballa wrote:
Am 28.1.2012 um 20:37 schrieb Jeremy Huddleston:
I'm hoping that this change might work around the "X11 looses focus" bug that I've never been able to reproduce.
I have to correct my previous post: this focus bug still exists. I would have needed to wait (and work) a bit more (five days running time, ten or more times sending the Mac to sleep and awakening it from sleep) to encounter it again. On a mixed spaces desktop with native Mac OS X applications and X11 windows when I click on an X client's window with the mouse this event goes through the X client and hits a native application. Then it's not possible to select any GNU Emacs window. In this situation it can happen that I start a text selection in an X window lying under the top most one. The situation can be made normal when I select the title bar of gkrellm.
-- Greetings
Pete
Only useless documentation transcends the first two laws. – Arnold's Third Law of Documentation
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Am 4.2.2012 um 20:15 schrieb Jeremy Huddleston:
Can you please create a screencapture of this happening using Quicktime X?
The two behaviours I described exist in Leopard (PPC) and Snow Leopard (intel) since the beginning. They are not easily reproduced. They happen rather rarely so that I am not able to see a law or rule, to see marginal conditions except that many windows need to be layered. To record this, Quicktime X would need to work like a video recorder in a bank or gas station: work for hours in an infinite loop but save only the last few minutes. And is the Quicktime X the "free" product that comes on a Mac OS X install DVD? -- Greetings Pete America believes in education: the average professor earns more money in a year than a professional athlete earns in a whole week. – Evan Esar
[Peter Dyballa <Peter_Dyballa@Web.DE> (2012-02-04 21:34:43 UTC)]
And is the Quicktime X the "free" product that comes on a Mac OS X install DVD?
I assume that is what he meant. The QuickTime Player app on my mac is version 10.1 (hence the X, in my imagination), and it does have screen capture capabilities.
To record this, Quicktime X would need to work like a video recorder in a bank or gas station: work for hours in an infinite loop but save only the last few minutes.
It's possible you could make that happen with a bit of Applescript. Start a recording, stop it a couple minutes later, start a new one, remove all but the latest half dozen recordings, repeat. No, I am not volunteering to write the script. - Harald
Am 5.2.2012 um 10:33 schrieb Harald Hanche-Olsen:
The QuickTime Player app on my mac is version 10.1 (hence the X, in my imagination), and it does have screen capture capabilities.
I tried to use this feature a few minutes ago – and I had luck: clicking onto GNU Emacs put it at once below the native applications. But – there was no QuickTime Player anymore to stop and save the recording, though the process still existed and had created a file of over 300 MB in /private/var/folders. Probably because I had played with it before without actually starting the recording – as I thought. The red button is something universal, starting and stopping the recording session. Did anyone succeed in doing a New Screen Recording? -- Greetings Pete "Indentation?! I will show you how to indent when I indent your skull!"
On Feb 5, 2012, at 3:17 PM, Peter Dyballa wrote:
Am 5.2.2012 um 10:33 schrieb Harald Hanche-Olsen:
The QuickTime Player app on my mac is version 10.1 (hence the X, in my imagination), and it does have screen capture capabilities.
I tried to use this feature a few minutes ago – and I had luck: clicking onto GNU Emacs put it at once below the native applications. But – there was no QuickTime Player anymore to stop and save the recording, though the process still existed and had created a file of over 300 MB in /private/var/folders. Probably because I had played with it before without actually starting the recording – as I thought. The red button is something universal, starting and stopping the recording session.
Did anyone succeed in doing a New Screen Recording?
As explained when you start recording a screen session, the QuickTime Player interface is hidden so it doesn't interfere with the recording. There's a Stop Recording button in the menu bar. You can also stop it by pressing Command-Control-Esc. Regards, Ken
Am 4.2.2012 um 20:15 schrieb Jeremy Huddleston:
Can you please create a screencapture of this happening using Quicktime X?
Could you tell me the address of an FTP server? Sending the two movies be eMail fails – over 400 MB! -- Greetings Pete It's not the valleys in life I dread so much as the dips. – Garfield
Can you trim them down to the 15s or so which are relevant? You can put it on dropbox and share them with me. I'll send you an invite you can use if you're not already a user. --Jeremy On Feb 6, 2012, at 16:52, Peter Dyballa wrote:
Am 4.2.2012 um 20:15 schrieb Jeremy Huddleston:
Can you please create a screencapture of this happening using Quicktime X?
Could you tell me the address of an FTP server? Sending the two movies be eMail fails – over 400 MB!
-- Greetings
Pete
It's not the valleys in life I dread so much as the dips. – Garfield
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Am 7.2.2012 um 18:53 schrieb Jeremy Huddleston:
Can you trim them down to the 15s or so which are relevant?
They're 43 sec and 39 sec. Cuts won't give much. I'm going to set up a DropBox account and then upload the two files. -- Greetings Pete No matter which way you ride, it's uphill and against the wind. – First Law of Bicycling
Am 7.2.2012 um 18:53 schrieb Jeremy Huddleston:
You can put it on dropbox and share them with me.
In approximately 1 h, local midnight, the upload will have finished. -- Greetings Pete If you don't find it in the index, look very carefully through the entire catalogue. – Sears, Roebuck, and Co., Consumer's Guide, 1897
Thanks, I have them, and I'll take a look later this week. --Jeremy On Feb 7, 2012, at 2:11 PM, Peter Dyballa <Peter_Dyballa@web.de> wrote:
Am 7.2.2012 um 18:53 schrieb Jeremy Huddleston:
You can put it on dropbox and share them with me.
In approximately 1 h, local midnight, the upload will have finished.
-- Greetings
Pete
If you don't find it in the index, look very carefully through the entire catalogue. – Sears, Roebuck, and Co., Consumer's Guide, 1897
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
participants (6)
-
Harald Hanche-Olsen
-
Jeremy Huddleston
-
Ken Thomases
-
Peter Dyballa
-
robert delius royar
-
Tom Lane