This page lists some long-standing recurring issues with Gramps. Be sure also to read the instructions on [[using the bug tracker]], and to check the bug tracker to learn what the current actively researched issues are --- they aren't reported here.

−

* Some Gtk versions seem not to properly refresh the GUI (need to use the mouse cursor), see bug {{bug|4863}}.

+

−

* Some Gtk versions have a refresh issue on Citation TreeView (3.4.x) after an edition, see bug {{bug|5688}}.

+

==Dependencies==

+

+

{| {{prettytable}}

+

|- align="center"

+

! Problem

+

! Cause on gramps3

+

! Cause on gramps4

+

|-

+

|freezes and crashes when refreshing the people or place tree view, Gnome desktop

+

|bgcolor="red"|ATK/GAIL

+

|bgcolor="geen"|

+

|-

+

|blank text into field

+

|bgcolor="red"| gtk+ < 3.0

+

|bgcolor="geen"|

+

|-

+

|segfault on expand all nodes/rows into a tree view

+

|bgcolor="geen"|

+

|bgcolor="red"|GObject < 3.4.0

+

|-

+

|missing scrollbars

+

|bgcolor="geen"|

+

|bgcolor="red"|3.6.4 < Gtk+ < 3.10.6

+

|-

+

|strange layout for menu into Geography views

+

|bgcolor="geen"|

+

|bgcolor="red"|Gtk+ >= 3.8

+

|-

+

|freeze after editing data

+

|bgcolor="geen"|

+

|bgcolor="red"|3.x < Gtk+ < 3.14.7

+

|-

+

|}

+

+

===Gramps and some Gtk versions===

+

* Some Gtk versions seem not to properly refresh the GUI (need to use the mouse cursor), see bug {{bug|4863}} CLOSED.

+

* Some Gtk versions have a refresh issue on Citation TreeView (3.4.x) after an edition, see bug {{bug|5688}} FEEDBACK.

There have been multiple reports of long freezes and crashes of GRAMPS when refreshing the people or place tree view, e.g. after editing a person or changing the Name Display Format. They are related to the use of GNOME Assistive Technologies (ATK/GAIL).

+

There have been multiple reports of long freezes and crashes of Gramps when refreshing the people or place tree view, e.g. after editing a person or changing the Name Display Format. They are related to the use of GNOME Assistive Technologies (ATK/GAIL).

If Python returns a codec/UTF8 warning and this file was pasted from an external support (CD, HD, USB key), maybe filename has been corrupted ! It seems correct on screen but not on command line. Your OS was not able to properly set the encoding used on your external support.

If Python returns a codec/UTF8 warning and this file was pasted from an external support (CD, HD, USB key), maybe filename has been corrupted ! It seems correct on screen but not on command line. Your OS was not able to properly set the encoding used on your external support.

Line 68:

Line 119:

You can try to fix the filename by setting the correct character. Now you will be able to import this file into Gramps !

You can try to fix the filename by setting the correct character. Now you will be able to import this file into Gramps !

−

== GRAMPS cannot display some characters into reports ==

+

==Reports ==

−

RTF (''C style escape''), Postscript (''latin1''), LaTex (''latin1'') file formats on output are not designed for an unicode support.

+

=== Gramps cannot display some characters into reports ===

−

It is possible to get a strange non-ASCII character handling by using these formats.

+

−

It could be very specific, because it has been tested and improved since many versions, but possible.

+

−

== GRAMPS cannot set date greater than 21 ==

+

RTF (''C style escape'') and LaTeX (''latin1'') file format backends on output not initially designed for a unicode support.

Latest revision as of 07:03, 25 February 2015

This page lists some long-standing recurring issues with Gramps. Be sure also to read the instructions on using the bug tracker, and to check the bug tracker to learn what the current actively researched issues are --- they aren't reported here.

Gramps and some python gobject introspection versions

There have been multiple reports of long freezes and crashes of Gramps when refreshing the people or place tree view, e.g. after editing a person or changing the Name Display Format. They are related to the use of GNOME Assistive Technologies (ATK/GAIL).

No horizontal scrollbars

Database

Gramps runs out of locks

With a large database, Gramps can "run out of available locks".
For 140.000 people you should use: max_locks 300000 and max_objects 300000

The easiest way to do this is to create an empty database the add a file DB_CONFIG to the database directory before importing (see gramps -l output for the directory of a specific family tree. Contents of this DB_CONFIG file should be:

Data

Gramps and AttributeError

This message is often related to your data into your FamilyTree.
See AttributeError

Encoding

Gramps cannot import media with non-ASCII characters on filename

If Python returns a codec/UTF8 warning and this file was pasted from an external support (CD, HD, USB key), maybe filename has been corrupted ! It seems correct on screen but not on command line. Your OS was not able to properly set the encoding used on your external support.