Processed: Re: Bug#1073176: gramps: Error with loss of data: TypeError: '<' not supported between instances of 'str' and 'NoneType'
Processing control commands: > tag -1 unreproducible Bug #1073176 [gramps] gramps: Error with loss of data: TypeError: '<' not supported between instances of 'str' and 'NoneType' Added tag(s) unreproducible. > severity -1 normal Bug #1073176 [gramps] gramps: Error with loss of data: TypeError: '<' not supported between instances of 'str' and 'NoneType' Severity set to 'normal' from 'grave' -- 1073176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1073176: gramps: Error with loss of data: TypeError: '<' not supported between instances of 'str' and 'NoneType'
control: tag -1 unreproducible control: severity -1 normal On Fri, 14 Jun 2024 19:39:23 +1200 Mark Robinson 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
Bug#1073176: gramps: Error with loss of data: TypeError: '<' not supported between instances of 'str' and 'NoneType'
On 14/06/24 19:02, IOhannes m zmölnig (Debian/GNU) wrote: On 14/06/2024 05:59, Mark Robinson wrote: Package: gramps Version: 5.2.2+dfsg-0.1 Severity: grave Justification: causes non-serious data loss bummer. New version of gramps in Trixie upgrade. Insisted on upgrading database advising to create backup without means. the latter would be an upstream bug. Most likely, but a Debian upgrade which takes the system into a state which requires a database upgrade while removing the ability to make a backup may justify a Debian News entry so users can back out of the software upgrade and perform the backup. Upgraded and loaded database. Spat error, lost new record. could you get into detail with the last bit? - when was the new record created? - how was it lost? 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. This information appears to have been lost in submitting the report: User Information: === Just after version upgrade and DB conversion. Being unable to backup a database after upgrading Gramps and before converting the database is highly problematic. Error Details: === 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 15060: 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-08.zip 15068: WARNING: updatecallback.py: line 94: UpdateCallback with total == 0 created 3905173: ERROR: grampsapp.py: line 188: Unhandled exception Traceback (most recent call last): File "/usr/lib/python3/dist-packages/gramps/gui/editors/editperson.py", line 984, in save self.db.commit_person(self.obj, trans) File "/usr/lib/python3/dist-packages/gramps/gen/db/generic.py", line 1911, in commit_person self.add_to_surname_list(person, trans.batch) File "/usr/lib/python3/dist-packages/gramps/gen/db/generic.py", line 2450, in add_to_surname_list i = bisect.bisect(self.surname_list, name) ^^ TypeError: '<' not supported between instances of 'str' and 'NoneType' System Information: === Gramps version: 5.2.2 Python version: 3.11.9 BSDDB version: 6.2.9 (5, 3, 28) sqlite version: 3.46.0 (2.6.0) LANG: en_GB.UTF-8 OS: Linux Distribution: 6.7.12-amd64 GTK version: 3.24.42 gobject version: 3.48.2 cairo version : (1, 26, 0) Ta, Mark
Bug#1073176: gramps: Error with loss of data: TypeError: '<' not supported between instances of 'str' and 'NoneType'
On 14/06/2024 05:59, Mark Robinson wrote: Package: gramps Version: 5.2.2+dfsg-0.1 Severity: grave Justification: causes non-serious data loss bummer. Dear Maintainer, New version of gramps in Trixie upgrade. Insisted on upgrading database advising to create backup without means. the latter would be an upstream bug. Upgraded and loaded database. Spat error, lost new record. could you get into detail with the last bit? - when was the new record created? - how was it lost? i would expect that either the db migration fails (in which case records might get lost, but regardless of being "new" or not). or the db migration succeeds, and then everything should work™ (if it doesn't then it should also not work with a completely new db - and gramps would be seriously broken) gmdsar IOhannes
Bug#1073176: gramps: Error with loss of data: TypeError: '<' not supported between instances of 'str' and 'NoneType'
Package: gramps Version: 5.2.2+dfsg-0.1 Severity: grave Justification: causes non-serious data loss Dear Maintainer, New version of gramps in Trixie upgrade. Insisted on upgrading database advising to create backup without means. Upgraded and loaded database. Spat error, lost new record. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.12-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gramps depends on: ii gir1.2-gtk-3.03.24.42-1 ii librsvg2-22.58.0+dfsg-1 ii python3 3.11.8-1 ii python3-bsddb36.2.9-2+b6 ii python3-gi3.48.2-1 ii python3-gi-cairo 3.48.2-1 ii xdg-utils 1.1.3-4.1 Versions of packages gramps recommends: ii gir1.2-geocodeglib-2.0 3.26.3-6+b2 ii gir1.2-gexiv2-0.10 0.14.2-2+b2 ii gir1.2-osmgpsmap-1.01.2.0-2+b2 ii graphviz2.42.2-9+b1 ii python3-icu 2.13.1-1 Versions of packages gramps suggests: ii fonts-freefont-ttf20211204+svn4273-2 pn gir1.2-goocanvas-2.0 pn gir1.2-gtkspell3-3.0 ii python3-numpy 1:1.26.4+ds-10 ii python3-pil 10.3.0-2 pn rcs -- no debconf information
