abrt version: 1.1.13 architecture: x86_64 cmdline: /usr/bin/python -O /usr/share/gramps/gramps.py comment: never started gramps before component: gramps executable: /usr/bin/python kernel: 2.6.35.6-48.fc14.x86_64 package: gramps-3.2.4-2.fc14 rating: 4 reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1289338119 uid: 500 backtrace ----- [New Thread 4124] [New Thread 4132] [New Thread 4131] [New Thread 4133] Core was generated by `/usr/bin/python -O /usr/share/gramps/gramps.py'. Program terminated with signal 11, Segmentation fault. #0 0x00000034c9e597c3 in FixedVMPoolAllocator (this=<value optimized out>) at JavaScriptCore/jit/ExecutableAllocatorFixedVMPool.cpp:308 Timeout exceeded: 60 second, killing gdb Debuginfo absent: 4257771e62117a262b24534d02815175ef7f4164 How to reproduce ----- 1. just started gramps 2. 3.
Created attachment 459273 [details] File: backtrace
Same problem for me. Gramps simply never starts up on Fedora 14.
gramps-3.2.5-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/gramps-3.2.5-1.fc14
gramps-3.2.5-1.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gramps'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/gramps-3.2.5-1.fc14
I tried out the new build, but the problem is not solved: it crashes with exactly the same error and stacktrace.
Copied from line in abrt: Package: gramps-3.2.5-1.fc14 Latest Crash: Sun 21 Nov 2010 10:35:01 AM Command: /usr/bin/python -O /usr/share/gramps/gramps.py Reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV) Comment: None Bug Reports: Copied from detail of line in abrt: [New Thread 7128] [New Thread 7141] [New Thread 7142] [New Thread 7143] Core was generated by `/usr/bin/python -O /usr/share/gramps/gramps.py'. Program terminated with signal 11, Segmentation fault. #0 0x00000030024597c3 in FixedVMPoolAllocator (this=<value optimized out>) at JavaScriptCore/jit/ExecutableAllocatorFixedVMPool.cpp:308 Timeout exceeded: 60 second, killing gdb Debuginfo absent: 4257771e62117a262b24534d02815175ef7f4164
Hmmm... I'm thinking that this has more to do with the embedded web browser. It looks like Gramps will use either webkit or gtkmozembed, depending on what's installed. Can you tell me what the output of "rpm -q pywebkitgtk gnome-python2-gtkmozembed" is?
I have the following: $ rpm -q pywebkitgtk gnome-python2-gtkmozembed pywebkitgtk-1.1.6-2.fc12.x86_64 package gnome-python2-gtkmozembed is not installed
Sorry, that's on my current Fedora 12 system... Here's the correct output: $ rpm -q pywebkitgtk gnome-python2-gtkmozembed pywebkitgtk-1.1.6-5.fc14.x86_64 package gnome-python2-gtkmozembed is not installed
Ok, I'm going to assign this to pywebkitgtk then, as this appears to be dying somewhere inside pywebkitgkt. You could try uninstalling pywebkitgtk and installing gnome-python2-gtkmozembed to see if anything changes, but I don't know what else would get uninstalled when you take pywebkitgtk out.
Yes, you seem to be correct. I did what you proposed (the only dependency that I also had to uninstall was rhythmbox), and then indeed gramps started. So the cause is pywebkitgtk.
*** Bug 657922 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 648319 ***