Changes

Jump to: navigation, search

Known issues

5,414 bytes added, 22 January
m
See also
= GRAMPS Freezes and crashes ={{stub}}
There have been multiple reports Lists of some long freezes and crashes of GRAMPS when refreshing -standing recurring issues with Gramps. Be sure also to read the instructions on [[using the people viewbug tracker]], e.g. after editing a person or changing and to check the Name Display Format. They seem to be related bug tracker to learn what the use of GNOME Assistive Technologies. If you experience similar problems try going into System current actively researched issues are --> Preferences -> Assistive Technologies, unchecking "Enable assistive technologies" and logging out and in againthey aren't reported here.
== See also Dependencies==* [http://bugzilla.gnome.org/show_bug.cgi?id=571596 GNOME Bug]
{| {{prettytable}}|- align= GRAMPS runs out of locks "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|-|}
With ===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}} Only an issue for Gramps 3.x / Not reproducible in Gramps 4.x or newer.* Some Gtk versions have a large databaserefresh issue on Citation TreeView (3.4.x) after an edition, see bug {{bug|5688}} FEEDBACK.* Incremental search and synchronization with typed letters, see bug {{bug|1450}} Resolved in Gramps 4.2.0.* New row/line on [[Census_Addons|Census gramplet (addon)]], see bug [http://www.gramps-project.org/bugs/view.php?id=5688#c24063 5688] Only an issue for Gramps 3.x / Not reproducible in Gramps 4.x or newer..* Layout issue for menu into Geography, GRAMPS can "run out of available locks"see bug [https://gramps-project. See org/bugs/view.php?id=5742#c38355 5742].* Gramps freezes after editing a data, see bug report below{{bug|7772}}. Fixed by using GTK+ 3.14.8 or higher.
== See also =Gramps and some python gobject introspection versions===* pygobject < 3.4.0: : segfault on expand all nodes/rows into a Tree View, see bug {{bug|6289}}.
=== Gramps freezes and crashes with ATK / GNOME / GAIL Assistive Technologies enabled ===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).  * Gnome 2.xIf you experience similar problems try going into {{man menu|System -> Preferences -> Assistive Technologies}}, '''unchecking''' ''Enable assistive technologies''.* Ubuntu 12.04 LTSIf you experience similar problems try going into {{man menu|System Settings -> Keyboard -> Universal Access}},'''Disable''' all assistive technologies. Then logging out and in again. You can also try this into a console: $ sudo gedit /etc/gconf/gconf.xml.mandatory/%gconf-tree.xmlor sudo gedit /var/lib/gconf/./%gconf-tree.xmlor $ sudo gedit /etc/gdm3/greeter.gconf-defaultsor $ sudo gedit .gconf/desktop/gnome/accessibility/keyboard/%gconf.xmlLocate this part: <dir name="accessibility"> <dir name="keyboard"> <entry name="enable" ... type="bool" value="true"/> </dir>and set ''enable'' to '''false'''. ====See also====* Gramps bug {{bug|3069}} CLOSED: GtkTreeView is very slow / crashes with Assistive Technologies / ATK / a11y enabled* [http://wwwbugzilla.gnome.org/show_bug.grampscgi?id=577098 GNOME Bug 577098 - GtkTreeView (lists, Nautilus) is very slow with Assistive Technologies enabled (at-projectspi)], Status: UNCONFIRMED* [http://bugzilla.gnome.org/bugsshow_bug.cgi?id=571596 GNOME Bug 571596 - GTK_MODULES=gail:atk-bridge slows down incredibly TreeStore in pygtk ], Status: RESOLVED / DUPLICATE of 577098* [http://bugzilla.gnome.org/viewshow_bug.phpcgi?id=587020 GNOME Bug 587020 - GtkTreeView crawls with a11y enabled], Status: RESOLVED / Resolution: DUPLICATE of 577098 ===No horizontal scrollbars=== * Gtk+3 bug from versions 3.8 to 3.10.6 ==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:  #may want to fiddle with cachesize also #set_cachesize 0 200000000 2 set_lk_max_locks 300000 set_lk_max_objects 300000  See bug report below. '''See also'''* Gramps bugs {{bug|2686 GRAMPS Bug }}: crashed importing d03 stress test database, and workarounds ==Data == === Gramps and AttributeError === This message is often related to your data into your FamilyTree.See [[AttributeError:_NoneType_object_has_no_attribute|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. The [http://en.wikipedia.org/wiki/Unicode_Specials#Replacement_character replacement character] will be often a "�" (black diamond with a white question mark). You can try to fix the filename by setting the correct character. Now you will be able to import this file into Gramps ! ==Reports == === Gramps cannot display some characters into reports === RTF (''C style escape'') and LaTeX (''latin1'') file format backends on output not initially designed for a unicode support. It is possible to get strange non-ASCII character handling when using these formats. It could be very specific, because it has been tested and improved since many versions, but still possible. * {{bug|3802}} relationship graph URL's not working with PDF format ==== See also ====* (resolved) {{bug|6883}} non-Western fonts broken in PS reports* (resolved) {{bug|6884}} RTF reports backend seems to be non-UTF-aware, breaks non-Western text   =See also=* [[Known issues]]* [[Common problems]]* [[Font troubleshooting]]* [[Gramps and Windows]]
[[Category:Troubleshooting]]
[[Category:Developers/Quality Assurance]]

Navigation menu