control: tag -1 unreproducible control: severity -1 normal
On Fri, 14 Jun 2024 19:39:23 +1200 Mark Robinson <debian-b...@zl2tod.net> wrote:
On completing the database migration I created a new person, added birth and death information including a new death location and notes, and clicked OK.This resulted in the python error referred to in the headline which left the new person with the OK button greyed out and no way to save it. The record was lost.
Hi Mark,sorry about that. I've tried to reproduce this bug, using the steps you've described above. It worked without any problem on my system, so I'm not able to reproduce the faulty behaviour of gramps.
I'm therefore lowering the severity, because otherwise gramps would be removed from testing. I currently don't think that this would be necessary.
However, there should be an automatic backup of your database, as printed in the status messages:
11723: WARNING: upgrade.py: line 2218: If upgrade and loading the Family Tree works, you can delete the zip file at /home/mark/.gramps/ROBINSON__Mark_Gregory_2024-06-14_12-07-04.zip
Could you try to extract that database version of your family tree and open it with gramps? The program should then ask you again to convert the tree to the new database format. Afterwards, could you repeat the steps above, i. e. creating a new person, adding birth and death information etc.? Then please report back if the error still occurs.
Regards, Tobias
OpenPGP_signature.asc
Description: OpenPGP digital signature
