From: John <jh...@ea...> - 2009-06-09 17:16:00
|
I recently installed the latest (as of a week or two ago) MacPorts version of gramps. I eventually found how to get it to fire up, and the few things I've tried so far seem to work. Except, every time I click on Export, it crashes and firing up again I need to clear the lock. The terminal window says simply: bus error The system log file says: macintosh-2 ReportCrash[27020]: Formulating crash report for process Python[26856] macintosh-2 ReportCrash[27020]: Saved crashreport to .../Library/Logs/CrashReporter/Python_2009-06-09-130347_Macintosh-2.crash using uid: 501 gid: 501, euid: 501 egid: 501 And the Python crashreport begins (too long to post completely?): Process: Python [26856] Path: /opt/local/Library/Frameworks/Python.framework/Versions/2.5/Resources/Python.app/Contents/MacOS/Python Identifier: Python Version: ??? (???) Code Type: X86 (Native) Parent Process: bash [26781] Date/Time: 2009-06-09 13:03:47.160 -0400 OS Version: Mac OS X 10.5.7 (9J61) Report Version: 6 Anonymous UUID: 8F7EB637-5CD5-4162-9800-DC228C380BAD Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000081 Crashed Thread: 0 Thread 0 Crashed: 0 org.python.python 0x001f53e4 PyType_IsSubtype + 148 1 _gobject.so 0x007241e9 pyg_type_add_interfaces + 233 2 _gobject.so 0x00724481 pyg_type_register + 497 3 _gobject.so 0x007252ba _wrap_pyg_type_register + 202 4 org.python.python 0x00239750 PyEval_EvalFrameEx + 24144 5 org.python.python 0x00239c2e PyEval_EvalFrameEx + 25390 6 org.python.python 0x0023b5ca PyEval_EvalCodeEx + 1962 7 org.python.python 0x001c845d function_call + 221 8 org.python.python 0x001a3bb2 PyObject_Call + 50 9 org.python.python 0x001ac966 instancemethod_call + 422 10 org.python.python 0x001a3bb2 PyObject_Call + 50 11 org.python.python 0x001f8337 slot_tp_init + 87 12 org.python.python 0x001fa9e0 type_call + 176 13 org.python.python 0x001a46a7 PyObject_CallFunctionObjArgs + 151 14 org.python.python 0x002347e1 PyEval_EvalFrameEx + 3809 15 org.python.python 0x0023b5ca PyEval_EvalCodeEx + 1962 16 org.python.python 0x0023b6d7 PyEval_EvalCode + 87 17 org.python.python 0x00252fcc PyImport_ExecCodeModuleEx + 188 18 org.python.python 0x00253453 load_source_module + 739 ... Can anyone shed some light on what I need to do to get export to work? Again, this the the MacPorts version. I had to install tons of prerequisites via MacPorts to get this far, never having needed any MacPorts software before. If the full crash dump is needed, and it is okay to post it, I can do that. Or if there is a piece of it not shown that is more relevant, I can post or look at just that. Thanks! |
From: Gerald B. <ger...@gm...> - 2009-06-09 17:24:17
|
Looking at the exception codes I would guess that this is a bug in the Python port used on the Mac. Since gramps is written in Python, it cannot, by itself, cause a bus error, which usually means trying to access memory that is not yours, IIRC. Probably you should handle this though Apple support channels. On Tue, Jun 9, 2009 at 1:15 PM, John<jh...@ea...> wrote: > I recently installed the latest (as of a week or two ago) > MacPorts version of gramps. I eventually found how to get > it to fire up, and the few things I've tried so far seem > to work. Except, every time I click on Export, it crashes > and firing up again I need to clear the lock. > > The terminal window says simply: > bus error > > The system log file says: > > macintosh-2 ReportCrash[27020]: Formulating crash report for process > Python[26856] > macintosh-2 ReportCrash[27020]: Saved crashreport to > .../Library/Logs/CrashReporter/Python_2009-06-09-130347_Macintosh-2.crash > using uid: 501 gid: 501, euid: 501 egid: 501 > > And the Python crashreport begins (too long to post completely?): > > Process: Python [26856] > Path: > /opt/local/Library/Frameworks/Python.framework/Versions/2.5/Resources/Python.app/Contents/MacOS/Python > Identifier: Python > Version: ??? (???) > Code Type: X86 (Native) > Parent Process: bash [26781] > > Date/Time: 2009-06-09 13:03:47.160 -0400 > OS Version: Mac OS X 10.5.7 (9J61) > Report Version: 6 > Anonymous UUID: 8F7EB637-5CD5-4162-9800-DC228C380BAD > > Exception Type: EXC_BAD_ACCESS (SIGBUS) > Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000081 > Crashed Thread: 0 > > Thread 0 Crashed: > 0 org.python.python 0x001f53e4 PyType_IsSubtype + 148 > 1 _gobject.so 0x007241e9 > pyg_type_add_interfaces + 233 > 2 _gobject.so 0x00724481 pyg_type_register + 497 > 3 _gobject.so 0x007252ba > _wrap_pyg_type_register + 202 > 4 org.python.python 0x00239750 PyEval_EvalFrameEx + > 24144 > 5 org.python.python 0x00239c2e PyEval_EvalFrameEx + > 25390 > 6 org.python.python 0x0023b5ca PyEval_EvalCodeEx + 1962 > 7 org.python.python 0x001c845d function_call + 221 > 8 org.python.python 0x001a3bb2 PyObject_Call + 50 > 9 org.python.python 0x001ac966 instancemethod_call + 422 > 10 org.python.python 0x001a3bb2 PyObject_Call + 50 > 11 org.python.python 0x001f8337 slot_tp_init + 87 > 12 org.python.python 0x001fa9e0 type_call + 176 > 13 org.python.python 0x001a46a7 > PyObject_CallFunctionObjArgs + 151 > 14 org.python.python 0x002347e1 PyEval_EvalFrameEx + 3809 > 15 org.python.python 0x0023b5ca PyEval_EvalCodeEx + 1962 > 16 org.python.python 0x0023b6d7 PyEval_EvalCode + 87 > 17 org.python.python 0x00252fcc > PyImport_ExecCodeModuleEx + 188 > 18 org.python.python 0x00253453 load_source_module + 739 > ... > > Can anyone shed some light on what I need to do to get export to work? > Again, this the the MacPorts version. I had to install tons of > prerequisites via MacPorts to get this far, never having needed any > MacPorts software before. > > If the full crash dump is needed, and it is okay to post it, I can > do that. Or if there is a piece of it not shown that is more relevant, > I can post or look at just that. > > Thanks! > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > -- Gerald Britton |
From: Benny M. <ben...@gm...> - 2009-06-09 17:51:55
|
Yes, see if you can install newer python, or start gramps with an older one. Everything > 2.5.0 should work. Eg: python2.6 gramps.py or python2.5 gramps.py .. Benny 2009/6/9 Gerald Britton <ger...@gm...>: > Looking at the exception codes I would guess that this is a bug in the > Python port used on the Mac. Since gramps is written in Python, it > cannot, by itself, cause a bus error, which usually means trying to > access memory that is not yours, IIRC. > > Probably you should handle this though Apple support channels. > > On Tue, Jun 9, 2009 at 1:15 PM, John<jh...@ea...> wrote: >> I recently installed the latest (as of a week or two ago) >> MacPorts version of gramps. I eventually found how to get >> it to fire up, and the few things I've tried so far seem >> to work. Except, every time I click on Export, it crashes >> and firing up again I need to clear the lock. >> >> The terminal window says simply: >> bus error >> >> The system log file says: >> >> macintosh-2 ReportCrash[27020]: Formulating crash report for process >> Python[26856] >> macintosh-2 ReportCrash[27020]: Saved crashreport to >> .../Library/Logs/CrashReporter/Python_2009-06-09-130347_Macintosh-2.crash >> using uid: 501 gid: 501, euid: 501 egid: 501 >> >> And the Python crashreport begins (too long to post completely?): >> >> Process: Python [26856] >> Path: >> /opt/local/Library/Frameworks/Python.framework/Versions/2.5/Resources/Python.app/Contents/MacOS/Python >> Identifier: Python >> Version: ??? (???) >> Code Type: X86 (Native) >> Parent Process: bash [26781] >> >> Date/Time: 2009-06-09 13:03:47.160 -0400 >> OS Version: Mac OS X 10.5.7 (9J61) >> Report Version: 6 >> Anonymous UUID: 8F7EB637-5CD5-4162-9800-DC228C380BAD >> >> Exception Type: EXC_BAD_ACCESS (SIGBUS) >> Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000081 >> Crashed Thread: 0 >> >> Thread 0 Crashed: >> 0 org.python.python 0x001f53e4 PyType_IsSubtype + 148 >> 1 _gobject.so 0x007241e9 >> pyg_type_add_interfaces + 233 >> 2 _gobject.so 0x00724481 pyg_type_register + 497 >> 3 _gobject.so 0x007252ba >> _wrap_pyg_type_register + 202 >> 4 org.python.python 0x00239750 PyEval_EvalFrameEx + >> 24144 >> 5 org.python.python 0x00239c2e PyEval_EvalFrameEx + >> 25390 >> 6 org.python.python 0x0023b5ca PyEval_EvalCodeEx + 1962 >> 7 org.python.python 0x001c845d function_call + 221 >> 8 org.python.python 0x001a3bb2 PyObject_Call + 50 >> 9 org.python.python 0x001ac966 instancemethod_call + 422 >> 10 org.python.python 0x001a3bb2 PyObject_Call + 50 >> 11 org.python.python 0x001f8337 slot_tp_init + 87 >> 12 org.python.python 0x001fa9e0 type_call + 176 >> 13 org.python.python 0x001a46a7 >> PyObject_CallFunctionObjArgs + 151 >> 14 org.python.python 0x002347e1 PyEval_EvalFrameEx + 3809 >> 15 org.python.python 0x0023b5ca PyEval_EvalCodeEx + 1962 >> 16 org.python.python 0x0023b6d7 PyEval_EvalCode + 87 >> 17 org.python.python 0x00252fcc >> PyImport_ExecCodeModuleEx + 188 >> 18 org.python.python 0x00253453 load_source_module + 739 >> ... >> >> Can anyone shed some light on what I need to do to get export to work? >> Again, this the the MacPorts version. I had to install tons of >> prerequisites via MacPorts to get this far, never having needed any >> MacPorts software before. >> >> If the full crash dump is needed, and it is okay to post it, I can >> do that. Or if there is a piece of it not shown that is more relevant, >> I can post or look at just that. >> >> Thanks! >> >> ------------------------------------------------------------------------------ >> Crystal Reports - New Free Runtime and 30 Day Trial >> Check out the new simplified licensing option that enables unlimited >> royalty-free distribution of the report engine for externally facing >> server and web deployment. >> http://p.sf.net/sfu/businessobjects >> _______________________________________________ >> Gramps-users mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-users >> > > > > -- > Gerald Britton > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > |
From: Emrys W. <emr...@ev...> - 2009-06-09 18:08:19
|
Yes, this has just started happening to me, too. I see the python on my imac is now Python 2.5.4 (r254:67916, May 20 2009, 17:05:46) [GCC 4.0.1 (Apple Inc. build 5490)] and I think that export worked properly up until sometime around that time. I think that the automated updates to the X11 quartz application, and now to python, cause unexpected stuff to happen to gramps. I posted a note at http://www.gramps-project.org/wiki/index.php?title=Mac_OS_X_MacPorts about my latest experiences with X11 updating itself without me realising. It certainly is somewhat unnerving to have a buggy system where the backup program is the one which causes the crash! We do need to work on a better scheme for Mac installation. Let's think about it. Emrys Williams Gerald Britton wrote: > Looking at the exception codes I would guess that this is a bug in the > Python port used on the Mac. Since gramps is written in Python, it > cannot, by itself, cause a bus error, which usually means trying to > access memory that is not yours, IIRC. > > Probably you should handle this though Apple support channels. > > On Tue, Jun 9, 2009 at 1:15 PM, John<jh...@ea...> wrote: > >> I recently installed the latest (as of a week or two ago) >> MacPorts version of gramps. I eventually found how to get >> it to fire up, and the few things I've tried so far seem >> to work. Except, every time I click on Export, it crashes >> and firing up again I need to clear the lock. >> >> The terminal window says simply: >> bus error >> >> The system log file says: >> >> macintosh-2 ReportCrash[27020]: Formulating crash report for process >> Python[26856] >> macintosh-2 ReportCrash[27020]: Saved crashreport to >> .../Library/Logs/CrashReporter/Python_2009-06-09-130347_Macintosh-2.crash >> using uid: 501 gid: 501, euid: 501 egid: 501 >> >> And the Python crashreport begins (too long to post completely?): >> >> Process: Python [26856] >> Path: >> /opt/local/Library/Frameworks/Python.framework/Versions/2.5/Resources/Python.app/Contents/MacOS/Python >> Identifier: Python >> Version: ??? (???) >> Code Type: X86 (Native) >> Parent Process: bash [26781] >> >> Date/Time: 2009-06-09 13:03:47.160 -0400 >> OS Version: Mac OS X 10.5.7 (9J61) >> Report Version: 6 >> Anonymous UUID: 8F7EB637-5CD5-4162-9800-DC228C380BAD >> >> Exception Type: EXC_BAD_ACCESS (SIGBUS) >> Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000081 >> Crashed Thread: 0 >> >> Thread 0 Crashed: >> 0 org.python.python 0x001f53e4 PyType_IsSubtype + 148 >> 1 _gobject.so 0x007241e9 >> pyg_type_add_interfaces + 233 >> 2 _gobject.so 0x00724481 pyg_type_register + 497 >> 3 _gobject.so 0x007252ba >> _wrap_pyg_type_register + 202 >> 4 org.python.python 0x00239750 PyEval_EvalFrameEx + >> 24144 >> 5 org.python.python 0x00239c2e PyEval_EvalFrameEx + >> 25390 >> 6 org.python.python 0x0023b5ca PyEval_EvalCodeEx + 1962 >> 7 org.python.python 0x001c845d function_call + 221 >> 8 org.python.python 0x001a3bb2 PyObject_Call + 50 >> 9 org.python.python 0x001ac966 instancemethod_call + 422 >> 10 org.python.python 0x001a3bb2 PyObject_Call + 50 >> 11 org.python.python 0x001f8337 slot_tp_init + 87 >> 12 org.python.python 0x001fa9e0 type_call + 176 >> 13 org.python.python 0x001a46a7 >> PyObject_CallFunctionObjArgs + 151 >> 14 org.python.python 0x002347e1 PyEval_EvalFrameEx + 3809 >> 15 org.python.python 0x0023b5ca PyEval_EvalCodeEx + 1962 >> 16 org.python.python 0x0023b6d7 PyEval_EvalCode + 87 >> 17 org.python.python 0x00252fcc >> PyImport_ExecCodeModuleEx + 188 >> 18 org.python.python 0x00253453 load_source_module + 739 >> ... >> >> Can anyone shed some light on what I need to do to get export to work? >> Again, this the the MacPorts version. I had to install tons of >> prerequisites via MacPorts to get this far, never having needed any >> MacPorts software before. >> >> If the full crash dump is needed, and it is okay to post it, I can >> do that. Or if there is a piece of it not shown that is more relevant, >> I can post or look at just that. >> >> Thanks! >> >> ------------------------------------------------------------------------------ >> Crystal Reports - New Free Runtime and 30 Day Trial >> Check out the new simplified licensing option that enables unlimited >> royalty-free distribution of the report engine for externally facing >> server and web deployment. >> http://p.sf.net/sfu/businessobjects >> _______________________________________________ >> Gramps-users mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-users >> >> > > > > |
From: Gerald B. <ger...@gm...> - 2009-06-09 18:20:57
|
Dear Emrys, If I understand correctly, the problem you and John are experiencing is not gramps-specific. It appears to be that a recent update to Python on your systems introduced this error. Since gramps is written in Python, it is literally incapable of causing this sort of error. Please have a look at the Apple support forums to see if there are any others reporting errors like these in other applications. Also, it would probably be helpful to take a look at the changelog if it is available to you. On Tue, Jun 9, 2009 at 1:47 PM, Emrys Williams<emr...@ev...> wrote: > Yes, this has just started happening to me, too. I see the python on my > imac is now > Python 2.5.4 (r254:67916, May 20 2009, 17:05:46) > [GCC 4.0.1 (Apple Inc. build 5490)] > and I think that export worked properly up until sometime around that time. > > I think that the automated updates to the X11 quartz application, and > now to python, cause unexpected stuff to happen to gramps. I posted a > note at > http://www.gramps-project.org/wiki/index.php?title=Mac_OS_X_MacPorts > about my latest experiences with X11 updating itself without me realising. > > It certainly is somewhat unnerving to have a buggy system where the > backup program is the one which causes the crash! > > We do need to work on a better scheme for Mac installation. Let's think > about it. > > Emrys Williams > > Gerald Britton wrote: >> Looking at the exception codes I would guess that this is a bug in the >> Python port used on the Mac. Since gramps is written in Python, it >> cannot, by itself, cause a bus error, which usually means trying to >> access memory that is not yours, IIRC. >> >> Probably you should handle this though Apple support channels. >> >> On Tue, Jun 9, 2009 at 1:15 PM, John<jh...@ea...> wrote: >> >>> I recently installed the latest (as of a week or two ago) >>> MacPorts version of gramps. I eventually found how to get >>> it to fire up, and the few things I've tried so far seem >>> to work. Except, every time I click on Export, it crashes >>> and firing up again I need to clear the lock. >>> >>> The terminal window says simply: >>> bus error >>> >>> The system log file says: >>> >>> macintosh-2 ReportCrash[27020]: Formulating crash report for process >>> Python[26856] >>> macintosh-2 ReportCrash[27020]: Saved crashreport to >>> .../Library/Logs/CrashReporter/Python_2009-06-09-130347_Macintosh-2.crash >>> using uid: 501 gid: 501, euid: 501 egid: 501 >>> >>> And the Python crashreport begins (too long to post completely?): >>> >>> Process: Python [26856] >>> Path: >>> /opt/local/Library/Frameworks/Python.framework/Versions/2.5/Resources/Python.app/Contents/MacOS/Python >>> Identifier: Python >>> Version: ??? (???) >>> Code Type: X86 (Native) >>> Parent Process: bash [26781] >>> >>> Date/Time: 2009-06-09 13:03:47.160 -0400 >>> OS Version: Mac OS X 10.5.7 (9J61) >>> Report Version: 6 >>> Anonymous UUID: 8F7EB637-5CD5-4162-9800-DC228C380BAD >>> >>> Exception Type: EXC_BAD_ACCESS (SIGBUS) >>> Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000081 >>> Crashed Thread: 0 >>> >>> Thread 0 Crashed: >>> 0 org.python.python 0x001f53e4 PyType_IsSubtype + 148 >>> 1 _gobject.so 0x007241e9 >>> pyg_type_add_interfaces + 233 >>> 2 _gobject.so 0x00724481 pyg_type_register + 497 >>> 3 _gobject.so 0x007252ba >>> _wrap_pyg_type_register + 202 >>> 4 org.python.python 0x00239750 PyEval_EvalFrameEx + >>> 24144 >>> 5 org.python.python 0x00239c2e PyEval_EvalFrameEx + >>> 25390 >>> 6 org.python.python 0x0023b5ca PyEval_EvalCodeEx + 1962 >>> 7 org.python.python 0x001c845d function_call + 221 >>> 8 org.python.python 0x001a3bb2 PyObject_Call + 50 >>> 9 org.python.python 0x001ac966 instancemethod_call + 422 >>> 10 org.python.python 0x001a3bb2 PyObject_Call + 50 >>> 11 org.python.python 0x001f8337 slot_tp_init + 87 >>> 12 org.python.python 0x001fa9e0 type_call + 176 >>> 13 org.python.python 0x001a46a7 >>> PyObject_CallFunctionObjArgs + 151 >>> 14 org.python.python 0x002347e1 PyEval_EvalFrameEx + 3809 >>> 15 org.python.python 0x0023b5ca PyEval_EvalCodeEx + 1962 >>> 16 org.python.python 0x0023b6d7 PyEval_EvalCode + 87 >>> 17 org.python.python 0x00252fcc >>> PyImport_ExecCodeModuleEx + 188 >>> 18 org.python.python 0x00253453 load_source_module + 739 >>> ... >>> >>> Can anyone shed some light on what I need to do to get export to work? >>> Again, this the the MacPorts version. I had to install tons of >>> prerequisites via MacPorts to get this far, never having needed any >>> MacPorts software before. >>> >>> If the full crash dump is needed, and it is okay to post it, I can >>> do that. Or if there is a piece of it not shown that is more relevant, >>> I can post or look at just that. >>> >>> Thanks! >>> >>> ------------------------------------------------------------------------------ >>> Crystal Reports - New Free Runtime and 30 Day Trial >>> Check out the new simplified licensing option that enables unlimited >>> royalty-free distribution of the report engine for externally facing >>> server and web deployment. >>> http://p.sf.net/sfu/businessobjects >>> _______________________________________________ >>> Gramps-users mailing list >>> Gra...@li... >>> https://lists.sourceforge.net/lists/listinfo/gramps-users >>> >>> >> >> >> >> > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > -- Gerald Britton |
From: John <jh...@ea...> - 2009-06-10 02:04:46
|
Emrys Williams wrote: > Yes, this has just started happening to me, too. I see the python on my > imac is now > Python 2.5.4 (r254:67916, May 20 2009, 17:05:46) > [GCC 4.0.1 (Apple Inc. build 5490)] My Python is 2.5.1 and I see from googling that this is *the* version Apple delivers in Leopard. I'd consider upgrading to 2.5.4 (or later?) but it seems you have the same problem at 2.5.4 and I'm nervous about upgrading Python. Can/should I do that in Macports, I wonder, or a fresh download and install? I feel incredibly lucky that my MacBook didn't end up wounded after two days of MacPorts installs to get gramps working. I'll consider upgrading Python if I gain a confidence (somehow) that it is harmless to Leopard. But if Emrys has the same problem, it sounds like it might be a futile exercise anyway. I'm not sure yet how to proceed. Since I just installed gramps, I have no history of successes and failures with the code and package versions yet. John > and I think that export worked properly up until sometime around that time. > > I think that the automated updates to the X11 quartz application, and > now to python, cause unexpected stuff to happen to gramps. I posted a > note at > http://www.gramps-project.org/wiki/index.php?title=Mac_OS_X_MacPorts > about my latest experiences with X11 updating itself without me realising. > > It certainly is somewhat unnerving to have a buggy system where the > backup program is the one which causes the crash! > > We do need to work on a better scheme for Mac installation. Let's think > about it. > > Emrys Williams > > Gerald Britton wrote: >> Looking at the exception codes I would guess that this is a bug in the >> Python port used on the Mac. Since gramps is written in Python, it >> cannot, by itself, cause a bus error, which usually means trying to >> access memory that is not yours, IIRC. >> >> Probably you should handle this though Apple support channels. >> >> On Tue, Jun 9, 2009 at 1:15 PM, John<jh...@ea...> wrote: >> >>> I recently installed the latest (as of a week or two ago) >>> MacPorts version of gramps. I eventually found how to get >>> it to fire up, and the few things I've tried so far seem >>> to work. Except, every time I click on Export, it crashes >>> and firing up again I need to clear the lock. >>> >>> The terminal window says simply: >>> bus error >>> >>> The system log file says: >>> >>> macintosh-2 ReportCrash[27020]: Formulating crash report for process >>> Python[26856] >>> macintosh-2 ReportCrash[27020]: Saved crashreport to >>> .../Library/Logs/CrashReporter/Python_2009-06-09-130347_Macintosh-2.crash >>> using uid: 501 gid: 501, euid: 501 egid: 501 >>> >>> And the Python crashreport begins (too long to post completely?): >>> >>> Process: Python [26856] >>> Path: >>> /opt/local/Library/Frameworks/Python.framework/Versions/2.5/Resources/Python.app/Contents/MacOS/Python >>> Identifier: Python >>> Version: ??? (???) >>> Code Type: X86 (Native) >>> Parent Process: bash [26781] >>> >>> Date/Time: 2009-06-09 13:03:47.160 -0400 >>> OS Version: Mac OS X 10.5.7 (9J61) >>> Report Version: 6 >>> Anonymous UUID: 8F7EB637-5CD5-4162-9800-DC228C380BAD >>> >>> Exception Type: EXC_BAD_ACCESS (SIGBUS) >>> Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000081 >>> Crashed Thread: 0 >>> >>> Thread 0 Crashed: >>> 0 org.python.python 0x001f53e4 PyType_IsSubtype + 148 >>> 1 _gobject.so 0x007241e9 >>> pyg_type_add_interfaces + 233 >>> 2 _gobject.so 0x00724481 pyg_type_register + 497 >>> 3 _gobject.so 0x007252ba >>> _wrap_pyg_type_register + 202 >>> 4 org.python.python 0x00239750 PyEval_EvalFrameEx + >>> 24144 >>> 5 org.python.python 0x00239c2e PyEval_EvalFrameEx + >>> 25390 >>> 6 org.python.python 0x0023b5ca PyEval_EvalCodeEx + 1962 >>> 7 org.python.python 0x001c845d function_call + 221 >>> 8 org.python.python 0x001a3bb2 PyObject_Call + 50 >>> 9 org.python.python 0x001ac966 instancemethod_call + 422 >>> 10 org.python.python 0x001a3bb2 PyObject_Call + 50 >>> 11 org.python.python 0x001f8337 slot_tp_init + 87 >>> 12 org.python.python 0x001fa9e0 type_call + 176 >>> 13 org.python.python 0x001a46a7 >>> PyObject_CallFunctionObjArgs + 151 >>> 14 org.python.python 0x002347e1 PyEval_EvalFrameEx + 3809 >>> 15 org.python.python 0x0023b5ca PyEval_EvalCodeEx + 1962 >>> 16 org.python.python 0x0023b6d7 PyEval_EvalCode + 87 >>> 17 org.python.python 0x00252fcc >>> PyImport_ExecCodeModuleEx + 188 >>> 18 org.python.python 0x00253453 load_source_module + 739 >>> ... >>> >>> Can anyone shed some light on what I need to do to get export to work? >>> Again, this the the MacPorts version. I had to install tons of >>> prerequisites via MacPorts to get this far, never having needed any >>> MacPorts software before. >>> >>> If the full crash dump is needed, and it is okay to post it, I can >>> do that. Or if there is a piece of it not shown that is more relevant, >>> I can post or look at just that. >>> >>> Thanks! >>> >>> ------------------------------------------------------------------------------ >>> Crystal Reports - New Free Runtime and 30 Day Trial >>> Check out the new simplified licensing option that enables unlimited >>> royalty-free distribution of the report engine for externally facing >>> server and web deployment. >>> http://p.sf.net/sfu/businessobjects >>> _______________________________________________ >>> Gramps-users mailing list >>> Gra...@li... >>> https://lists.sourceforge.net/lists/listinfo/gramps-users >>> >>> >> >> >> > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > |
From: John <jh...@ea...> - 2009-06-18 15:13:42
|
Emrys Williams wrote: > Yes, this has just started happening to me, too. I see the python on my > imac is now > Python 2.5.4 (r254:67916, May 20 2009, 17:05:46) > [GCC 4.0.1 (Apple Inc. build 5490)] > and I think that export worked properly up until sometime around that time. > Emrys, Did you "solve" the problem? I have now installed: Python 2.6.2 XQuartz 2.3.3.2 (on MacOS X 10.5.7) and still get the same gramps export bus error. Macports installed gramps 3.0.4-1, is there a way to install a newer version via Macports or over the Macports install? (I have no data of any worth in gramps yet). Is there a reason to expect the problem would go away in a newer version of gramps? Thanks, John |
From: Emrys W. <emr...@ev...> - 2009-06-18 18:55:29
|
No, I haven't solved the problem. Gramps export still crashes on my mac. However, I have been distracted. I am trying to use this system: https://sourceforge.net/apps/trac/gtk-osx/wiki/Build to build a native Mac binary installable application out of gramps, so I have been busy at that instead of trying to fix the macports gramps. I have made some progress - but not great progress. I expect it to take at least another week of fooling around with programs I don't understand before I have a gramps that I can even attempt to run. I'm just about to post on the gramps-devel list about some issues there, if anyone feels like joining in. However, if I get it to work, I think it will be neater than either the fink or macports versions, and we'll have something we can at least file coherent bugs against. It should be able to read existing gramps databases, too. Personally, I choose to: (a) not worry too much about macports just at the moment (b) back up my database by copying the .gramps directory, and all its contents, to another location every so often. And copy all my media files like that too. (c) make sure the Mac Time Machine backups are working to another disk. then if we get a native gramps port working, maybe that will just work. You know, one day, I might actually get back to researching my family history! Does that make sense? Thanks! Emrys John wrote: > Emrys Williams wrote: > >> Yes, this has just started happening to me, too. I see the python on my >> imac is now >> Python 2.5.4 (r254:67916, May 20 2009, 17:05:46) >> [GCC 4.0.1 (Apple Inc. build 5490)] >> and I think that export worked properly up until sometime around that time. >> >> > > Emrys, > > Did you "solve" the problem? > I have now installed: > Python 2.6.2 > XQuartz 2.3.3.2 > (on MacOS X 10.5.7) > > and still get the same gramps export bus error. > > Macports installed gramps 3.0.4-1, is there a way to install a > newer version via Macports or over the Macports install? > (I have no data of any worth in gramps yet). > Is there a reason to expect the problem would go away in > a newer version of gramps? > > Thanks, > John > > > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > > |
From: Benny M. <ben...@gm...> - 2009-06-09 18:31:05
|
Anybody in linux with python 2.5.4 to see if it works there? To know the version, in a terminal: python -V Benny 2009/6/9 Emrys Williams <emr...@ev...>: > Yes, this has just started happening to me, too. I see the python on my > imac is now > Python 2.5.4 (r254:67916, May 20 2009, 17:05:46) > [GCC 4.0.1 (Apple Inc. build 5490)] > and I think that export worked properly up until sometime around that time. > > I think that the automated updates to the X11 quartz application, and > now to python, cause unexpected stuff to happen to gramps. I posted a > note at > http://www.gramps-project.org/wiki/index.php?title=Mac_OS_X_MacPorts > about my latest experiences with X11 updating itself without me realising. > > It certainly is somewhat unnerving to have a buggy system where the > backup program is the one which causes the crash! > > We do need to work on a better scheme for Mac installation. Let's think > about it. > > Emrys Williams > > Gerald Britton wrote: >> Looking at the exception codes I would guess that this is a bug in the >> Python port used on the Mac. Since gramps is written in Python, it >> cannot, by itself, cause a bus error, which usually means trying to >> access memory that is not yours, IIRC. >> >> Probably you should handle this though Apple support channels. >> >> On Tue, Jun 9, 2009 at 1:15 PM, John<jh...@ea...> wrote: >> >>> I recently installed the latest (as of a week or two ago) >>> MacPorts version of gramps. I eventually found how to get >>> it to fire up, and the few things I've tried so far seem >>> to work. Except, every time I click on Export, it crashes >>> and firing up again I need to clear the lock. >>> >>> The terminal window says simply: >>> bus error >>> >>> The system log file says: >>> >>> macintosh-2 ReportCrash[27020]: Formulating crash report for process >>> Python[26856] >>> macintosh-2 ReportCrash[27020]: Saved crashreport to >>> .../Library/Logs/CrashReporter/Python_2009-06-09-130347_Macintosh-2.crash >>> using uid: 501 gid: 501, euid: 501 egid: 501 >>> >>> And the Python crashreport begins (too long to post completely?): >>> >>> Process: Python [26856] >>> Path: >>> /opt/local/Library/Frameworks/Python.framework/Versions/2.5/Resources/Python.app/Contents/MacOS/Python >>> Identifier: Python >>> Version: ??? (???) >>> Code Type: X86 (Native) >>> Parent Process: bash [26781] >>> >>> Date/Time: 2009-06-09 13:03:47.160 -0400 >>> OS Version: Mac OS X 10.5.7 (9J61) >>> Report Version: 6 >>> Anonymous UUID: 8F7EB637-5CD5-4162-9800-DC228C380BAD >>> >>> Exception Type: EXC_BAD_ACCESS (SIGBUS) >>> Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000081 >>> Crashed Thread: 0 >>> >>> Thread 0 Crashed: >>> 0 org.python.python 0x001f53e4 PyType_IsSubtype + 148 >>> 1 _gobject.so 0x007241e9 >>> pyg_type_add_interfaces + 233 >>> 2 _gobject.so 0x00724481 pyg_type_register + 497 >>> 3 _gobject.so 0x007252ba >>> _wrap_pyg_type_register + 202 >>> 4 org.python.python 0x00239750 PyEval_EvalFrameEx + >>> 24144 >>> 5 org.python.python 0x00239c2e PyEval_EvalFrameEx + >>> 25390 >>> 6 org.python.python 0x0023b5ca PyEval_EvalCodeEx + 1962 >>> 7 org.python.python 0x001c845d function_call + 221 >>> 8 org.python.python 0x001a3bb2 PyObject_Call + 50 >>> 9 org.python.python 0x001ac966 instancemethod_call + 422 >>> 10 org.python.python 0x001a3bb2 PyObject_Call + 50 >>> 11 org.python.python 0x001f8337 slot_tp_init + 87 >>> 12 org.python.python 0x001fa9e0 type_call + 176 >>> 13 org.python.python 0x001a46a7 >>> PyObject_CallFunctionObjArgs + 151 >>> 14 org.python.python 0x002347e1 PyEval_EvalFrameEx + 3809 >>> 15 org.python.python 0x0023b5ca PyEval_EvalCodeEx + 1962 >>> 16 org.python.python 0x0023b6d7 PyEval_EvalCode + 87 >>> 17 org.python.python 0x00252fcc >>> PyImport_ExecCodeModuleEx + 188 >>> 18 org.python.python 0x00253453 load_source_module + 739 >>> ... >>> >>> Can anyone shed some light on what I need to do to get export to work? >>> Again, this the the MacPorts version. I had to install tons of >>> prerequisites via MacPorts to get this far, never having needed any >>> MacPorts software before. >>> >>> If the full crash dump is needed, and it is okay to post it, I can >>> do that. Or if there is a piece of it not shown that is more relevant, >>> I can post or look at just that. >>> >>> Thanks! >>> >>> ------------------------------------------------------------------------------ >>> Crystal Reports - New Free Runtime and 30 Day Trial >>> Check out the new simplified licensing option that enables unlimited >>> royalty-free distribution of the report engine for externally facing >>> server and web deployment. >>> http://p.sf.net/sfu/businessobjects >>> _______________________________________________ >>> Gramps-users mailing list >>> Gra...@li... >>> https://lists.sourceforge.net/lists/listinfo/gramps-users >>> >>> >> >> >> >> > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > |
From: Gerald B. <ger...@gm...> - 2009-06-09 18:36:50
|
I'm running 2.5.4, lemme check the export On Tue, Jun 9, 2009 at 2:30 PM, Benny Malengier<ben...@gm...> wrote: > Anybody in linux with python 2.5.4 to see if it works there? > To know the version, in a terminal: > python -V > > Benny > > 2009/6/9 Emrys Williams <emr...@ev...>: >> Yes, this has just started happening to me, too. I see the python on my >> imac is now >> Python 2.5.4 (r254:67916, May 20 2009, 17:05:46) >> [GCC 4.0.1 (Apple Inc. build 5490)] >> and I think that export worked properly up until sometime around that time. >> >> I think that the automated updates to the X11 quartz application, and >> now to python, cause unexpected stuff to happen to gramps. I posted a >> note at >> http://www.gramps-project.org/wiki/index.php?title=Mac_OS_X_MacPorts >> about my latest experiences with X11 updating itself without me realising. >> >> It certainly is somewhat unnerving to have a buggy system where the >> backup program is the one which causes the crash! >> >> We do need to work on a better scheme for Mac installation. Let's think >> about it. >> >> Emrys Williams >> >> Gerald Britton wrote: >>> Looking at the exception codes I would guess that this is a bug in the >>> Python port used on the Mac. Since gramps is written in Python, it >>> cannot, by itself, cause a bus error, which usually means trying to >>> access memory that is not yours, IIRC. >>> >>> Probably you should handle this though Apple support channels. >>> >>> On Tue, Jun 9, 2009 at 1:15 PM, John<jh...@ea...> wrote: >>> >>>> I recently installed the latest (as of a week or two ago) >>>> MacPorts version of gramps. I eventually found how to get >>>> it to fire up, and the few things I've tried so far seem >>>> to work. Except, every time I click on Export, it crashes >>>> and firing up again I need to clear the lock. >>>> >>>> The terminal window says simply: >>>> bus error >>>> >>>> The system log file says: >>>> >>>> macintosh-2 ReportCrash[27020]: Formulating crash report for process >>>> Python[26856] >>>> macintosh-2 ReportCrash[27020]: Saved crashreport to >>>> .../Library/Logs/CrashReporter/Python_2009-06-09-130347_Macintosh-2.crash >>>> using uid: 501 gid: 501, euid: 501 egid: 501 >>>> >>>> And the Python crashreport begins (too long to post completely?): >>>> >>>> Process: Python [26856] >>>> Path: >>>> /opt/local/Library/Frameworks/Python.framework/Versions/2.5/Resources/Python.app/Contents/MacOS/Python >>>> Identifier: Python >>>> Version: ??? (???) >>>> Code Type: X86 (Native) >>>> Parent Process: bash [26781] >>>> >>>> Date/Time: 2009-06-09 13:03:47.160 -0400 >>>> OS Version: Mac OS X 10.5.7 (9J61) >>>> Report Version: 6 >>>> Anonymous UUID: 8F7EB637-5CD5-4162-9800-DC228C380BAD >>>> >>>> Exception Type: EXC_BAD_ACCESS (SIGBUS) >>>> Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000081 >>>> Crashed Thread: 0 >>>> >>>> Thread 0 Crashed: >>>> 0 org.python.python 0x001f53e4 PyType_IsSubtype + 148 >>>> 1 _gobject.so 0x007241e9 >>>> pyg_type_add_interfaces + 233 >>>> 2 _gobject.so 0x00724481 pyg_type_register + 497 >>>> 3 _gobject.so 0x007252ba >>>> _wrap_pyg_type_register + 202 >>>> 4 org.python.python 0x00239750 PyEval_EvalFrameEx + >>>> 24144 >>>> 5 org.python.python 0x00239c2e PyEval_EvalFrameEx + >>>> 25390 >>>> 6 org.python.python 0x0023b5ca PyEval_EvalCodeEx + 1962 >>>> 7 org.python.python 0x001c845d function_call + 221 >>>> 8 org.python.python 0x001a3bb2 PyObject_Call + 50 >>>> 9 org.python.python 0x001ac966 instancemethod_call + 422 >>>> 10 org.python.python 0x001a3bb2 PyObject_Call + 50 >>>> 11 org.python.python 0x001f8337 slot_tp_init + 87 >>>> 12 org.python.python 0x001fa9e0 type_call + 176 >>>> 13 org.python.python 0x001a46a7 >>>> PyObject_CallFunctionObjArgs + 151 >>>> 14 org.python.python 0x002347e1 PyEval_EvalFrameEx + 3809 >>>> 15 org.python.python 0x0023b5ca PyEval_EvalCodeEx + 1962 >>>> 16 org.python.python 0x0023b6d7 PyEval_EvalCode + 87 >>>> 17 org.python.python 0x00252fcc >>>> PyImport_ExecCodeModuleEx + 188 >>>> 18 org.python.python 0x00253453 load_source_module + 739 >>>> ... >>>> >>>> Can anyone shed some light on what I need to do to get export to work? >>>> Again, this the the MacPorts version. I had to install tons of >>>> prerequisites via MacPorts to get this far, never having needed any >>>> MacPorts software before. >>>> >>>> If the full crash dump is needed, and it is okay to post it, I can >>>> do that. Or if there is a piece of it not shown that is more relevant, >>>> I can post or look at just that. >>>> >>>> Thanks! >>>> >>>> ------------------------------------------------------------------------------ >>>> Crystal Reports - New Free Runtime and 30 Day Trial >>>> Check out the new simplified licensing option that enables unlimited >>>> royalty-free distribution of the report engine for externally facing >>>> server and web deployment. >>>> http://p.sf.net/sfu/businessobjects >>>> _______________________________________________ >>>> Gramps-users mailing list >>>> Gra...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gramps-users >>>> >>>> >>> >>> >>> >>> >> >> ------------------------------------------------------------------------------ >> Crystal Reports - New Free Runtime and 30 Day Trial >> Check out the new simplified licensing option that enables unlimited >> royalty-free distribution of the report engine for externally facing >> server and web deployment. >> http://p.sf.net/sfu/businessobjects >> _______________________________________________ >> Gramps-users mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-users >> > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > -- Gerald Britton |
From: Gerald B. <ger...@gm...> - 2009-06-09 18:41:50
|
No problem with export on my system On Tue, Jun 9, 2009 at 2:36 PM, Gerald Britton<ger...@gm...> wrote: > I'm running 2.5.4, lemme check the export > > On Tue, Jun 9, 2009 at 2:30 PM, Benny > Malengier<ben...@gm...> wrote: >> Anybody in linux with python 2.5.4 to see if it works there? >> To know the version, in a terminal: >> python -V >> >> Benny >> >> 2009/6/9 Emrys Williams <emr...@ev...>: >>> Yes, this has just started happening to me, too. I see the python on my >>> imac is now >>> Python 2.5.4 (r254:67916, May 20 2009, 17:05:46) >>> [GCC 4.0.1 (Apple Inc. build 5490)] >>> and I think that export worked properly up until sometime around that time. >>> >>> I think that the automated updates to the X11 quartz application, and >>> now to python, cause unexpected stuff to happen to gramps. I posted a >>> note at >>> http://www.gramps-project.org/wiki/index.php?title=Mac_OS_X_MacPorts >>> about my latest experiences with X11 updating itself without me realising. >>> >>> It certainly is somewhat unnerving to have a buggy system where the >>> backup program is the one which causes the crash! >>> >>> We do need to work on a better scheme for Mac installation. Let's think >>> about it. >>> >>> Emrys Williams >>> >>> Gerald Britton wrote: >>>> Looking at the exception codes I would guess that this is a bug in the >>>> Python port used on the Mac. Since gramps is written in Python, it >>>> cannot, by itself, cause a bus error, which usually means trying to >>>> access memory that is not yours, IIRC. >>>> >>>> Probably you should handle this though Apple support channels. >>>> >>>> On Tue, Jun 9, 2009 at 1:15 PM, John<jh...@ea...> wrote: >>>> >>>>> I recently installed the latest (as of a week or two ago) >>>>> MacPorts version of gramps. I eventually found how to get >>>>> it to fire up, and the few things I've tried so far seem >>>>> to work. Except, every time I click on Export, it crashes >>>>> and firing up again I need to clear the lock. >>>>> >>>>> The terminal window says simply: >>>>> bus error >>>>> >>>>> The system log file says: >>>>> >>>>> macintosh-2 ReportCrash[27020]: Formulating crash report for process >>>>> Python[26856] >>>>> macintosh-2 ReportCrash[27020]: Saved crashreport to >>>>> .../Library/Logs/CrashReporter/Python_2009-06-09-130347_Macintosh-2.crash >>>>> using uid: 501 gid: 501, euid: 501 egid: 501 >>>>> >>>>> And the Python crashreport begins (too long to post completely?): >>>>> >>>>> Process: Python [26856] >>>>> Path: >>>>> /opt/local/Library/Frameworks/Python.framework/Versions/2.5/Resources/Python.app/Contents/MacOS/Python >>>>> Identifier: Python >>>>> Version: ??? (???) >>>>> Code Type: X86 (Native) >>>>> Parent Process: bash [26781] >>>>> >>>>> Date/Time: 2009-06-09 13:03:47.160 -0400 >>>>> OS Version: Mac OS X 10.5.7 (9J61) >>>>> Report Version: 6 >>>>> Anonymous UUID: 8F7EB637-5CD5-4162-9800-DC228C380BAD >>>>> >>>>> Exception Type: EXC_BAD_ACCESS (SIGBUS) >>>>> Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000081 >>>>> Crashed Thread: 0 >>>>> >>>>> Thread 0 Crashed: >>>>> 0 org.python.python 0x001f53e4 PyType_IsSubtype + 148 >>>>> 1 _gobject.so 0x007241e9 >>>>> pyg_type_add_interfaces + 233 >>>>> 2 _gobject.so 0x00724481 pyg_type_register + 497 >>>>> 3 _gobject.so 0x007252ba >>>>> _wrap_pyg_type_register + 202 >>>>> 4 org.python.python 0x00239750 PyEval_EvalFrameEx + >>>>> 24144 >>>>> 5 org.python.python 0x00239c2e PyEval_EvalFrameEx + >>>>> 25390 >>>>> 6 org.python.python 0x0023b5ca PyEval_EvalCodeEx + 1962 >>>>> 7 org.python.python 0x001c845d function_call + 221 >>>>> 8 org.python.python 0x001a3bb2 PyObject_Call + 50 >>>>> 9 org.python.python 0x001ac966 instancemethod_call + 422 >>>>> 10 org.python.python 0x001a3bb2 PyObject_Call + 50 >>>>> 11 org.python.python 0x001f8337 slot_tp_init + 87 >>>>> 12 org.python.python 0x001fa9e0 type_call + 176 >>>>> 13 org.python.python 0x001a46a7 >>>>> PyObject_CallFunctionObjArgs + 151 >>>>> 14 org.python.python 0x002347e1 PyEval_EvalFrameEx + 3809 >>>>> 15 org.python.python 0x0023b5ca PyEval_EvalCodeEx + 1962 >>>>> 16 org.python.python 0x0023b6d7 PyEval_EvalCode + 87 >>>>> 17 org.python.python 0x00252fcc >>>>> PyImport_ExecCodeModuleEx + 188 >>>>> 18 org.python.python 0x00253453 load_source_module + 739 >>>>> ... >>>>> >>>>> Can anyone shed some light on what I need to do to get export to work? >>>>> Again, this the the MacPorts version. I had to install tons of >>>>> prerequisites via MacPorts to get this far, never having needed any >>>>> MacPorts software before. >>>>> >>>>> If the full crash dump is needed, and it is okay to post it, I can >>>>> do that. Or if there is a piece of it not shown that is more relevant, >>>>> I can post or look at just that. >>>>> >>>>> Thanks! >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Crystal Reports - New Free Runtime and 30 Day Trial >>>>> Check out the new simplified licensing option that enables unlimited >>>>> royalty-free distribution of the report engine for externally facing >>>>> server and web deployment. >>>>> http://p.sf.net/sfu/businessobjects >>>>> _______________________________________________ >>>>> Gramps-users mailing list >>>>> Gra...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/gramps-users >>>>> >>>>> >>>> >>>> >>>> >>>> >>> >>> ------------------------------------------------------------------------------ >>> Crystal Reports - New Free Runtime and 30 Day Trial >>> Check out the new simplified licensing option that enables unlimited >>> royalty-free distribution of the report engine for externally facing >>> server and web deployment. >>> http://p.sf.net/sfu/businessobjects >>> _______________________________________________ >>> Gramps-users mailing list >>> Gra...@li... >>> https://lists.sourceforge.net/lists/listinfo/gramps-users >>> >> >> ------------------------------------------------------------------------------ >> Crystal Reports - New Free Runtime and 30 Day Trial >> Check out the new simplified licensing option that enables unlimited >> royalty-free distribution of the report engine for externally facing >> server and web deployment. >> http://p.sf.net/sfu/businessobjects >> _______________________________________________ >> Gramps-users mailing list >> Gra...@li... >> https://lists.sourceforge.net/lists/listinfo/gramps-users >> > > > > -- > Gerald Britton > -- Gerald Britton |
From: Emrys W. <emr...@ev...> - 2009-06-10 08:22:46
|
I'm not sure how I ended up with this version of python, then. But it doesn't seem to be the problem. There is some underlying bug that has only started being exercised recently - gramps export certainly worked for me on iMac on 9 May 2009, and I have the archive to prove it! The OS and X11 updates that arrived starting on 15 May certainly changed the behaviour of gramps a great deal. If we're to support gramps properly for users on Mac, we have to create a proper package of gramps, python, a pile of libraries, and X11, all as a simple installable package - no need to sign up as an apple developer. That may be hard to achieve, if only because of all the various licences involved. I have no idea yet how to do that, but until we do, we're going to struggle with all these various components updating at different times and exercising different bugs. John, I think you're right to think that you're lucky to get through the mac gramps install process. It took me over 7 hours, with the latest iMac and a 4Mbit broadband connection, to install macports gramps, even though almost nothing went wrong. It really is quite a remarkable tribute to proper design that all that computing can produce a working program. However, it would be much nicer to just click and install. And click-and-upgrade. I have no idea how to upgrade from the gramps 3.0.4.1 which is what macports gives us. Especially with the export feature not working! Emrys John wrote: > Emrys Williams wrote: > >> Yes, this has just started happening to me, too. I see the python on my >> imac is now >> Python 2.5.4 (r254:67916, May 20 2009, 17:05:46) >> [GCC 4.0.1 (Apple Inc. build 5490)] >> > > My Python is 2.5.1 and I see from googling that this is *the* version > Apple delivers in Leopard. I'd consider upgrading to 2.5.4 (or later?) > but it seems you have the same problem at 2.5.4 and I'm nervous about > upgrading Python. Can/should I do that in Macports, I wonder, or a fresh > download and install? > > I feel incredibly lucky that my MacBook didn't end up wounded after two > days of MacPorts installs to get gramps working. I'll consider upgrading > Python if I gain a confidence (somehow) that it is harmless to Leopard. > But if Emrys has the same problem, it sounds like it might be a futile > exercise anyway. > > I'm not sure yet how to proceed. Since I just installed gramps, I have > no history of successes and failures with the code and package versions > yet. > > John > > > |
From: Benny M. <ben...@gm...> - 2009-06-10 09:47:19
|
2009/6/10 Emrys Williams <emr...@ev...>: > program. However, it would be much nicer to just click and install. And > click-and-upgrade. I have no idea how to upgrade from the gramps 3.0.4.1 > which is what macports gives us. Especially with the export feature not > working! About this, if you backup the database directory (in a terminal: gramps -l to see all family trees and their directory path), then you can upgrade, and the new GRAMPS will see your old trees. On click, he will ask you if ok to upgrade the file. So without export, you can still upgrade to a new version. Just take a real backup of the data, instead of doing a backup via the export option. Benny |
From: Benny M. <ben...@gm...> - 2009-06-10 09:45:18
|
2009/6/10 Emrys Williams <emr...@ev...>: > If we're to support gramps properly for users on Mac, we have to create > a proper package of gramps, python, a pile of libraries, and X11, all as > a simple installable package - no need to sign up as an apple developer. > That may be hard to achieve, if only because of all the various licences > involved. I have no idea yet how to do that, but until we do, we're > going to struggle with all these various components updating at > different times and exercising different bugs. > No, I believe this would be the wrong approach. The good approach would be to make GRAMPS native on MAC, using the gtk-osx project: http://apps.sourceforge.net/trac/gtk-osx/wiki/WikiStart They have gnucash and gimp native on Mac, so it should work for GRAMPS too. Perhaps you should take up contact with the developers of that project? If somebody donates me a Mac, I can look into too ;-D Benny |
From: Benny M. <ben...@gm...> - 2009-06-10 10:49:20
|
2009/6/10 Benny Malengier <ben...@gm...>: > 2009/6/10 Emrys Williams <emr...@ev...>: > >> If we're to support gramps properly for users on Mac, we have to create >> a proper package of gramps, python, a pile of libraries, and X11, all as >> a simple installable package - no need to sign up as an apple developer. >> That may be hard to achieve, if only because of all the various licences >> involved. I have no idea yet how to do that, but until we do, we're >> going to struggle with all these various components updating at >> different times and exercising different bugs. >> > > No, I believe this would be the wrong approach. The good approach > would be to make GRAMPS native on MAC, using the gtk-osx project: > > http://apps.sourceforge.net/trac/gtk-osx/wiki/WikiStart > > They have gnucash and gimp native on Mac, so it should work for GRAMPS > too. Perhaps you should take up contact with the developers of that > project? If somebody donates me a Mac, I can look into too ;-D > To get you started, I asked it on their new forum: https://apps.sourceforge.net/phpbb/gtk-osx/viewtopic.php?f=4&t=4 Join in! Further discussion on this better go to the developer mailing list though. Benny > Benny > |
From: Emrys W. <emr...@ev...> - 2009-06-10 11:58:22
|
Give me a chance, I've not finished reading the first page of their wiki yet! Yes, this looks a good scheme, much simpler than all the separate bits and pieces. I will read all about it and then come back when I'm stuck. Thanks! Emrys Williams Benny Malengier wrote: > 2009/6/10 Benny Malengier <ben...@gm...>: > >> 2009/6/10 Emrys Williams <emr...@ev...>: >> >> >>> If we're to support gramps properly for users on Mac, we have to create >>> a proper package of gramps, python, a pile of libraries, and X11, all as >>> a simple installable package - no need to sign up as an apple developer. >>> That may be hard to achieve, if only because of all the various licences >>> involved. I have no idea yet how to do that, but until we do, we're >>> going to struggle with all these various components updating at >>> different times and exercising different bugs. >>> >>> >> No, I believe this would be the wrong approach. The good approach >> would be to make GRAMPS native on MAC, using the gtk-osx project: >> >> http://apps.sourceforge.net/trac/gtk-osx/wiki/WikiStart >> >> They have gnucash and gimp native on Mac, so it should work for GRAMPS >> too. Perhaps you should take up contact with the developers of that >> project? If somebody donates me a Mac, I can look into too ;-D >> >> > > To get you started, I asked it on their new forum: > > https://apps.sourceforge.net/phpbb/gtk-osx/viewtopic.php?f=4&t=4 > > Join in! > Further discussion on this better go to the developer mailing list though. > > Benny > >> Benny >> >> > > |
From: Theo T. <tj....@ph...> - 2009-06-11 14:36:33
|
I think I should let Gramps-users know that I have installed the recent new version under LinuxMint-7 codenamed Gloria and it is running so far with no problems. With best wishes, Yours sincerely, - Theo Tulley. tj....@ph... |
From: Benny M. <ben...@gm...> - 2009-06-11 15:02:29
|
2009/6/11 Theo Tulley <tj....@ph...>: > I think I should let Gramps-users know that I have installed the recent > new version under LinuxMint-7 codenamed Gloria and it is running so far > with no problems. Did you use the ubuntu package, or a specific linuxmint package? If the ubuntu package, add linuxmint in the list of derivatives at http://www.gramps-project.org/wiki/index.php?title=Installation#Manual_download_and_install_of_GRAMPS Benny |
From: Theo T. <tj....@ph...> - 2009-06-11 19:50:27
|
I used the Ubuntu 9.04 package - from which LinuxMint-7 is derived. I don't know how to add that to the list of derivatives - I thought the Mint team had to set up the Mint repository. Theo. Benny Malengier wrote: > 2009/6/11 Theo Tulley <tj....@ph...>: > >> I think I should let Gramps-users know that I have installed the recent >> new version under LinuxMint-7 codenamed Gloria and it is running so far >> with no problems. >> > > Did you use the ubuntu package, or a specific linuxmint package? > If the ubuntu package, add linuxmint in the list of derivatives at > http://www.gramps-project.org/wiki/index.php?title=Installation#Manual_download_and_install_of_GRAMPS > > Benny > > |
From: John <jh...@ea...> - 2009-06-17 16:00:12
|
I have now installed: Python 2.6.2 XQuartz 2.3.3.2 (on MacOS X 10.5.7) and get the same gramps export bus error. Part of the Python crash file: Process: Python [12691] Path: /opt/local/Library/Frameworks/Python.framework/Versions/2.5/Resources/Python.app/Contents/MacOS/Python Identifier: Python Version: ??? (???) Code Type: X86 (Native) Parent Process: bash [12682] Date/Time: 2009-06-17 11:44:17.508 -0400 OS Version: Mac OS X 10.5.7 (9J61) Report Version: 6 Anonymous UUID: 8F7EB637-5CD5-4162-9800-DC228C380BAD Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000081 Crashed Thread: 0 Thread 0 Crashed: 0 org.python.python 0x001f53e4 PyType_IsSubtype + 148 1 _gobject.so 0x007241e9 pyg_type_add_interfaces + 233 === Now one thing I see above is the Python Versions/2.5/Resources in the path. But: % which python /Library/Frameworks/Python.framework/Versions/2.6/bin/python Is the Python path in gramps "hardwired" somewhere? Should I reinstall gramps? How should I do that (MacPorts)? Other ideas? Thanks, John John wrote: > I recently installed the latest (as of a week or two ago) > MacPorts version of gramps. I eventually found how to get > it to fire up, and the few things I've tried so far seem > to work. Except, every time I click on Export, it crashes > and firing up again I need to clear the lock. > > The terminal window says simply: > bus error > > The system log file says: > > macintosh-2 ReportCrash[27020]: Formulating crash report for process > Python[26856] > macintosh-2 ReportCrash[27020]: Saved crashreport to > .../Library/Logs/CrashReporter/Python_2009-06-09-130347_Macintosh-2.crash > using uid: 501 gid: 501, euid: 501 egid: 501 > > And the Python crashreport begins (too long to post completely?): > > Process: Python [26856] > Path: > /opt/local/Library/Frameworks/Python.framework/Versions/2.5/Resources/Python.app/Contents/MacOS/Python > > Identifier: Python > Version: ??? (???) > Code Type: X86 (Native) > Parent Process: bash [26781] > > Date/Time: 2009-06-09 13:03:47.160 -0400 > OS Version: Mac OS X 10.5.7 (9J61) > Report Version: 6 > Anonymous UUID: 8F7EB637-5CD5-4162-9800-DC228C380BAD > > Exception Type: EXC_BAD_ACCESS (SIGBUS) > Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000081 > Crashed Thread: 0 > > Thread 0 Crashed: > 0 org.python.python 0x001f53e4 PyType_IsSubtype + 148 > 1 _gobject.so 0x007241e9 > pyg_type_add_interfaces + 233 > 2 _gobject.so 0x00724481 pyg_type_register + 497 > 3 _gobject.so 0x007252ba > _wrap_pyg_type_register + 202 > 4 org.python.python 0x00239750 PyEval_EvalFrameEx + > 24144 > 5 org.python.python 0x00239c2e PyEval_EvalFrameEx + > 25390 > 6 org.python.python 0x0023b5ca PyEval_EvalCodeEx + 1962 > 7 org.python.python 0x001c845d function_call + 221 > 8 org.python.python 0x001a3bb2 PyObject_Call + 50 > 9 org.python.python 0x001ac966 instancemethod_call + > 422 > 10 org.python.python 0x001a3bb2 PyObject_Call + 50 > 11 org.python.python 0x001f8337 slot_tp_init + 87 > 12 org.python.python 0x001fa9e0 type_call + 176 > 13 org.python.python 0x001a46a7 > PyObject_CallFunctionObjArgs + 151 > 14 org.python.python 0x002347e1 PyEval_EvalFrameEx + > 3809 > 15 org.python.python 0x0023b5ca PyEval_EvalCodeEx + 1962 > 16 org.python.python 0x0023b6d7 PyEval_EvalCode + 87 > 17 org.python.python 0x00252fcc > PyImport_ExecCodeModuleEx + 188 > 18 org.python.python 0x00253453 load_source_module + 739 > ... > > Can anyone shed some light on what I need to do to get export to work? > Again, this the the MacPorts version. I had to install tons of > prerequisites via MacPorts to get this far, never having needed any > MacPorts software before. > > If the full crash dump is needed, and it is okay to post it, I can > do that. Or if there is a piece of it not shown that is more relevant, > I can post or look at just that. > > Thanks! > |