#29642 closed defect (invalid)
Gramps crashes X11.app in RootlessGlyphs on 10.5
| Reported by: | guy.linton@… | Owned by: | dbevans (David B. Evans) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.2 |
| Keywords: | leopard | Cc: | olivier.aubert@… |
| Port: | gramps |
Description
Upgraded all Macports, and now Gramps crashes X11. X11 starts, two empty windows are displayed from Gramps and then presumably when drawing within the windows X11 crashes. The same Gramps code ran with previous ports (from about a year ago), so the problem seems to be in the libraries.
Mac OS X 10.5.8 PPC G5.
Any idea how I can determine what the call is to X11 that is causing the problem?
Attachments (2)
Change History (12)
Changed 13 years ago by guy.linton@…
| Attachment: | crashlog.txt added |
|---|
Changed 13 years ago by guy.linton@…
| Attachment: | portinstalledlist.txt added |
|---|
List of versions of ports currently installed
comment:2 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | guy.linton@… removed |
|---|---|
| Owner: | changed from macports-tickets@… to devans@… |
| Port: | gramps added; Gramps removed |
comment:3 Changed 13 years ago by guy.linton@…
I have tried this with python25, 26 and 27 with exactly the same result.
I came across this recent patch to X11: http://xquartz.macosforge.org/trac/wiki/X112.6.2 could this be related? I note that this is really for xquartz, and also I am on Mac OS X 10.5.8, not 10.6. My about X11 says: XQuartz 2.1.6 (xorg-server 1.4.2-apple33). Also, it is strange that it used to work with earlier versions of the various Macports installed libraries.
comment:4 Changed 13 years ago by jeremyhu (Jeremy Huddleston Sequoia)
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
This is not the MacPorts provided server. Please use the xorg-server port for a newer X11.app (/Applications/MacPorts/X11.app)
comment:6 follow-up: 10 Changed 13 years ago by olivier.aubert@…
| Resolution: | invalid |
|---|---|
| Status: | closed → reopened |
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 ?
comment:7 Changed 12 years ago by jmroot (Joshua Root)
| Keywords: | leopard added |
|---|---|
| Summary: | Gramps crash in X11 RootlessGlyphs → Gramps crashes X11.app in RootlessGlyphs on 10.5 |
Is this still a problem with current versions? If so, I guess gramps (or whatever dependency makes most sense) should at least depend on xorg-server on Leopard.
comment:8 Changed 12 years ago by guy.linton@…
I have not lost interest in this bug, just unable to carry out a new test at the moment.
comment:9 Changed 12 years ago by jeremyhu (Jeremy Huddleston Sequoia)
| Resolution: | → invalid |
|---|---|
| Status: | reopened → closed |
That is probably the bug mentioned in the release notes for XQuartz 2.6.2: http://xquartz.macosforge.org/trac/wiki/X112.6.2
Please install XQuartz 2.6.3 on Leopard or use the X11 server from MacPorts.
comment:10 Changed 12 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Replying to 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.
X11 crashlog