Crash when adding a citation to a marriage event

Gramps v6.0.7 Win 11Pro

I thought I had a Mantis account but when I tried to login I couldn’t find any login details [Admin: details sent privately.], hence reporting this here. Gramps crashed when adding a citation to a marriage event and generated the dump below but I can’t reliably recreate this crash.

User Information:

Error Details:

463366: WARNING: imagethumb.py: line 99: Error scaling image down: Unable to marshal str as an array, use .encode() to convert to bytes
501621: WARNING: imagethumb.py: line 99: Error scaling image down: Unable to marshal str as an array, use .encode() to convert to bytes
528006: WARNING: imagethumb.py: line 99: Error scaling image down: Unable to marshal str as an array, use .encode() to convert to bytes
990956: WARNING: imagethumb.py: line 99: Error scaling image down: Unable to marshal str as an array, use .encode() to convert to bytes
1192915: ERROR: grampsapp.py: line 188: Unhandled exception
Traceback (most recent call last):
  File "C:\Program Files\GrampsAIO64-6.0.7\gramps\gui\widgets\persistenttreeview.py", line 90, in save_column_info
    if self.config_name == "undefined":
       ^^^^^^^^^^^^^^^^
AttributeError: 'PersistentTreeView' object has no attribute 'config_name'. Did you mean: 'set_config_name'?

System Information:

Gramps version: AIO64-6.0.7–1
Python version: 3.14.3
BSDDB version: not found
sqlite version: 3.52.0
orjson version: 3.11.7
LANG: en_GB.UTF-8
OS: Windows

GTK version : 3.24.51
gobject version: 3.56.1
cairo version : (1, 29, 0)

There were two bugs:

  1. Fix AttributeError on config_name when PersistentTreeView is GtkBuilder-created by dsblank · Pull Request #2205 · gramps-project/gramps · GitHub - the crash
  2. Fix imagethumb savev() passing strings instead of lists for array args by dsblank · Pull Request #2204 · gramps-project/gramps · GitHub - the warning

The crash was caused by something that we will catch in development as we use more modern testing methods.

OK.

Presumably the links you give to GitHub mean I don’t need to create a Mantis bug report now? I could do that now thanks to @gramps-project who helped me to login to Mantis again.

That is correct. The links are to github “Pull Requests” (requests to add these changes to Gramps). When they are accepted, they will be “merged” with Gramps code and will appear in the next version of Gramps.

We should ask @Nick-Hall if a reference MantisBT issue needs to be generated to link the solution to the problem report? That might be needed for the change log

Yes, each bug fix should really have a corresponding MantisBT issue.

So has someone added this to MantisBT, or is that for me to do?

User Pellog filed bug 14159 today.