16,602
edits
Changes
m
[[Category:Troubleshooting]]==Data ==
no edit summary
{{languages}}
== GRAMPS freezes Dependencies=====Gramps and crashes with ATK / GNOME Assistive Technologies enabled some Gtk versions===There have been multiple reports of long freezes and crashes of GRAMPS when refreshing * Some Gtk versions seem not to properly refresh the GUI (need to use the people or place tree viewmouse cursor), esee bug {{bug|4863}}.g* Some Gtk versions have a refresh issue on Citation TreeView (3.4. x) after editing a person or changing the Name Display Formatan edition, see bug {{bug|5688}}.* Incremental search and synchronization with typed letters, see bug {{bug|1450}}. They are related to the use of GNOME Assistive Technologies * New row/line on Census gramplet (ATKaddon), see bug [http:/GAIL)/www. If you experience similar problems try going into System gramps-> Preferences -> Assistive Technologies, unchecking "Enable assistive technologies" and logging out and in againproject.org/bugs/view.php?id=5688#c24063 5688].
===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}},'''See Disable''' all assistive technologies. Then logging out and in again. You can alsotry 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 Gramps bug {{bug|3069}}: GtkTreeView is very slow / crashes with Assistive Technologies / ATK / a11y enabled
* [http://bugzilla.gnome.org/show_bug.cgi?id=577098 GNOME Bug 577098 - GtkTreeView (lists, Nautilus) is very slow with Assistive Technologies enabled (at-spi)], Status: UNCONFIRMED
* [http://bugzilla.gnome.org/show_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/show_bug.cgi?id=587020 GNOME Bug 587020 - GtkTreeView crawls with a11y enabled], Status: RESOLVED / Resolution: DUPLICATE of 577098
== GRAMPS Database == === Gramps runs out of locks ===With a large database, GRAMPS 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 Gramps bugs {{bug|2686}}: crashed importing d03 stress test database], and workarounds
=== Gramps and AttributeError ===
This message is often related to your data into your FamilyTree.
See [[AttributeError:_NoneType_object_has_no_attribute|AttributeError]]
== GRAMPS 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.
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 set date greater than 21 Reports ==
=== Gramps cannot display some characters into reports === RTF (''C style escape''), Postscript (''latin1''), LaTex (''latin1'') file formats on output are not designed for an unicode support.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. ==Edition== === Gramps cannot set date greater than 21 === Gramps-3.0.4 under Jaunty 9.04 cannot uses date editor or media reference editor. [[Installation#Upgrading_GRAMPSUpgrading_Gramps|Upgrading]] to [[Installation#Ubuntu_and_derivatives|3.1.2]] fixes this issues.
'''See also'''
* [https://bugs.launchpad.net/ubuntu/+source/gramps/+bug/387665 GNOME bug]
[[Category:Troubleshooting]]
[[Category:Developers/Quality Assurance]]
