For me (on Win11/Gramps 5.2.2) Card View crashes Gramps frequently. Is it something with my install, or is this a common problem?
Do you see or can you provide the crash message? You might have to start Gramps using the GrampsAIO64 5.2.2-console shortcut.
There is no message. Gramps freezes after switching view either way, but only occasionally, say every 10th switch or so, but no pattern found. Database is locked after restart of Gramps.
Ok does Cardview work when used with either a new blank empty family tree or evenbetter if you can confirm the issue happens using the Example.gramps testing family tree please?
Also what version of the Cardview addon are you using as current version is â0.2024.04241â?
Thanks, will test and revert next week.
Is this related to the preferences bug reported in the CardView issue in @cdhorn GitHub repository?
If so, there is a patch posted there.
- Same thing happens when I test with the Example.gramps
- Yes, Iâm using the current version â0.2024.04241â
- This CardView version seems to have pointers to Gramps 5.2 in the .gpr.py files, so I guess that is not the problem. Unfortunately I have no idea what to do with the patch suggested in the thread above.
The issue is hard to pinpoint, as it happens seemingly at random, but about every 10-20th time I navigate in the view, or switch back/to CardView.
The console shows the folowing error:
Warning: DbState: Exception occurred in callback function.
Traceback (most recent call last):
File âC:\Program Files\GrampsAIO64-5.2.2\gramps\gen\utils\callback.pyâ, line 424, in emit
fn(*args)
File âC:\Program Files\GrampsAIO64-5.2.2\gramps\gui\displaystate.pyâ, line 611, in db_changed
self.clear_history()
File âC:\Users\marku\AppData\Roaming\gramps\gramps52\plugins\RestoreHist\restorehist.pyâ, line 52, in clear_history
history.mru = hist[history.nav_type]
~~~~^^^^^^^^^^^^^^^^^^
KeyError: âTagâ
Well this error is for the third party Restore History addon that I donât use, so please raise a separate issue on the bug tracker.
The user manual briefly mentions the following advice for the addon:
You can use the third party RestoreHist addon
So that a portion of the Go menu can be made to persist between restarts of Gramps. If installed then you can manually clear the stored state by finding and deleting /gramps52/plugins/RestoreHist/hist_save.ini file from the user folder (the ~.gramps folder or %Appdata% folder in Windows).
Well⌠the âRestore Historyâ (or âRestart where you were last workingâ as itâs called in the Addon & Plugin Manager) is maybe not the (only) culprit. I uninstalled it, restarted Gramps, and still Gramps crashed when clicking around in Cardview. The console showed no errors, just a list of rendered pages.
I found a way to replicate the crash: when moving between my first known paternal ancestor (A) and his son (B) it crashed. So, to test, I deleted A from the db, restarted Gramps and selected B in the person view, switched to CardView and -Crash. No error in the console. This caused the database to be unusable; I broke the lock, but the file didnât load, and Gamps hung. Well, no worries, I have backups, and -it seems- the problem went away when I switched to a backup. I can only hope it remains awayâŚ
I then re-installed the âRestart where you were last workingâ and it seems to be working fine. I guess some sort of database corruption must have occurred. Go figure.
Many thanks for your help, fantastic community here!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.