Did you perhaps save your database to a different location in your drive at some point, such that the new cards are not where you thought they were?
Or did you use "Activate cards" to filter out some of your cards? For the problem with corruption, I'd recommend you upgrade, but here Devin should help a bit, since I don't have OSX... Peter On Sun, 23 Mar 2025, 04:31 John Lawrence, <[email protected]> wrote: > Thank you, Devin! > > That worked for getting my copy of Mnemosyne to open again. However, when > I try to open or import any of the recent backup files from before the > corruption set in, Mnemosyne opens or imports them, but no cards that were > added post-2020 appear! > > Presumably, the problem is either (a) for some reason, when the .db files > supposedly backed up, they didn't save any of the post-2020 cards and those > cards are gone; (b) those cards are there in the .db, but Mnemosyne doesn't > recognize them / is refusing to add them to the new deck. > > The fastest way would be if I could (non-publicly) send you the .db file > to look at, to see if you can see post-2020 cards in the file, and we'll > then know whether it's (a) or (b). > > If you're not comfortable with that (since that would have to be done off > the message board), I can just try following further instructions from you > to fix the issue I'm having with getting the newest version installed, in > the hopes that that solves things. I just don't want to put you the trouble > of another back-and-forth (especially since you've both already been very > generous in responding to all of these problems), only to discover that it > was (a) all along, and we wasted our time on the install. > > John Lawrence > > On Saturday, March 22, 2025 at 5:11:51 PM UTC-4 Devin Howard wrote: > >> Hi John >> >> If you have a potentially working backup, but you aren't able to open >> Mnemosyne to use it, you could try deleting or moving the Mnemosyne folder >> on your computer (which holds the current copy of the database, the >> likely-corrupted one). There's some detail about this on >> https://mnemosyne-proj.org/help/backups.php. If you want to try clearing >> the existing data, you can do this in Terminal or in Finder >> >> In Terminal: type "mv ~/Library/Mnemosyne ~/Desktop/Mnemosyne-corrupted" >> and hit Enter >> >> In Finder: Use the "Go" menu or Shift+Cmd+L to open your Library folder. >> Scroll through the folders to find the Mnemosyne folder and drag it out of >> that folder on to your Desktop. >> >> (it doesn't have to be your desktop - you can move it anywhere) >> >> Once you've done this, your Mnemosyne should behave as if it's freshly >> installed, and should allow you to attempt to restore from backup. Hope it >> works! >> >> On Thu, Mar 20, 2025 at 12:51 AM Peter Bienstman <[email protected]> >> wrote: >> >>> I don't have experience with Mac's myself, so I'm putting Devin, our >>> OSX developer, in CC. >>> >>> Cheers, >>> >>> Peter >>> >>> On Wed, Mar 19, 2025 at 8:38 PM John Lawrence <[email protected]> >>> wrote: >>> > >>> > Thanks, Peter, but I tried that too. >>> > >>> > I downloaded Python expressly for that purpose. (I've not used it >>> before.) And I was able to get Mnemosyne-updater.command and >>> Mnemosyne.command script icons in my Applications. When I double-clicked on >>> them, they appeared to run properly, in as much as the Terminal said: >>> > >>> > Saving session... >>> > >>> > ...copying shared history... >>> > >>> > ...saving history...truncating history files... >>> > >>> > ...completed. >>> > >>> > >>> > [Process completed] >>> > >>> > >>> > But I'm not aware of anything further that either script did, as no >>> installation began. >>> > >>> > >>> > (I tried this on both computers.) >>> > >>> > >>> > John >>> > >>> > >>> > On Wednesday, March 19, 2025 at 2:52:05 PM UTC-4 Peter Bienstman wrote: >>> >> >>> >> I noticed you are running quite an old version of Mnemosyne. You >>> >> should definitely try upgrading to the latest version 2.11. Thinking >>> >> about this a bit more, I have vague memories of fixing a bug like this >>> >> in the distant past... >>> >> >>> >> Peter >>> >> >>> >> On Wed, Mar 19, 2025 at 7:47 PM John Lawrence <[email protected]> >>> wrote: >>> >> > >>> >> > Thanks for the swift reply, Peter! >>> >> > >>> >> > My initial instinct was that the database was corrupted, as you've >>> suggested. But when that has happened to me once before, I was able to fix >>> that by merely restoring an older version of the database, from before the >>> corruption set in. In this case, when I restore the recent versions that >>> were working perfectly a few days ago, that makes no difference. Going even >>> further back in time (e.g. to the update from last month) makes no >>> difference. >>> >> > >>> >> > Also, while I do have some of the backups you're referring to >>> (although they are, alas, six years old), those aren't of any use to me >>> because I can't even reach the stage where I have a choice of which .db >>> files to use. I get this message the moment I click Mnemosyne to open it up >>> on this computer. >>> >> > >>> >> > I have another copy of Mnemosyne on a different computer. Its deck >>> hasn't been updated since 10/03/2020. It's still functional. However, when >>> I tell it to import any newer database (not just from this year, from any >>> time after 2020), it claims that it's importing those new cards and merging >>> the log data and so forth. And then when it's done, and I check the deck, >>> it didn't upload a single new card from the newer database. I tried this >>> again by installing a new copy of Mnemosyne on that computer, and once >>> again trying to import any post-2020.db that I have. No matter what, it >>> shows only the cards from 2020 or earlier. >>> >> > >>> >> > John >>> >> > >>> >> > On Wednesday, March 19, 2025 at 12:19:35 PM UTC-4 Peter Bienstman >>> wrote: >>> >> >> >>> >> >> I'm afraid your database got corrupted somehow. If you put your >>> database on a network drive or on Dropbox, that could happen if two >>> programs try to access the database at the same time. You could also have a >>> failing harddrive. >>> >> >> >>> >> >> Do you have other backups outside of Dropbox? >>> >> >> >>> >> >> You could also try the backups Mnemosyne creates itself: >>> https://mnemosyne-proj.org/help/backups.php >>> >> >> >>> >> >> Good luck! >>> >> >> >>> >> >> Peter >>> >> >> >>> >> >> On Wed, 19 Mar 2025, 17:15 John Lawrence, <[email protected]> >>> wrote: >>> >> >>> >>> >> >>> My copy of Mnemosyne was working normally as of two days ago. But >>> starting yesterday, it displays the follow message every time I try to open >>> it: >>> >> >>> >>> >> >>> An unexpected error has occurred. >>> >> >>> >>> >> >>> Please forward the following info to the developers: >>> >> >>> >>> >> >>> >>> >> >>> Traceback (innermost last): >>> >> >>> >>> >> >>> File "mnemosyne/pyqt_ui/mnemosyne", line 279, in <module> >>> >> >>> >>> >> >>> File "mnemosyne/libmnemosyne/__init__.py", line 444, in initialise >>> >> >>> >>> >> >>> File "mnemosyne/libmnemosyne/__init__.py", line 435, in initialise >>> >> >>> >>> >> >>> File "mnemosyne/libmnemosyne/loggers/database_logger.py", line >>> 26, in started_program >>> >> >>> >>> >> >>> File "mnemosyne/libmnemosyne/databases/SQLite_logging.py", line >>> 32, in log_started_program >>> >> >>> >>> >> >>> File "mnemosyne/libmnemosyne/databases/_sqlite3.py", line 77, in >>> execute >>> >> >>> >>> >> >>> mnemosyne.libmnemosyne.utils.MnemosyneError: SQL error: insert >>> into log(event_type, timestamp, object_id) values(?,?,?) (1, 1742400090, >>> 'Mnemosyne 2.7.3 posix darwin TZ -4') >>> >> >>> >>> >> >>> >>> >> >>> Traceback (innermost last): >>> >> >>> >>> >> >>> File "mnemosyne/libmnemosyne/databases/_sqlite3.py", line 74, in >>> execute >>> >> >>> >>> >> >>> sqlite3.DatabaseError: database disk image is malformed >>> >> >>> >>> >> >>> >>> >> >>> I've tried downloading and installing another copy of Mnesmoyne, >>> but that didn't work. The new copy says this: >>> >> >>> >>> >> >>> An unexpected error has occurred. >>> >> >>> >>> >> >>> Please forward the following info to the developers: >>> >> >>> >>> >> >>> >>> >> >>> Traceback (innermost last): >>> >> >>> >>> >> >>> File "mnemosyne/pyqt_ui/mnemosyne", line 270, in <module> >>> >> >>> >>> >> >>> File "mnemosyne/libmnemosyne/__init__.py", line 441, in initialise >>> >> >>> >>> >> >>> File "mnemosyne/libmnemosyne/__init__.py", line 432, in initialise >>> >> >>> >>> >> >>> File "mnemosyne/libmnemosyne/loggers/database_logger.py", line >>> 26, in started_program >>> >> >>> >>> >> >>> File "mnemosyne/libmnemosyne/databases/SQLite_logging.py", line >>> 32, in log_started_program >>> >> >>> >>> >> >>> File "mnemosyne/libmnemosyne/databases/_sqlite3.py", line 72, in >>> execute >>> >> >>> >>> >> >>> sqlite3.DatabaseError: database disk image is malformed >>> >> >>> >>> >> >>> >>> >> >>> I also tried restoring the .db files (using Dropbox) to older >>> versions that were working fine last week. That didn't work either. >>> >> >>> >>> >> >>> What should I do to fix this problem? >>> >> >>> >>> >> >>> (I'm working on Mac OS 12.5, in case that's necessary >>> information.) >>> >> >>> >>> >> >>> Thanks. >>> >> >>> >>> >> >>> -- >>> >> >>> You received this message because you are subscribed to the >>> Google Groups "mnemosyne-proj-users" group. >>> >> >>> To unsubscribe from this group and stop receiving emails from it, >>> send an email to [email protected]. >>> >> >>> To view this discussion visit >>> https://groups.google.com/d/msgid/mnemosyne-proj-users/5753f36a-9751-4f8f-8c6e-9534402db42cn%40googlegroups.com >>> . >>> >> > >>> >> > -- >>> >> > You received this message because you are subscribed to the Google >>> Groups "mnemosyne-proj-users" group. >>> >> > To unsubscribe from this group and stop receiving emails from it, >>> send an email to [email protected]. >>> >> > To view this discussion visit >>> https://groups.google.com/d/msgid/mnemosyne-proj-users/d3d5080b-d8ed-47b5-a180-2e2503f9baa5n%40googlegroups.com >>> . >>> > >>> > -- >>> > You received this message because you are subscribed to the Google >>> Groups "mnemosyne-proj-users" group. >>> > To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> > To view this discussion visit >>> https://groups.google.com/d/msgid/mnemosyne-proj-users/ca2e1465-301c-4d32-a244-7305005bf2d8n%40googlegroups.com >>> . >>> >> -- > You received this message because you are subscribed to the Google Groups > "mnemosyne-proj-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion visit > https://groups.google.com/d/msgid/mnemosyne-proj-users/edacdbdc-8b2d-4066-bee8-af969f6fc3a7n%40googlegroups.com > <https://groups.google.com/d/msgid/mnemosyne-proj-users/edacdbdc-8b2d-4066-bee8-af969f6fc3a7n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/mnemosyne-proj-users/CAMdxoPGLt10c5Qtt74ZUqhp9vyn_xWffh6AdQfxw8YSvKhM4cw%40mail.gmail.com.
