Is it me or is anyone else getting gramps failing to run on a fully updated system with the error:
$ pacman -Qi gramps Name : gramps Version : 4.0.0-1 $ gramps ResourcePath.ERROR: Resource Path /build/pkg/gramps/usr/share is invalid
I get this error too, resource-path is wrong:
$ cat /usr/lib/python2.7/site-packages/gramps/gen/utils/resource-path /build/pkg/gramps/usr/share
Setting it to /usr/share in the file or in the environment variable doesn't fix it:
$ GRAMPS_RESOURCES=/usr/share /usr/bin/gramps No handlers could be found for logger "grampslocale" Gdk, Gtk or Pango typelib not installed. Install Gnome Introspection, and pygobject version 3.3.2 or later. Install then instrospection data for Gdk, Gtk and Pango Gramps will terminate now.
http://sourceforge.net/mailarchive/mess … d=30655143 shows that we're not the only ones with the problem, but that thread seems to be debian-centric.
I opened a bug report: https://bugs.archlinux.org/task/35444
I'm getting it to semi-work by using just the following command (no other mods or environment variables) to generate the resource-path file (as root):
echo -n /usr/share > /usr/lib/python2.7/site-packages/gramps/gen/utils/resource-path
Note the "-n". The resource-path file cannot have any whitespace (including carriage return) after the path. By doing this, gramps will start (just "gramps" at the command line), though I first get the
No handlers could be found for logger "grampslocale"
warning, followed by a series of error panels that state things like
2013-05-23 18:41:01.375: ERROR: grampsapp.py: line 114: Unhandled exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/gramps/gui/widgets/validatedmaskedentry.py", line 1174, in do_changed if self._block_changed: AttributeError: 'Entry' object has no attribute '_block_changed'
After clicking through all those, my database is open and I can navigate as usual. However, I continue to get _block_changed errors as I move around. In addition, I will say that 4.0.0 looks very raw - the UI could use a lot of spit and polish to bring it up to the usability of 3.4.4.
Linux User #353 - SLS -> Slackware -> Red Hat -> Mandrake -> Fedora -> Arch
Thanks guys, good to know I'm not alone!
I will say that 4.0.0 looks very raw - the UI could use a lot of spit and polish to bring it up to the usability of 3.4.4.
The bug got closed as 'won't fix' and gramps got downgraded to 3.4.5 (although atm 4.0.0-1 is still available).
4.0 looks unusable and needs patching
Edit: Version 1:3.4.5-1 is now (again) available.
Last edited by karol (2013-05-24 11:31:47)
Luckily I am also running gramps in Spanish from a shell script: LANG=es_PA gramps. My newly installed version 4.0 runs ok in Spanish. It will fail like reported above in English where LANG=en_US. After some trace I made with strace I copied the missing gramps.mo file from /usr/share/locale/en_GB/LC_MESSAGES/gramps.mo to /usr/share/locale-bundle/en. Its is not a valid en_US gramp.mo file but it works!... I hope to get a valid gramps.mo file somewhere soon.
Last edited by gzsuniq (2013-05-31 04:49:26)