November 2008 - Xquartz-dev - lists.macosforge.org

Menubar inaccessible if X11 window is behind it (2.3.2_beta3)
by Brian Bender 12 Nov '08

12 Nov '08

Hi Jeremy, Another oddity (not a showstopper, IMHO) that I haven't seen mentioned yet (but maybe related to the "geometry regression" conversation?): if an X11 window is higher (Y-axis) than the menu bar and has focus, you can't select the menu bar. I have that dual-screen setup where the top edges of the screens are uneven; my secondary display is above the level of the top of the menubar on my primary screen. If I have a window spanning both desktops and higher than the top of the main screen, as I move my pointer up to the menu bar it stays captured by the X11 window behind it, and goes behind the menubar. I'm unable to select the menu bar until I switch the focus away from X11.app (or move the window, obviously). It's not a big issue itself, but I thought it might help in tracking down other "weird things". - Brian

2 2

Re: [Xquartz-dev] Xquartz-dev Digest, Vol 13, Issue 8
by Sven de Vries 12 Nov '08

12 Nov '08

Hi, I installed 2.3.2_beta3 > What about the localisation of at least the new pasteboard screen of > the X11 preferences (see http://lists.macosforge.org/pipermail/xquartz-dev/attachments/20080922/6859… but I don't see that pasteboard screen (in X11->Preferences). any trick necessary to enable it? should I see xcutsel in ActiivtyMonitor (I don't)? thanks, sven

2 1

Re: [Xquartz-dev] geometry regression in 2.3.2-beta3
by robert delius royar 12 Nov '08

12 Nov '08

Tue, 11 Nov 2008 (21:26 -0800 UTC) Jeremy Huddleston wrote: > Well my emacs is using gtk2 for windowing... Is yours using motif maybe? > What is the output of 'ldd /usr/bin/emacs' on your Fedora box? > > On Nov 11, 2008, at 21:18, Tom Lane wrote: > > > I wrote: > > > Well, I'd be the first to admit that I'm using an ancient Emacs (19.34.1 > > > actually) ... but I wouldn't expect it to break between beta2 and beta3. > > > > Also, I'm getting the same behavior with emacs 22.2.1 ssh'd in from a > > reasonably up-to-date machine (Fedora 9). > > > > regards, tom lane I am seeing the same thing with xterm 237 (self compiled with the configuration ./configure --enable-wide-chars --enable-256-color \ --with-terminal-type=xterm-256color --enable-dabbrev \ --prefix=/usr/X11 --enable-mini-luit --enable-toolbar \ --with-X --with-Xaw3d CC=/usr/bin/gcc-4.2 ). The program flashes open at its requested geometry location then disappears and returns to 0,0. I see this in any xterm I open. I have some processes that start automatically at X11 initial startup which are set to begin iconified. When I de-iconify those xterms or XEmacs processes for the first time later in a session, they open where their initial geometry settings requested. The initial geometry was provided as a command-line parameter. Perhaps I need some additional Xresource values to fix this? I also see this with a 21.5.beta28 (latest hg sources) XEmacs. Finally, I use fspanel. It now obscures the OS X dock, but other X11 windows do not. fspanel is set to remain in the X foreground. I suspect that looking at the code might help discover where the problem came in. I have a modified version of fspanel which does not support separate desktops. But I did not modify the sections that keep it foregrounded. -- Dr. Robert Delius Royar <r.royar(a)morehead-st.edu> Associate Professor of English, Morehead State University

2 1

2.3.2_beta3
by Mike Krogh 12 Nov '08

12 Nov '08

Hi, I just installed 2.3.2_beta3 on my Leopard 10.5.5 MacBook and am having several problems with our X11 based application now. First, I tried to install X11-2.3.1.pkg after trying 2.3.2-beta3 but it crashes every time I try to start the X11 server. I've rebooted, reinstall a couple of times but no luck. X11 now just crashes immediately. How does one downgrade X11? Second, at least with 2.3.2_beta3 our application's dialogs now frequently, but not always, pop to the upper left corner of the desktop (dual monitors) after twiddling some of the dialog's widgets. Third, the application opens multiple connections to the X server since it uses both Motif and QT4. With 2.3.2_beta3, some dialogs created via PyQT are now causing the X11 server to crash; the main app is Motif based. Unfortunately, I have not been keeping up with all the 2.3.x updates so I don't know how far back this problem goes. Prior to this I was running 2.2.2 without these problems. I'll be happy to try the various 2.2.x and 2.3.x release to see when the problem was introduced if someone can tell me how to properly downgrade. Thanks! Mike

3 8

Re: [Xquartz-dev] geometry regression in 2.3.2-beta3
by Jeremy Huddleston 12 Nov '08

12 Nov '08

It works for me: ~ $ emacs -geometry 80x61-0+0 ~ $ emacs --version GNU Emacs 22.3.1 Copyright (C) 2008 Free Software Foundation, Inc. GNU Emacs comes with ABSOLUTELY NO WARRANTY. You may redistribute copies of Emacs under the terms of the GNU General Public License. For more information about these matters, see the file named COPYING. my xwininfo: xwininfo: Window id: 0x800014 "emacs@<snip>" Root window id: 0x3bd (the root window) (has no name) Parent window id: 0x60000b (has no name) 4 children: 0x80002f (has no name): () 516x793+0+65 +2844+365 2 children: 0x8000c3 (has no name): () 18x13+0+780 +2844+1145 0x8000c2 (has no name): () 18x767+0+0 +2844+365 0x80005f (has no name): () 516x38+0+27 +2844+327 1 child: 0x800060 (has no name): () 516x38+0+0 +2844+327 15 children: 0x8000e2 (has no name): () 34x34+449+2 +3293+329 1 child: 0x8000e3 (has no name): () 34x34+0+0 +3293+329 0x8000e0 (has no name): () 34x34+415+2 +3259+329 1 child: 0x8000e1 (has no name): () 34x34+0+0 +3259+329 0x8000de (has no name): () 34x34+381+2 +3225+329 1 child: 0x8000df (has no name): () 34x34+0+0 +3225+329 0x8000dc (has no name): () 34x34+347+2 +3191+329 1 child: 0x8000dd (has no name): () 34x34+0+0 +3191+329 0x8000da (has no name): () 34x34+313+2 +3157+329 1 child: 0x8000db (has no name): () 34x34+0+0 +3157+329 0x8000d8 (has no name): () 34x34+279+2 +3123+329 1 child: 0x8000d9 (has no name): () 34x34+0+0 +3123+329 0x8000d6 (has no name): () 34x34+245+2 +3089+329 1 child: 0x8000d7 (has no name): () 34x34+0+0 +3089+329 0x8000d4 (has no name): () 34x34+211+2 +3055+329 1 child: 0x8000d5 (has no name): () 34x34+0+0 +3055+329 0x8000d2 (has no name): () 34x34+177+2 +3021+329 1 child: 0x8000d3 (has no name): () 34x34+0+0 +3021+329 0x8000d0 (has no name): () 34x34+143+2 +2987+329 1 child: 0x8000d1 (has no name): () 34x34+0+0 +2987+329 0x8000ce (has no name): () 34x34+109+2 +2953+329 1 child: 0x8000cf (has no name): () 34x34+0+0 +2953+329 0x8000cc (has no name): () 29x34+80+2 +2924+329 1 child: 0x8000cd (has no name): () 29x34+0+0 +2924+329 0x8000ca (has no name): () 34x34+46+2 +2890+329 1 child: 0x8000cb (has no name): () 34x34+0+0 +2890+329 0x8000c8 (has no name): () 34x34+12+2 +2856+329 1 child: 0x8000c9 (has no name): () 34x34+0+0 +2856+329 0x800063 (has no name): () 506x38+10+0 +2854+327 0x800049 (has no name): () 516x27+0+0 +2844+300 6 children: 0x80005e (has no name): () 42x23+250+2 +3094+302 0x80005d (has no name): () 48x23+202+2 +3046+302 0x80005c (has no name): () 60x23+142+2 +2986+302 0x80005b (has no name): () 64x23+78+2 +2922+302 0x80005a (has no name): () 39x23+39+2 +2883+302 0x800059 (has no name): () 36x23+3+2 +2847+302 0x800015 (has no name): () 1x1+-1+-1 +2843+299 Absolute upper-left X: 2844 Absolute upper-left Y: 300 Relative upper-left X: 0 Relative upper-left Y: 22 Width: 516 Height: 858 Depth: 24 Visual Class: TrueColor Border width: 0 Class: InputOutput Colormap: 0x21 (installed) Bit Gravity State: NorthWestGravity Window Gravity State: NorthWestGravity Backing Store State: NotUseful Save Under State: no Map State: IsViewable Override Redirect State: no Corners: +2844+300 -0+300 -0-20 +2844-20 -geometry 80x61-0-20 Bit gravity: NorthWestGravity Window gravity: NorthWestGravity Backing-store hint: NotUseful Backing-planes to be preserved: 0xffffffff Backing pixel: 0 Save-unders: No Someone wants these events: KeyPress KeyRelease EnterWindow LeaveWindow Exposure StructureNotify FocusChange PropertyChange ColormapChange Do not propagate these events: Override redirection?: No Window manager hints: Client accepts input or input focus: Yes Initial state is Normal State Normal window size hints: User supplied location: 0, 0 User supplied size: 0 by 0 Program supplied minimum size: 48 by 91 Program supplied base size: 36 by 65 Program supplied x resize increment: 6 Program supplied y resize increment: 13 User supplied size in resize increments: 0 by 0 Program supplied minimum size in resize increments: 8 by 7 Program supplied base size in resize increments: 6 by 5 Program supplied window gravity: NorthWestGravity No zoom window size hints defined No window shape defined No border shape defined On Nov 11, 2008, at 20:18, Tom Lane wrote: > Jeremy Huddleston <jeremyhu(a)apple.com> writes: >> What does 'xwininfo -all' say about this window? > > Attached. I've since found that no set of position coordinates will > be > honored :-( ... the size coordinates are fine, but the window ends up > at top left no matter what the last two numbers are. > > (It's interesting that what's shown as the -geometry is +0+0 ... > that's most certainly not what's in the environment...) > > Oh ... not sure if this is relevant, but I should probably mention > that this is a remote client coming in via SSH proxying. Again, all > of this setup worked fine before beta3. > > Also, the force-to-upper-left behavior is affecting some but not all > of the windows displayed by a Tcl application I use heavily. Dunno > what to make of that. > > regards, tom lane > > > xwininfo: Window id: 0xc00013 "emacs(a)sss2.sss.pgh.pa.us" > > Root window id: 0x1fd (the root window) (has no name) > Parent window id: 0x600047 (has no name) > 1 child: > 0xc00014 (has no name): () 496x797+0+0 +0+22 > 1 child: > 0xc00015 (has no name): () 496x797+0+0 +0+22 > 6 children: > 0xc00040 (has no name): () 12x13+482+782 +482+804 > 0xc00041 (has no name): () 12x13+482+782 +482+804 > 0xc0003e (has no name): () 12x377+482+392 +482+414 > 0xc0003f (has no name): () 12x377+482+392 +482+414 > 0xc0003c (has no name): () 12x377+482+2 +482+24 > 0xc0003d (has no name): () 12x377+482+2 +482+24 > > Absolute upper-left X: 0 > Absolute upper-left Y: 22 > Relative upper-left X: 0 > Relative upper-left Y: 22 > Width: 496 > Height: 797 > Depth: 24 > Visual Class: TrueColor > Border width: 0 > Class: InputOutput > Colormap: 0x21 (installed) > Bit Gravity State: NorthWestGravity > Window Gravity State: NorthWestGravity > Backing Store State: NotUseful > Save Under State: no > Map State: IsViewable > Override Redirect State: no > Corners: +0+22 -944+22 -944-59 +0-59 > -geometry 80x61+0+0 > > Bit gravity: NorthWestGravity > Window gravity: NorthWestGravity > Backing-store hint: NotUseful > Backing-planes to be preserved: 0xffffffff > Backing pixel: 0 > Save-unders: No > > Someone wants these events: > KeyPress > ButtonPress > ButtonRelease > EnterWindow > LeaveWindow > PointerMotion > Exposure > VisibilityChange > StructureNotify > FocusChange > PropertyChange > ColormapChange > Do not propagate these events: > Override redirection?: No > > Window manager hints: > Client accepts input or input focus: Yes > Initial state is Normal State > > Normal window size hints: > User supplied location: 940, 0 > Program supplied size: 496 by 797 > Program supplied minimum size: 16 by 4 > Program supplied base size: 16 by 4 > Program supplied x resize increment: 6 > Program supplied y resize increment: 13 > Program supplied size in resize increments: 82 by 61 > Program supplied minimum size in resize increments: 2 by 0 > Program supplied base size in resize increments: 2 by 0 > Program supplied window gravity: NorthEastGravity > No zoom window size hints defined > > No window shape defined > No border shape defined >

2 5

Re: [Xquartz-dev] geometry regression in 2.3.2-beta3
by Jeremy Huddleston 12 Nov '08

12 Nov '08

What does 'xwininfo -all' say about this window? On Nov 11, 2008, at 19:20, Tom Lane wrote: > For many years I've launched emacs at the right side of my screen by > setting this via xrdb: > > emacs*geometry: 80x61-0+0 > > It worked fine with xquartz up till now (through beta2), but in beta3 > what I see is the window flashing up at the right side and immediately > bouncing over to the left somewhere. I suspect this has something > to do > with the fullscreen hacks in beta3 ... but I'm not using fullscreen > mode. Help!? > > regards, tom lane

1 0

Re: [Xquartz-dev] 2.3.2_beta3
by Dave Ray 12 Nov '08

12 Nov '08

Overall the new release has many bug fixes and improvements - Thanks Jeremy! Some feedback: Mine also crashes when the system alert bell supposed to go off, like hitting the delete key at the terminal prompt. Preferences option for the Apple menubar appearing in fullscreen mode is a nice feature. The delay is just enough to let me grab the workspace grab-bars if I want. It would be nice to add the command-tab functionality while the menubar is activated, so I don't have to use option-cmd-A. I am still seeing occasional drawing errors from short-lived GUI components, such as part of a drop menu or tooltip. It seems that every once in a while a menu or popup would be drawn briefly, went away, and would leave a white silhouette instead of being filled by the background or next layer behind. Dave

2 1

Re: [Xquartz-dev] 2.3.2_beta3
by Jeremy Huddleston 12 Nov '08

12 Nov '08

Yep, I can reproduce it. Workaround: enable "Use system alert effect" in the X11 Preferences- >Output panel. Would you mind filing a bug report at http://xquartz.macosforge.org on this please? Thanks, Jeremy On Nov 11, 2008, at 16:28, Emanuele Giaquinta wrote: > Hi, > > On Tue, Nov 11, 2008 at 10:51:44AM -0800, Jeremy Huddleston wrote: > >> Please let me know if there are any major show-stopping issues. I >> expect that this will be fairly close to what becomes rc1 (the main >> difference being that I intend to make xpbproxy be a server thread >> for >> the release-candidate rather than a separate process). > > I can consistently reproduce a crash of the server (bus error). > Attached > are the system.log excerpt and the .crash file. The crash does not > happen with X11-1.4.2-apple21. > > Emanuele Giaquinta > <X11_2008-11-12-011946_orion.crash><system.log>

1 0

2.3.2_beta3 jumps back to X-11 screen on mac side close
by William Davis 11 Nov '08

11 Nov '08

easy to reproduce: 1. In terminal do gedit & 2. switch to full X-11 screen opt-cmd-a 3. do whatever then switch back to mac screen with opt-cmd-a 4. open calculator 5. close calculator 6. ZAP -- you are back on the X-11 full grey screen William Davis frstanATbellsouthDOTnet Mac OS X.5.5 Darwin 9.5.0 XQuartz 2.3.2 (xorg-server 1.4.2-apple21) Mac Mini Intel Duo @ 1.86 GHz Mundus vult decepi, ego non

2 1

2.3.2_beta3
by Jeremy Huddleston 11 Nov '08

11 Nov '08

#1) Yes, the spin from beta2 is fixed. http://static.macosforge.org/xquartz/downloads/X11-2.3.2_beta3.pkg The main changes from beta 2 are: Many GLX updates... support for multisampling is now present, better listing of supported visuals pbproxy updates... PICT support, workaround nedit/eterm bugs The menu bar is no longer mapped to the X11 screen (so other WMs won't "hide under" the menu bar) Fixed some threading related issues in mieq (possible crash with a full event queue fixed) quartz-wm now supports window gravity libXplugin is now more thread safe (the "spin" bug from beta2) X11.app should now exit if you are using a WM other than quartz-wm and you exit the WM Added an option to show the menu bar when your mouse approaches it in fullscreen mode. Please let me know if there are any major show-stopping issues. I expect that this will be fairly close to what becomes rc1 (the main difference being that I intend to make xpbproxy be a server thread for the release-candidate rather than a separate process). --Jeremy

5 8