Hi everyone, Since releasing 2.3.3, I've been spending my time working on the 1.5 server branch. I've been chipping away at the regressions that had been introduced over 1.4, and they are mostly cleared out now. Well... at least the ones I'm aware of. Two changes of note: 1) I believe a possible deadlock with 8bit visuals has been fixed that was reported in 2.3.3.2. Hopefully someone can confirm this for me. 2) I added support to quit X11 when the last window is closed. This was a requested feature a while back, so here it is. It's documented in the man page for quartz-wm, but I don't intend to make a GUI checkbox for it. defaults write org.x.X11 wm_auto_quit -bool true The full ChangeLog is available here: http://xquartz.macosforge.org/trac/wiki/ChangeLog And here's the DMG link: http://static.macosforge.org/xquartz/downloads/X11-2.4.0_beta2.dmg The only remaining known regression with this release affects users who have a ~/.Xmodmap file. There is a race condition to setup the keyboard mappings when this file is present. The results are unpredictable, and I recommend moving this file aside for the time being and running xmodmap manually once X11 has started up. Thanks, Jeremy
On Fri, Jun 5, 2009 at 11:36 AM, Jeremy Huddleston<jeremyhu@apple.com> wrote:
Hi everyone,
Since releasing 2.3.3, I've been spending my time working on the 1.5 server branch. I've been chipping away at the regressions that had been introduced over 1.4, and they are mostly cleared out now. Well... at least the ones I'm aware of.
Two changes of note: 1) I believe a possible deadlock with 8bit visuals has been fixed that was reported in 2.3.3.2. Hopefully someone can confirm this for me.
2) I added support to quit X11 when the last window is closed. This was a requested feature a while back, so here it is. It's documented in the man page for quartz-wm, but I don't intend to make a GUI checkbox for it.
defaults write org.x.X11 wm_auto_quit -bool true
Whoah, that was me! A feature implemented just for me!? Sweet! Christmas! Thanks, Jeremy! I'm going to download it right now, though I won't be able to really seriously try it out until work on Monday. ~ Nathan
On Jun 6, 2009, at 2:52 AM, Nathan wrote:
On Fri, Jun 5, 2009 at 11:36 AM, Jeremy Huddleston<jeremyhu@apple.com> wrote:
2) I added support to quit X11 when the last window is closed. This was a requested feature a while back, so here it is. It's documented in the man page for quartz-wm, but I don't intend to make a GUI checkbox for it.
defaults write org.x.X11 wm_auto_quit -bool true
Whoah, that was me! A feature implemented just for me!? Sweet! Christmas!
You may have been the one to ask for it (or the one to ask loudly), but it's really useful. Matches the auto-open very well. Thanks, Jeremy! ~~ Brian
oopps, this "feature" may give sou some trouble. If an app launches a splash screen which closes before the main window is opened... the XServer shuts down and now the app can't connect to the XServer. I just got a bug report about this issue from a user, who couldn't launch GIMP any longer since he had enabled auto-shutdown. Disabling auto-shutdown solved it. The same issue should occur if you log into a remote computer using 'ssh -X' and start any xclient. After you quit the xclient,and if this was the last X window, XQuartz quits too, leaving the ssh connetion in an unusable state. Yeah, this is really some sort of "auto-shutdown". No matter what you want to do, it will shut down your app and the XServer automatically. ;-) (SCNR) So I vote to drop this auto-shutdown switch to avoid users getting into trouble. skl http://gimp.lisanet.de
defaults write org.x.X11 wm_auto_quit -bool true
Whoah, that was me! A feature implemented just for me!? Sweet! Christmas!
Thanks, Jeremy! I'm going to download it right now, though I won't be able to really seriously try it out until work on Monday.
On Jun 11, 2009, at 15:57, Simone Karin Lehmann wrote:
I just got a bug report about this issue from a user, who couldn't launch GIMP any longer since he had enabled auto-shutdown. Disabling auto-shutdown solved it.
Yeah, that would be the effect... perhaps I can add a timer for this... so if it's still at 0 after a few seconds...
The same issue should occur if you log into a remote computer using 'ssh -X' and start any xclient. After you quit the xclient,and if this was the last X window, XQuartz quits too, leaving the ssh connetion in an unusable state.
Really? Why would ssh be in an unusable state? I agree that the X client that did an XOpenDisplay may be in an unusable state, but ssh and new clients should be fine.
Yeah, this is really some sort of "auto-shutdown".
Yeah, that's the idea.
No matter what you want to do, it will shut down your app and the XServer automatically. ;-) (SCNR)
Yep, that's the intention.
So I vote to drop this auto-shutdown switch to avoid users getting into trouble.
Well if the user read the man-page and set the option themselves, they should be aware of the issue. That being said, I agree that adding a timeout would be better than quitting immediately to handle the use case you described above.
skl
defaults write org.x.X11 wm_auto_quit -bool true
Whoah, that was me! A feature implemented just for me!? Sweet! Christmas!
Thanks, Jeremy! I'm going to download it right now, though I won't be able to really seriously try it out until work on Monday.
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
On 11Jun2009 17:02, Jeremy Huddleston <jeremyhu@apple.com> wrote:
On Jun 11, 2009, at 15:57, Simone Karin Lehmann wrote:
I just got a bug report about this issue from a user, who couldn't launch GIMP any longer since he had enabled auto-shutdown. Disabling auto-shutdown solved it.
Yeah, that would be the effect... perhaps I can add a timer for this... so if it's still at 0 after a few seconds...
What about counting active X11 connections instead of windows? An app with a splash screen should survive ok with that. No good for "ssh -Y", but it at least seems less fragile. Cheers, -- Cameron Simpson <cs@zip.com.au> DoD#743 http://www.cskk.ezoshosting.com/cs/ Do what you think is interesting, do something that you think is fun and worthwhile, because otherwise you won't do it well anyway. - Brian Kernighan
On Jun 11, 2009, at 23:15, Cameron Simpson wrote:
On 11Jun2009 17:02, Jeremy Huddleston <jeremyhu@apple.com> wrote:
On Jun 11, 2009, at 15:57, Simone Karin Lehmann wrote:
I just got a bug report about this issue from a user, who couldn't launch GIMP any longer since he had enabled auto-shutdown. Disabling auto-shutdown solved it.
Yeah, that would be the effect... perhaps I can add a timer for this... so if it's still at 0 after a few seconds...
What about counting active X11 connections instead of windows? An app with a splash screen should survive ok with that.
The window manager doesn't know about active connections. At this time, I don't intend to build this functionality into the server itself.
On 12Jun2009 00:11, Jeremy Huddleston <jeremyhu@apple.com> wrote:
On Jun 11, 2009, at 23:15, Cameron Simpson wrote:
On 11Jun2009 17:02, Jeremy Huddleston <jeremyhu@apple.com> wrote:
On Jun 11, 2009, at 15:57, Simone Karin Lehmann wrote:
I just got a bug report about this issue from a user, who couldn't launch GIMP any longer since he had enabled auto-shutdown. Disabling auto-shutdown solved it.
Yeah, that would be the effect... perhaps I can add a timer for this... so if it's still at 0 after a few seconds...
What about counting active X11 connections instead of windows? An app with a splash screen should survive ok with that.
The window manager doesn't know about active connections.
At this time, I don't intend to build this functionality into the server itself.
Ah. I had taken this to be in the server. Forget I said anything then... -- Cameron Simpson <cs@zip.com.au> DoD#743 http://www.cskk.ezoshosting.com/cs/ Churchill's Commentary on Man: Man will occasionally stumble over the truth, but most of the time he will pick himself up and continue on.
Hi Jeremy! Am 12.06.2009 um 02:02 schrieb Jeremy Huddleston:
Well if the user read the man-page and set the option themselves, they should be aware of the issue. That being said, I agree that adding a timeout would be better than quitting immediately to handle the use case you described above.
I am the user whom Simone talks of. :-) I have installed the latest XQuartz 2.4.0beta, and I have installed the latest Gimp 2.6.6. I've had enabled this new switch "wm_auto_quit" to test and play a little bit with it. Because I appreciate this switch, too.:-) I've tested it with Gimp, I've tested it with Inkscape. Because Inkscape starts and works very well with this XQuartz 2.4.0beta (and "wm_auto_quit" true), but Gimp quits right after finishing its splash screen, I sent an email with my log file esssence to Simone, because my first thought of cause has NOT been XQuartz' X11 but Gimp. Why? Because Inkscape starts and works without any problem (as well as X11 alone without any other X11 application started). That's why I asked Simone, if the cause could've been Gimp itself. Together with the help of Simone, I could reduce the cause to this issue very quickly to this new "wm_auto_quit" switch and turned it off again to its default value. Gimp uses a splash screen which causes this trouble when quitting and this new "wm_auto_quit" is enabled, so that the following main X11 window of Gimp hasn't any chance to come up. With this new switch enabled, Gimp is unusable, because the start of its main application window will be aborted too early (because auf the splash screen). So I very appreciate your proposal to add a reasonable chosen timeout to this new "wm_auto_quit" switch, which hence doesn't let any X11 application with a splash screen (like Gimp) abort/quit too early. Sierk -- Sierk Bornemann http://sierkbornemann.de/
On Thu, Jun 11, 2009 at 4:57 PM, Simone Karin Lehmann<simone@lisanet.de> wrote:
oopps, this "feature" may give sou some trouble. If an app launches a splash screen which closes before the main window is opened... the XServer shuts down and now the app can't connect to the XServer. I just got a bug report about this issue from a user, who couldn't launch GIMP any longer since he had enabled auto-shutdown. Disabling auto-shutdown solved it. The same issue should occur if you log into a remote computer using 'ssh -X' and start any xclient. After you quit the xclient,and if this was the last X window, XQuartz quits too, leaving the ssh connetion in an unusable state. Yeah, this is really some sort of "auto-shutdown". No matter what you want to do, it will shut down your app and the XServer automatically. ;-) (SCNR) So I vote to drop this auto-shutdown switch to avoid users getting into trouble.
The user already has to discover that the option even exists, and then manually configure it via the command-line. If they're able to do that, surely they'll be competent enough to turn it back off if they have problems with it(!?). It's a very useful feature for some of us. If anyone were to revisit the feature, I would vote for further refining it instead of excising it. ~ Nathan
Am 12.06.2009 um 22:55 schrieb Nathan:
The user already has to discover that the option even exists, and then manually configure it via the command-line. If they're able to do that, surely they'll be competent enough to turn it back off if they have problems with it(!?).
Done. See my last posting to Jeremy. :-)
It's a very useful feature for some of us.
Yes, I back that, I underline that. :-)
If anyone were to revisit the feature, I would vote for further refining it instead of excising it.
+1 Sierk -- Sierk Bornemann http://sierkbornemann.de/
participants (6)
-
Brian Gernhardt
-
Cameron Simpson
-
Jeremy Huddleston
-
Nathan
-
Sierk Bornemann
-
Simone Karin Lehmann