[MacPorts] #29642: Gramps crashes X11.app in RootlessGlyphs on 10.5

[MacPorts]

#29642: Gramps crashes X11.app in RootlessGlyphs on 10.5
-----------------------------------+----------------------------------------
  Reporter:  guy.linton@…          |       Owner:  devans@…           
      Type:  defect                |      Status:  closed             
  Priority:  Normal                |   Milestone:                     
 Component:  ports                 |     Version:  1.9.2              
Resolution:  invalid               |    Keywords:  leopard            
      Port:  gramps                |  
-----------------------------------+----------------------------------------

Comment(by jeremyhu@…):

 Replying to [comment:6 olivier.aubert@…]:
 > I am facing the same issue with my app (http://www.advene.org/). And
 other apps suffer from the same crashes (Wireshark for instance:
 http://ask.wireshark.org/questions/6388/wireshark-crashes-on-osx-105-on-
 startup-from-macports ).
 >
 > It is perfectly true that:
 >
 > 1- the problem liens in the X11.app itself, since it should not crash,
 regardless of what data the client sends to it.
 >
 > 2- the macports server works correctly, and it is not the job of the
 macports project to handle Apple bugs.

 Changes in GTK exposed this latent bug, and I put out an additional
 XQuartz release for Leopard *just* for this bugfix.  Leopard is well past
 EOL and not getting updates from Apple SU.

  > However, when distributing software, it is a chore to have to
 distribute yet another component, the X11 server, which has then to be
 explicitly launched - OK, xorg-server can be setup to launch
 automatically, but it is still more work. Instead of telling users
 "Download the .dmg image, and install the app", longer (and more complex)
 instructions have to be given.

 Then just put it as a requirement.  You can even put in a check for the
 server version and tell users to get 2.6.3 if they're on 2.1.6.

 > Would it then be possible to reopen this bug, and reassign it to gtk2 ?

 No, it's an xorg-server bug that was fixed over a year ago.

 http://cgit.freedesktop.org/~jeremyhu/xserver/commit/?h=XQuartz-2.6.2&id=1939043a34c47d2cff63aac3909f31f08aa6ab84

-- 
Ticket URL: <https://trac.macports.org/ticket/29642#comment:10>
MacPorts <http://www.macports.org/>
Ports system for Mac OS