What's probably happening here is that you have two installations of Mnemosyne on the same system: one on the hard drive and another one on the usb key.
Be sure to have only one, and follow the instructions on how to start Mnemosyne from the USB key exactly as they are written on the website. Peter On Tuesday 24 February 2009 18:47:12 Frank wrote: > On Feb 24, 5:56?pm, Peter Bienstman <[email protected]> wrote: > > On Tuesday 24 February 2009 17:20:04 Frank wrote: > > > So I basically have two questions: > > > - Can anyone confirm this is a problem of differing python versions? > > > > That is indeed the problem. > > Apparently, there's something more to it. Looks like I've messed up > something else. > > I've just had mnemosyne working fine on a python2.4 installation from > my usb stick. After trying the same usb stick on another system with > another python2.4 installation mnemosyne starts with "Unable to load > database. Creating tmp file." > > And worst of all: the creation of said tmp file fails with > ... > File "/usr/lib/python2.4/site-packages/Mnemosyne-1.2-py2.4.egg/ > mnemosyne/core/mnemosyne_core.py", line 977, in new_database > save_database(contract_path(path, basedir)) > File "/usr/lib/python2.4/site-packages/Mnemosyne-1.2-py2.4.egg/ > mnemosyne/core/mnemosyne_core.py", line 1094, in save_database > raise SaveError() > > The log.txt file is pretty much useless: > > 2009-02-24 18:35:52 : Program started : Mnemosyne 1.2 posix linux2 > 2009-02-24 18:38:07 : New database > > and nothing more. I sure hope that error messages get improved for > 2.0, because I have absolutely no clue what's going wrong and where. > > I do have full write access to the directory and manual creation of > files is no problem. There's enough free space as well, so I don't > know what's the problem. > > > Now what's even stranger is my "solution" to this problem: > > Starting mnemosyne from the ~/.mnemosyne directory with > $ mnemosyne default.mem > actually starts up mnemosyne and correctly loads my database. Even > more so, it kind of 'repairs' the database, as after that I can > normally start mnemosyne using the default directory and it works. > > > Anyone minds shedding some light on what's going on here? > > > Frank > ------------------------------------------------ Peter Bienstman Ghent University, Dept. of Information Technology Sint-Pietersnieuwstraat 41, B-9000 Gent, Belgium tel: +32 9 264 34 46, fax: +32 9 264 35 93 WWW: http://photonics.intec.UGent.be email: [email protected] ------------------------------------------------ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/mnemosyne-proj-users?hl=en -~----------~----~----~----~------~----~------~--~---
