Experiences with 2.3.2_rc1
I usually use my Mac in fullscreen X mode, and had delayed switching to Leopard because it didn't work. Seeing that it's now available, I have made the switch and installed 2.3.2_rc1. I'm using fvwm2 as my window manager. Here are some problems I've encountered. Some of the things I mention below should probably be submitted as bugs, but as I haven't been through the bug list carefully yet I thought I'd raise them here first. (1) White rectangles. I see there is already a bug report for these, but I'll describe what I get anyway. There appears to be a white rectangle for each pop-up window, mostly menus. They don't appear immediately after popping up the menu, but after switching to the main Mac display (alt-apple-a) and back to the fullscreen X display. They don't obscure X windows, just the background. But if I switch to the Mac display again, they are there too and *do* obscure other windows. Popping up the same menu again makes them go away until I switch to the Mac display again. (2) Sometimes on starting up X in fullscreen mode the menu bar appears at the top - and in one case something appeared at the bottom - and goes away when I move the mouse over it (or perhaps when I click - it hasn't happened often enough to be sure). I don't have "auto-show menu bar" selected. (3) On one occasion, on starting up X I got the X background with a beachball cursor. The only way I found to get out of it was to log in from another machine and kill X11.app. alt-apple-a did not work. (4) On one occasion after switching to the X display the cursor was stuck in the top-left corner. Switching to the Mac display and back fixed it. (5) My xterms (started with "xterm -ls" from fvwm) have / as their current directory. I guess this is because that's the window manager's current directory. (It occurs to me I can probably fix that by putting cd $HOME in my .xinitrc, but I haven't tried it yet.) (6) The window manager and initial xterm appear to have their DISPLAY variable set to /tmp/launchd-xxx/:0, but xterms started later from fvwm get :1.0. Why is there this difference, and why is it :1.0 instead of :0.0? (This is inconvenient because I have code that assumes - perhaps wrongly - that if DISPLAY is something:n, then hostname:n will work from another machine.) Despite these problems I'm pleased to have fullscreen working on Leopard, and I'd like to thank all those who have worked on it. -- Richard -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.
Thanks Richard. On Nov 26, 2008, at 07:27, Richard Tobin wrote:
(1) White rectangles.
Known issue... and will most likely not be fixed in 2.3.2
(2) Sometimes on starting up X in fullscreen mode the menu bar appears at the top - and in one case something appeared at the bottom - and goes away when I move the mouse over it (or perhaps when I click - it hasn't happened often enough to be sure). I don't have "auto-show menu bar" selected.
Yeah, I think there's something off with the initial window placement. It doesn't "trigger" fullscreen when it should. I'll take a look at that, but again, it's not on the hitlist for 2.3.2 right now.
(3) On one occasion, on starting up X I got the X background with a beachball cursor. The only way I found to get out of it was to log in from another machine and kill X11.app. alt-apple-a did not work.
I'd really like to see a crash log of this if you have it... otherwise there's nothing I can do since this is the first report I've heard of it.
(4) On one occasion after switching to the X display the cursor was stuck in the top-left corner. Switching to the Mac display and back fixed it.
Again, this is a known issue, that I've seen once, can't reproduce, and have no clue what might be causing it.
(5) My xterms (started with "xterm -ls" from fvwm) have / as their current directory. I guess this is because that's the window manager's current directory. (It occurs to me I can probably fix that by putting cd $HOME in my .xinitrc, but I haven't tried it yet.)
X11.app starts with / as the current directory... maybe I can put a chdir to the user home dir before in there... but yeah, your workaround should work too. PS I advise you to not have a ~/.xinitrc... Starting with 2.3.2_rc2, you'll be able to drop scripts into ~/.xinitrc.d that will get executed by the system xinitrc right before it would launchd the WM. That way you can take advantage of changes to the system xinitrc.
(6) The window manager and initial xterm appear to have their DISPLAY variable set to /tmp/launchd-xxx/:0, but xterms started later from fvwm get :1.0. Why is there this difference, and why is it :1.0 instead of :0.0?
X11.app's environment has the launchd display socket as DISPLAY. twm was started by xinit and thus has the unix socket as DISPLAY. It's :1 becuse there is a lock file on :0 (probably from when your X server crashed and it won't be removed until you reboot or remove it from /tmp manually)
(This is inconvenient because I have code that assumes - perhaps wrongly - that if DISPLAY is something:n, then hostname:n will work from another machine.)
Yeah, that's bad. If you 'ssh -Y' to another machine (and that other machine allows X11 forwarding in ssh), it should "just work"
Despite these problems I'm pleased to have fullscreen working on Leopard, and I'd like to thank all those who have worked on it.
You're welcome. I'm glad that it's useful in its current form... hopefully these issues can be squashed soon. Please open bug reports for the ones that aren't already open. Thanks, Jeremy
participants (2)
-
Jeremy Huddleston
-
Richard Tobin