Comments on: X11 on Leopard is broken

By: Neal

Neal — Sun, 15 Jun 2008 17:09:24 +0000

I got around the broken cut/paste problem by installing ETerm (using port), option-click in ETerm pastes the highlighted text.

By: Jason Weathered

Jason Weathered — Mon, 02 Jun 2008 20:48:53 +0000

Hmm, it seems if one forgets to answer the anti-spam question, a not so pleasant dose of addslashes() is applied to the comment text.

Oh isn't PHP fun? :)

By: Jason Weathered

Jason Weathered — Mon, 02 Jun 2008 20:44:41 +0000

mk: I think you\'re after Xnest. Something like the following should do the trick:

Xnest -geometry 1024x768 :1& DISPLAY=:1 ssh -X host gnome-session

By: mk

mk — Mon, 02 Jun 2008 14:31:18 +0000

I do like the feature that you can simply run ssh -X user@host gnome-session in a normal terminal to get things started, but Leopard has rendered X11 useless. It resizes to a fill my entire screen, except that my gnome top and bottom menus are covered by the Mac's bar, so I can't click anything. Firefox seems to run ok in a window...

Anyone know how to force X11/Xorg to run at say 1024x768 instead of trying (in my case) to make the resolution 1920x1200???

By: Orv

Orv — Thu, 27 Dec 2007 00:40:47 +0000

When I run KDE apps in Leopard -- either locally, or via X forwarding -- scrolling doesn't work properly. Instead of the new window contents replacing the old, they overwrite the old ones, making an illegible mess. Does anyone know of a workaround?

By: Peter Hosey

Peter Hosey — Thu, 06 Dec 2007 05:38:37 +0000

Kevin Turpie: I haven't noticed any scroll-bar problems, but you're right that it may be .Xdefault-related.

Anyway, I suggest that you check out the follow-up post that I linked up top, and consider whether it's worth it to you to try one of the alpha versions that have come out since Leopard.

By: Kevin Turpie

Kevin Turpie — Thu, 06 Dec 2007 05:19:32 +0000

I use a lot of X11 apps and I've had all the problems mentioned in the post. This is frustrating. I am used to doing a lot of cutting and pasting with my laptop (between editor and command line) and this just doesn't work anymore. In addition to the various foibles mentioned, I've noticed that the scroll bar and other features I'm accustomed to seeing in xterm are missing. It's probably the side stepping of .Xdefaults, but I don't know.

By: Stu

Stu — Fri, 16 Nov 2007 18:01:46 +0000

The latest update, 10.5.1, has totally broken X11 for me. I even tried xterm.app, but either way, it just tries to open and dies.

It either appears twice on the dock, and then disappears, or it appears, shows an xterm window, without a frame around it, and when you click on the window, it dies.

Anyone else have this problem after updating Leopard?

By: Richard French

Richard French — Wed, 07 Nov 2007 03:06:31 +0000

I just installed Leopard X11 on my G5, and when I try to enlarge an xterm window by dragging the lower right corner, it kills X11 completely. Has anyone else run into this problem? Suggestions? Would doing a clean install rather than an upgrade from Tiger make any difference?

By: Bert JW Regeer

Bert JW Regeer — Mon, 05 Nov 2007 04:29:29 +0000

A new version of quartz-wm has been posted by an Apple employee at http://www.x.org/wiki/XDarwin follow the installation instructions, and Wireshark will work again as expected. It also fixes the bug of being able to drag a Window to a second screen.

There are still some issues with Focus, but it has to do with the way Mac OS X handles Spaces.

By: Rick Robino

Rick Robino — Sat, 03 Nov 2007 20:30:04 +0000

Again, thanks for the tip. Saved me from having to fork up for Etherpeek, if they even have a Leopard version. Anyway...

Regarding wireshark: in addition to the suggestion to set the colors to thousands (and restart X11 apparently), you may also need to keep unset DYLD_LIBRARY_PATH [so that Apple's default lib path will be followed] and set DYLD_FALLBACK_LIBRARY_PATH [so that your own library path will be followed]. This works around a behavior that exhibits itself as:

dyld: Symbol not found: __cg_jpeg_resync_to_restart
Referenced from: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Versions/A/ImageIO
Expected in: /opt/local/lib/libjpeg.62.dylib

Another tip: install portaudio before configure runs when building wireshark. wireshark will pick it up and give you the (G711) player even though it might not be an option in automated build systems that handle dependencies like macports.

By: Jason Weathered

Jason Weathered — Fri, 02 Nov 2007 02:01:14 +0000

Adam Durana at 2007-11-01 17:57 UTC wrote:
> set the 'Colors' option to 'Thousands' in X11.app.

Thanks for posting this workaround. Another item off my Leopard teething list.

By: Peter Hosey

Peter Hosey — Thu, 01 Nov 2007 18:53:43 +0000

Dave Schroeder: I'd seen some of it; I put a couple links to messages in that thread in the post.

However, I wasn't aware that, in your words, many problems are fixed already. That's good news, so thanks for the follow-up.

By: Dave Schroeder

Dave Schroeder — Thu, 01 Nov 2007 18:22:41 +0000

There is a LOT of discussion about this on Apple's X11-users list...I'd recommend joining. Many, many problems have already been resolved in unofficial builds released by Apple's X11 maintainer (who is also an XDarwin maintainer). The X11 maintainer at Apple is actively responding to problems and requests:

http://lists.apple.com/mailman/listinfo/x11-users

By: Adam Durana

Adam Durana — Thu, 01 Nov 2007 17:57:58 +0000

I too ran into the Wireshark bug. There\'s a Wireshark bug logged in their database of bugs, but a work around that appears to work is to set the \'Colors\' option to \'Thousands\' in X11.app.