abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: /usr/bin/python -O /usr/share/gramps/gramps.py comment: I had just started Gramps up. It had not displayed on the screen yet. component: gramps crash_function: FixedVMPoolAllocator 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: 1289435405 uid: 500
Created attachment 459592 [details] File: backtrace
Package: gramps-3.2.4-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Start the program. It crashes during initialization. 2. 3.
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
Package: gramps-3.2.4-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Starting gramps 2. 3. Comment ----- I built the 3.2.5 version of gramps using the spec file from 3.2.4 (fedora). The 3.2.5 version crashes the same, but won't report here because of my gpg key not being accepted. Gramps seems to work fine until I quit the program and then try to restart it. Then the failure is hard in that it will never run again until I reboot my system.
*** This bug has been marked as a duplicate of bug 648319 ***