FTV v0.1.168 (i.e. current version) crashes Gramps v6.0.6 on Windows

Help
1

Subject line says it all really.

Gramps v 6.0.6 installs and tuns on Windows without error until I select FTV as the chart view. When I do that, Gramps crashes completely. There is no error message.

When I reopen Gramps, I get a ‘db is locked’ message but if I break that lock Gramps again crashes, since it’s trying to activate the FTV chart view. I have to delete the locked tree and then ensure FTV is not selected before Gramps will reopen / be usable again.

@ztlxltl please can you look at this?

2

The other way you could have tried is to change the gramps.ini so that the FTV charts view isn’t the default view.

Then you should be able to break the lock and open the tree.

You are likely to still have a problem if you switch to FTV. But you do not have to delete the tree and you can do a backup.

(Opening in safe mode from the command line would be similar. Safe Mode does not load the addons either.)

3

There is a chance this is related to a recent fix. Could you tell me,

  1. When you installed 6.0.6, which version did you have installed previously?
  2. Did you uninstall the previous version before you installed 6.0.6?

Also, is it safe to assume that the functionality you were trying worked properly in the previous version you had installed?

Thanks.

4

There is also an issue on Github and I’m already investigating.
I’m having trouble identifying the cause of the crash. It seems like that it’s (once again) related to Pango. Any additional information would be appreciated.
As a workaround, avoid opening the panel and deactivate all badges. This should prevent the crash.

1 Like
5
  1. Previously had v6.0.5 installed v6.0.6
  2. No, but I did uninstall it immediately after the v6.0.6 installer had completed but before I first opened v6.0.6
  3. Yes, FTV works fine with v6.0.5.
2 Likes
6

Yes the issue on Github sounds just like what I see but I don’t see any error message but since I never run Gramps via the console that’s not surprising. I’ll try to do that and if I get any new details I’ll post back.

1 Like
7

I knew there would be a less nuclear option to get Gramps to reopen but in my case deleting the tree was not fatal. This is a secondary version of my tree and I already frequently delete it and reimport a fresh copy from my primary installation.

The fact it is a secondary version is also why I did the v6.0.5 to v6.0.6 update on this installation first. If it went wrong (which it did) my primary copy would still be safe (which it is).

1 Like
8

This crash seems to be related to an issue which was reported in July on Fedora, see #60, #61, bug report 13920 and the forum discussion starting here.

The fix for Fedora doesn’t seem to work, as no TypeError is raised. I just released an update, v0.1.169, which always uses my fallback implementation of Pango.extents_to_pixels(). Please report back if the latest version works for you.

2 Likes
9

This new update fixes the crash for me, i.e FTV v0.1.169 works as expected in Gramps v6.0.6 on Win 11 (v24H2 build 26100.6899)

(FTV 0.1.169 also works as expected in Gramps v6.0.5)

2 Likes
10

Basic test with 1.169 and Gramps 6.0.6 - no crash after restarting Gramps following addon update.

3 Likes
11

Great! Although the workaround with my reimplementation of the problematic Pango function works, the underlying issue of Pango remains and could affect other Gramps addons.
Please let me know if you become aware of any updates regarding the upstream bug.

I would also like to appreciate the fact that two people noticed and reported this problem (in this forum thread and on GitHub) within the first few hours after the new Gramps AIO with the critical new Pango version was uploaded, and that multiple other users helped to resolve the issue quickly. This not only shows me that many people regularly use the FTV addon, but also that the Gramps community is really supportive. Thank you!

2 Likes
12

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.