Difference between revisions of "Known issues"
(add troubleshooting category) |
|||
Line 1: | Line 1: | ||
− | = | + | = GRAMPS Freezes and crashes = |
There have been multiple reports of long freezes and crashes of GRAMPS when refreshing the people view, e.g. after editing a person or changing the Name Display Format. They seem to be related to the use of GNOME Assistive Technologies. If you experience similar problems try going into System -> Preferences -> Assistive Technologies, unchecking "Enable assistive technologies" and logging out and in again. | There have been multiple reports of long freezes and crashes of GRAMPS when refreshing the people view, e.g. after editing a person or changing the Name Display Format. They seem to be related to the use of GNOME Assistive Technologies. If you experience similar problems try going into System -> Preferences -> Assistive Technologies, unchecking "Enable assistive technologies" and logging out and in again. | ||
− | + | == See also == | |
* [http://bugzilla.gnome.org/show_bug.cgi?id=571596 GNOME Bug] | * [http://bugzilla.gnome.org/show_bug.cgi?id=571596 GNOME Bug] | ||
+ | |||
+ | = GRAMPS runs out of locks = | ||
+ | |||
+ | With a large database, GRAMPS can "run out of available locks". See bug report below. | ||
+ | |||
+ | == See also == | ||
+ | |||
+ | * [http://www.gramps-project.org/bugs/view.php?id=2686 GRAMPS Bug and workarounds] | ||
[[Category:Troubleshooting]] | [[Category:Troubleshooting]] |
Revision as of 12:38, 12 April 2009
GRAMPS Freezes and crashes
There have been multiple reports of long freezes and crashes of GRAMPS when refreshing the people view, e.g. after editing a person or changing the Name Display Format. They seem to be related to the use of GNOME Assistive Technologies. 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 runs out of locks
With a large database, GRAMPS can "run out of available locks". See bug report below.