Difference between revisions of "Known issues"

From Gramps
Jump to: navigation, search
m (GRAMPS runs out of locks)
(Gramps cannot display some characters into reports: 6883, 6884 resolved)
(14 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{languages}}
 
{{languages}}
==GRAMPS and some Gtk versions==
+
==Dependencies==
 +
===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}}.
 
* Some Gtk versions seem not to properly refresh the GUI (need to use the mouse cursor), see bug {{bug|4863}}.
 
* Some Gtk versions have a refresh issue on Citation TreeView (3.4.x) after an edition, see bug {{bug|5688}}.
 
* Some Gtk versions have a refresh issue on Citation TreeView (3.4.x) after an edition, see bug {{bug|5688}}.
Line 6: Line 7:
 
* New row/line on Census gramplet (addon), see bug [http://www.gramps-project.org/bugs/view.php?id=5688#c24063 5688].
 
* New row/line on Census gramplet (addon), see bug [http://www.gramps-project.org/bugs/view.php?id=5688#c24063 5688].
  
== GRAMPS freezes and crashes with ATK / GNOME / GAIL Assistive Technologies enabled ==
+
===Gramps and some python gobject introspection versions===
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).  
+
* 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.x
 
* Gnome 2.x
Line 19: Line 23:
  
 
You can also try this into a console:
 
You can also try this into a console:
  $ sudo gedit /var/lib/gdm/.gconf.mandatory/%gconf-tree.xml
+
  $ sudo gedit /etc/gconf/gconf.xml.mandatory/%gconf-tree.xml
 +
or
 +
sudo gedit /var/lib/gconf/./%gconf-tree.xml
 +
or
 +
$ sudo gedit /etc/gdm3/greeter.gconf-defaults
 +
or
 +
$ sudo gedit .gconf/desktop/gnome/accessibility/keyboard/%gconf.xml
 
Locate this part:
 
Locate this part:
 
  <dir name="accessibility">
 
  <dir name="accessibility">
Line 27: Line 37:
 
and set ''enable'' to '''false'''.
 
and set ''enable'' to '''false'''.
  
===See also===
+
====See also====
* GRAMPS bug {{bug|3069}}: GtkTreeView is very slow / crashes with Assistive Technologies / ATK / a11y enabled
+
* 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=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=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
 
* [http://bugzilla.gnome.org/show_bug.cgi?id=587020 GNOME Bug 587020 - GtkTreeView crawls with a11y enabled], Status: RESOLVED / Resolution: DUPLICATE of 577098
  
== GRAMPS runs out of locks ==
+
==Database ==
With a large database, GRAMPS can "run out of available locks".  
+
 
 +
=== 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
 
For 140.000 people you should use: max_locks 300000 and max_objects 300000
  
Line 48: Line 60:
  
 
'''See also'''
 
'''See also'''
* GRAMPS bugs {{bug|2686}}: crashed importing d03 stress test database, and workarounds
+
* Gramps bugs {{bug|2686}}: crashed importing d03 stress test database, and workarounds
  
== Gramps and AttributeError ==
+
==Data ==
 +
 
 +
=== Gramps and AttributeError ===
  
 
This message is often related to your data into your FamilyTree.
 
This message is often related to your data into your FamilyTree.
 
See [[AttributeError:_NoneType_object_has_no_attribute|AttributeError]]
 
See [[AttributeError:_NoneType_object_has_no_attribute|AttributeError]]
  
== GRAMPS cannot import media with non-ASCII characters on filename ==
+
==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.
 
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.
Line 62: Line 78:
 
You can try to fix the filename by setting the correct character. Now you will be able to import this file into Gramps !
 
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'') 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.
 +
 
 +
==== 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
 +
 
 +
==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_GRAMPS|Upgrading]] to [[Installation#Ubuntu_and_derivatives|3.1.2]] fixes this issues.
+
Gramps-3.0.4 under Jaunty 9.04 cannot uses date editor or media reference editor. [[Installation#Upgrading_Gramps|Upgrading]] to [[Installation#Ubuntu_and_derivatives|3.1.2]] fixes this issues.
  
 
'''See also'''
 
'''See also'''
Line 70: Line 100:
  
 
[[Category:Troubleshooting]]
 
[[Category:Troubleshooting]]
 +
[[Category:Developers/Quality Assurance]]

Revision as of 23:50, 6 August 2013

Dependencies

Gramps and some Gtk versions

  • Some Gtk versions seem not to properly refresh the GUI (need to use the mouse cursor), see bug 4863.
  • Some Gtk versions have a refresh issue on Citation TreeView (3.4.x) after an edition, see bug 5688.
  • Incremental search and synchronization with typed letters, see bug 1450.
  • New row/line on Census gramplet (addon), see bug 5688.

Gramps and some python gobject introspection versions

  • pygobject < 3.4.0: : segfault on expand all nodes/rows into a Tree View, see 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.x

If you experience similar problems try going into System -> Preferences -> Assistive Technologies, unchecking Enable assistive technologies.

  • Ubuntu 12.04 LTS

If you experience similar problems try going into 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.xml

or

sudo gedit /var/lib/gconf/./%gconf-tree.xml

or

$ sudo gedit /etc/gdm3/greeter.gconf-defaults

or

$ sudo gedit .gconf/desktop/gnome/accessibility/keyboard/%gconf.xml

Locate this part:

<dir name="accessibility">
<dir name="keyboard">
   <entry name="enable" ... type="bool" value="true"/>
</dir>

and set enable to false.

See also

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 2686: 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

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 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.

See also

  • (resolved) 6883 non-Western fonts broken in PS reports
  • (resolved) 6884 RTF reports backend seems to be non-UTF-aware, breaks non-Western text

Edition

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