Difference between revisions of "Known issues"
m (→GRAMPS freezes and crashes with ATK / GNOME Assistive Technologies enabled) |
m |
||
| Line 16: | Line 16: | ||
[[Category:Troubleshooting]] | [[Category:Troubleshooting]] | ||
| + | |||
| + | == Gramps and AttributeError == | ||
| + | |||
| + | This message is often related to your data into your FamilyTree. | ||
| + | See [[AttributeError:_NoneType_object_has_no_attribute|AttributeError]] | ||
== GRAMPS cannot import media with non-ASCII characters on filename == | == GRAMPS cannot import media with non-ASCII characters on filename == | ||
Revision as of 09:44, 16 December 2011
 |
Languages: |
[[::Known issues|English]] |
Contents
GRAMPS freezes and crashes with ATK / GNOME 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). If you experience similar problems try going into System -> Preferences -> Assistive Technologies, unchecking "Enable assistive technologies" and logging out and in again.
See also
- GRAMPS bug 3069: GtkTreeView is very slow / crashes with Assistive Technologies / ATK / a11y enabled
- GNOME Bug 577098 - GtkTreeView (lists, Nautilus) is very slow with Assistive Technologies enabled (at-spi), Status: UNCONFIRMED
- GNOME Bug 571596 - GTK_MODULES=gail:atk-bridge slows down incredibly TreeStore in pygtk , Status: RESOLVED / DUPLICATE of 577098
- GNOME Bug 587020 - GtkTreeView crawls with a11y enabled, Status: RESOLVED / Resolution: DUPLICATE of 577098
GRAMPS runs out of locks
With a large database, GRAMPS can "run out of available locks". See bug report below.
See also
- GRAMPS bugs 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
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 !
GRAMPS cannot set date greater than 21
Gramps-3.0.4 under Jaunty 9.04 cannot uses date editor or media reference editor. Upgrading to 3.1.2 fixes this issues.
See also
