[MacPorts] #29642: Gramps crash in X11 RootlessGlyphs

[MacPorts]

#29642: Gramps crash in X11 RootlessGlyphs
-----------------------------------+----------------------------------------
  Reporter:  guy.linton@…          |       Owner:  devans@…           
      Type:  defect                |      Status:  reopened           
  Priority:  Normal                |   Milestone:                     
 Component:  ports                 |     Version:  1.9.2              
Resolution:                        |    Keywords:                     
      Port:  gramps                |  
-----------------------------------+----------------------------------------
Changes (by olivier.aubert@…):

  * status:  closed => reopened
  * resolution:  invalid =>


Comment:

 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.

 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.

 Since the error was not triggered before, it would be interesting to be
 able to know what change in the underlying libs introduced the crash. I
 looked at the git logs for gtk2, but found nothing evident. Then we could
 simply patch the lib bundled with the application, and users would not
 have to care about the bug.

 Yes, it is putting your dirt under the carpet. But, as the python motto
 says, "practicality beats purity". I am willing to have a look at it, but
 do not quite know where/what to look, and some starting points would be
 helpful.

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

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