[Linux Slackware] Segfault after pygobject-3.55.1 upgrade (Reverting to pygobject-3.55.0 fixes it)

Gramps-6.0.6 on Linux Slackware -current, package created from gramps-6.0.6.zip

After upgrading pygobject-3.55.0 > 3.55.1 Gramps starts OK but as soon as I try to change anything, e.g. adding a birth date, it crashes with a generic ‘segfault’.

Anyone else experiencing the same?

Reverted to pygobject-3.55.0 and all is well.

Have you reported the issue to Slackware if so can you link to the issue report please?

reported upstream:

Slackware has for now reverted to 3.55.0, from yesterday’s changelog:

pygobject3-3.55.0-x86_64-1.txz:  Upgraded.
Reverted, as 3.55.1 is causing segfaults.
Unless there's a good reason, we'll probably wait for 3.56.0.
2 Likes

Fixed by the pygobject devs, so next version3.55.2 should be OK. I just compiled and upgraded pygobject from latest git, and no more segfaults

2 Likes

Spoke too soon, turned out that this wasn’t fixed after all…
Even if I did a quick test with the latest version - opening Gramps, editing a post, all OK - I now noticed that even if the first edit went OK, the second gave a segfault. So back to 3.55.0 for now…
pygobject devs are notified.

1 Like

The segfault issue has been solved by the pygobject devs. I’ve tested pygobject built from latest git: made a sequence of edits, made reports with various settings and so on, without hiccups. So the next release should hopefully work. Till then, gramps users had better avoid versions 3.55.1 and 3.55.2.

5 Likes

Thanks @hamkg! PyGObject devs have made a note that Gramps may need to follow-up on.

1 Like

Have forgotten to mention that the fix is included in pygobject-3.55.3 released a week ago.

3 Likes

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