Difference between revisions of "Known issues"
m (→GRAMPS cannot import media with non-ASCII characters on filename) |
m (→GRAMPS cannot import media with non-ASCII characters on filename) |
||
| Line 21: | Line 21: | ||
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. | ||
| − | + | 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 ! | |
| − | The [http://en.wikipedia.org/wiki/Unicode_Specials#Replacement_character replacement character will be often a | ||
| − | You can try to 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 cannot set date greater than 21 == | ||
Revision as of 19:31, 21 January 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 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 runs out of locks
With a large database, GRAMPS can "run out of available locks". See bug report below.
See also
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
