Bug 208047 - app segfaults when trying to load a db4 database
Summary: app segfaults when trying to load a db4 database
Alias: None
Product: Fedora
Classification: Fedora
Component: gramps
Version: rawhide
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2006-09-26 02:24 UTC by Steven Usdansky
Modified: 2007-11-30 22:11 UTC (History)
0 users

Clone Of:
Last Closed: 2006-11-26 16:33:18 UTC

Attachments (Terms of Use)

Description Steven Usdansky 2006-09-26 02:24:01 UTC
Description of problem:
Working with self-compiled gramps-2.1.95. Gramps crashes when loading or trying
to create a new db4 database.

Version-Release number of selected component (if applicable):

How reproducible:
every time

Steps to Reproduce:
1. Start gramps
2a. File-> New to create a new datanase
2b. File->Open and select an existing gramps db4 database
Actual results:
Segmentation fault

Expected results:
new or existing database opened as requested

Additional info:
reverting to db4-4.3.29-7.fc6 fixes the problem

Terminal session of crash:
media/disk/mishpaha$ gramps mishpaha.grdb
Spelling checker is not installed
/usr/local/share/gramps/DisplayState.py:315: GtkWarning:
gtk_menu_attach_to_widget(): menu already attached to GtkImageMenuItem
LPRDoc: Free true type fonts not found.
        Found Microsoft true type fonts. Will use them for now.
        These fonts are not free. 
        You are advised to switch to Free true type fonts
        INSTALL Free true type fonts
        from http://www.nongnu.org/freefont/
Trying to open: mishpaha.grdb ...
Type: GRAMPS database
Segmentation fault

Comment 1 Jindrich Novy 2006-09-26 08:10:05 UTC
Works for me with gramps-2.0.11.fc6 and db4-4.3.29-9.fc6 following your test case.

Reassigning to gramps to get more info from the gramps side.

Brian, are you able to reproduce that?

Comment 2 Brian Pepple 2006-09-26 14:19:01 UTC
I've got to reinstall Rawhide again, but once I do I'll try to reproduce this. 
It will probably be next week though, since I'm going to be fairly busy with
Ohio LinuxFest work this week.

Comment 3 Brian Pepple 2006-10-25 19:04:10 UTC
I'm unable to reproduce this error either, using either of the methods outlined.
 Steven, are you still experiencing it?  If so, do you have a sample db for me
to test with?

Comment 4 Brian Pepple 2006-11-16 21:52:55 UTC

Comment 5 Brian Pepple 2006-11-26 16:33:18 UTC
Closing due to being unable to reproduce this.  Steven, If this is still a
problem, please re-open and attach some sample data for me to reproduce the bug.

Note You need to log in before you can comment on or make changes to this bug.