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 <johnyilawre...@gmail.com> 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 <johnyil...@gmail.com> 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, <johnyil...@gmail.com> 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 mnemosyne-proj-u...@googlegroups.com. >> >>> 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 mnemosyne-proj-u...@googlegroups.com. >> > 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 mnemosyne-proj-users+unsubscr...@googlegroups.com. > 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 mnemosyne-proj-users+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/mnemosyne-proj-users/CAMdxoPGdM7KMquKvsu2YBnLowp1%3DPa%3DWrGQOBY2TOXf%3D5tWSog%40mail.gmail.com.