Until I figure out what causes the hang, a reboot should fix this. I have some difficulty reproducing this, though.
Peter > -----Original Message----- > From: [email protected] [mailto:mnemosyne- > [email protected]] On Behalf Of Gnome > Sent: 14 December 2013 21:57 > To: [email protected] > Subject: Re: [mnemosyne-proj-users] Re: 2.3 test release > > It ended up in sdcard/mnemosyne. I now deleted this folder via an file > browser app to try again. However, when enabling sync and clicking OK in > mnemosyne server settings I get a message that the sync server is running, I > click OK and then mnemosyne freezes. Reviewing in web-browser is > enabled. I aslo get freeze if I try to disable the review browser, or just hit OK. > > kl. 14:31:13 UTC+1 lørdag 14. desember 2013 skrev Peter Bienstman > følgende: > > What is the location the Mnemosyne directory ended up at in the > end? > Perhaps you need to specify that directory in mnemosyne.py and try > again? > > Mnemosyne does not contain a javascrip parser to see which files > you > include in javascript. Only certain file types referenced by a src="" > tag are included in the sync protocol. The others you have to copy > manually. > > Cheers, > > Peter > > Citeren Gnome <[email protected] <javascript:> >: > > > Now I found the directory using an client file browser app, then it > > appeared with it contents also via usb. It seems like .js files are > > synched, however some files are included from a javascript file > > programmatically, these are not synched. Does it however matter if > I copy > > the directory where I have scripts manually? > > > > kl. 12:14:13 UTC+1 l�rdag 14. desember 2013 skrev Gnome > f�lgende: > >> > >> There is a mnemosyne directory sometimes appearing, it was > empty. I > >> deleted it and it preformed a successful sync. I reviewed and > graded a card > >> on the client. Then clicked 'exit'. Then I where asked to preform a > sync. > >> It said "sync finished!". Then there was a message asking if I > wanted to > >> close the terminal because the process exided. I clicked yes. I > relauched > >> mnemosyne.py again, and I get the same error: mismached user > ids. Again I > >> did not find a mnemosyne directory on the SD-card. > >> > >> kl. 11:36:21 UTC+1 l�rdag 14. desember 2013 skrev Gnome > f�lgende: > >>> > >>> There is no mnemosyne directory in the root of the sd-card > >>> and mnemosyne.py refers to "/sdcard/mnemosyne/". > >>> .js files does not seem to be synced. > >>> > >>> kl. 07:31:42 UTC+1 l�rdag 14. desember 2013 skrev Peter > Bienstman > >>> f�lgende: > >>>> > >>>> That's probably because of the thing that went wrong during > the first > >>>> sync with the filenames. Delete your Mnemosyne directory on > your > >>>> Android and sync again. > >>>> > >>>> Javascript support is of course courtesy of the browser you use > to > >>>> review to determine whether this actually works well. > >>>> > >>>> Cheers, > >>>> > >>>> Peter > >>>> > >>>> Citeren Gnome <[email protected]>: > >>>> > >>>> > I renamed all the files and it finished syncing. The client went > into > >>>> > 'review mode'. The card did not display anything (it was an > card with > >>>> some > >>>> > javascript in it), so I clicked 'exit'. The script excited into SL4A. > >>>> Then > >>>> > I did review a few cards on the server to a card without > javascript. > >>>> So I > >>>> > started the client again and I got this error message: "Error: > >>>> mismached > >>>> > user ids. The first sync should happen on an empty > database." > >>>> > > >>>> > kl. 19:01:30 UTC+1 fredag 13. desember 2013 skrev Peter > Bienstman > >>>> f�lgende: > >>>> >> > >>>> >> You seem to having a media file with non-latin characters in > it. I'll > >>>> try > >>>> >> to > >>>> >> fix this for the next release, but for now, you can work > around this > >>>> by > >>>> >> renaming the file. > >>>> >> > >>>> >> Cheers, > >>>> >> > >>>> >> Peter > >>>> >> > >>>> >> > -----Original Message----- > >>>> >> > From: [email protected] <javascript:> > [mailto: > >>>> >> mnemosyne-proj- <javascript:> > >>>> >> > [email protected] <javascript:>] On Behalf Of > Gnome > >>>> >> > Sent: 13 December 2013 18:38 > >>>> >> > To: [email protected] <javascript:> > >>>> >> > Subject: Re: [mnemosyne-proj-users] Re: 2.3 test release > >>>> >> > > >>>> >> > I have the latest 2.3. It says "Sending mediafiles" on the > server > >>>> and > >>>> >> the > >>>> >> > android client says: > >>>> >> > Taceback (innermost last): > >>>> >> > File "/mnt/sdcard/sl4a/scripts/openSM2sync/client.py", > line 567, in > >>>> >> > get_server_media_files file_size, progress_bar=False) File > >>>> >> > "/mnt/sdcard/sl4a/scripts/openSM2sync/partner.py", line > 35, in > >>>> >> > download_binary_file = file (filname, "wb") > >>>> >> > UnicodeEncoeError: 'ascii' codec can't encode character > u'\xf8' in > >>>> >> position 59: > >>>> >> > ordinal not in range(128) > >>>> >> > > >>>> >> > > >>>> >> > kl. 06:20:33 UTC+1 fredag 13. desember 2013 skrev Peter > Bienstman > >>>> >> > f�lgende: > >>>> >> > > >>>> >> > The new Android client will take some time to > develop, so > >>>> by all > >>>> >> > means report all the errors you can find :-) > >>>> >> > > >>>> >> > Make sure to run the 2.3 I posted in the mail on the > server > >>>> too, > >>>> >> and > >>>> >> > not some earlier version. > >>>> >> > > >>>> >> > Peter > >>>> >> > > >>>> >> > > >>>> >> > Gnome <[email protected] <javascript:> > wrote: > >>>> >> > > >>>> >> > I really apprecheate the time taken to develop > >>>> this, but > >>>> >> I > >>>> >> see > >>>> >> > the android client may have some issues. It connects to > my server > >>>> for > >>>> >> > syncing, but I get an error message on the client. I'm not > sure if > >>>> I > >>>> >> should > >>>> >> > report these errors if a totally new version will be > developed. > >>>> >> > > >>>> >> > Also when going into settings in mnemosyne and > >>>> clicking > >>>> >> ok > >>>> >> > seems to cause mnemosyne to crash after the server is > set up. > >>>> >> > > >>>> >> > > >>>> >> > kl. 22:29:04 UTC+1 torsdag 12. desember 2013 > skrev > >>>> Gnome > >>>> >> > f�lgende: > >>>> >> > > >>>> >> > Finally! I have been waiting for this > >>>> release. > >>>> >> > > >>>> >> > kl. 21:53:17 UTC+1 torsdag 12. desember > >>>> 2013 > >>>> >> skrev > >>>> >> > Peter Bienstman f�lgende: > >>>> >> > > >>>> >> > > >>>> >> > A preliminary version of 2.3 for > >>>> people > >>>> >> to > >>>> >> > play with is now available: > >>>> >> > > >>>> >> > > >>>> >> > > >>>> http://users.ugent.be/~pbienst/pub/mnemosyne-2.3-pre- > setup.exe <http://users.ugent.be/~pbienst/pub/mnemosyne-2.3-pre- > setup.exe> > >>>> >> > <http://users.ugent.be/~pbienst/pub/mnemosyne-2.3- > pre-setup.exe <http://users.ugent.be/~pbienst/pub/mnemosyne-2.3-pre- > setup.exe> > > >>>> >> > > >>>> >> > > http://users.ugent.be/~pbienst/pub/Mnemosyne%20Android.zip > <http://users.ugent.be/~pbienst/pub/Mnemosyne%20Android.zip> > >>>> >> > > <http://users.ugent.be/~pbienst/pub/Mnemosyne%20Android.zip > <http://users.ugent.be/~pbienst/pub/Mnemosyne%20Android.zip> > > >>>> >> > > >>>> >> > (Note the Android version requires > >>>> also > >>>> >> the > >>>> >> > 2.3 desktop version) > >>>> >> > > >>>> >> > Changelog: > >>>> >> > > >>>> >> > (Note that for Windows users we > >>>> >> > recommend uninstalling the previous version > >>>> >> > before installing the new one.) > >>>> >> > > >>>> >> > The sync protocol has changed in > >>>> this > >>>> >> > version, so make sure you update both > >>>> >> > the client and the server at the > >>>> same > >>>> >> time. > >>>> >> > > >>>> >> > -A quick-and-dirty Android client > >>>> is > >>>> >> available, > >>>> >> > where you can do reviews in > >>>> >> > your mobile browser using a > >>>> webserver > >>>> >> > which runs on your Android device. > >>>> >> > This client has full support for > >>>> the > >>>> >> syncing > >>>> >> > protocol. > >>>> >> > -The functionality of > >>>> >> mnemosyne-webserver > >>>> >> > has now been merged into the main > >>>> >> > program and can be activated > >>>> through > >>>> >> > 'Configure Mnemosyne - servers'. > >>>> >> > -Time to create backups has > >>>> decreased, > >>>> >> in > >>>> >> > some situations even by a factor > >>>> >> > of 2 or more, speeding up syncing > >>>> and > >>>> >> > program exit. > >>>> >> > -Sped up all editing operations in > >>>> the > >>>> >> card > >>>> >> > browser. > >>>> >> > -The name of the currently active > >>>> saved > >>>> >> set > >>>> >> of > >>>> >> > cards is now listed in title > >>>> >> > bar (requested by Silverbear). > >>>> >> > -Added new statistic: number of new > >>>> >> cards > >>>> >> > learned per day. > >>>> >> > -Also sync relevant settings (e.g. > >>>> >> fonts, > >>>> >> > colours, ...) during the initial > >>>> >> > sync. > >>>> >> > -Improve the timeout handling of > >>>> the > >>>> >> sync > >>>> >> > protocol. > >>>> >> > -Fix erroneous 'Wrong username or > >>>> >> > password' error. > >>>> >> > -Keep the sort order in the card > >>>> browser > >>>> >> > when editing cards (reported by > >>>> >> > Gnome and Tristan). > >>>> >> > -Added command line options > >>>> >> --sync-server > >>>> >> > and --web-server which starts the > >>>> >> > sync and the web server in > >>>> headless > >>>> >> mode > >>>> >> > (i.e. without a GUI) (useful to run > >>>> >> > e.g. on a NAS server). > >>>> >> > -Fix more errors coming from > >>>> loading > >>>> >> config > >>>> >> > files. > >>>> >> > -Rework error handling when trying > >>>> to > >>>> >> load a > >>>> >> > database which no longer exists > >>>> >> > in its previous location. > >>>> >> > -When editing a card through the > >>>> >> browser, > >>>> >> > make sure the correct set of tags is > >>>> >> > displayed if sister cards have > >>>> >> different > >>>> >> tags > >>>> >> > (requested by Scott Youngman). > >>>> >> > -Instruct people on the correct way > >>>> to > >>>> >> deal > >>>> >> > with '*.cards' files if they try > >>>> >> > to open it as a separate database > >>>> >> (Kensor0). > >>>> >> > -Make it clearer what 'Find > >>>> duplicates' > >>>> >> does. > >>>> >> > -Various cosmetic fixes when > >>>> importing > >>>> >> > *.cards files (reported by Ansgar > >>>> >> > Bohmann). > >>>> >> > -Fix tag tree sometimes not > >>>> updating > >>>> >> > correctly if the user adds a new tag. > >>>> >> > -People writing e.g. Javascript > >>>> card and > >>>> >> > needing access to the full path of > >>>> >> > the media directory can now use > >>>> >> > db_media:///foo.png (requested by Gnome). > >>>> >> > -Flash files are now synced as well > >>>> >> (reported > >>>> >> > by heldtfisken). > >>>> >> > -When editing a card where > >>>> different > >>>> >> sister > >>>> >> > cards have different tags, ask if > >>>> >> > the tags should be applied to the > >>>> >> current > >>>> >> > card or to all sister cards. > >>>> >> > -Fix Windows crash when using the > >>>> card > >>>> >> > browser with cards imported from > >>>> >> > Supermemo (reported by Piotr). > >>>> >> > -Make Mnemosyne 1.x import more > >>>> robust > >>>> >> > (reported by Jack Thro). > >>>> >> > -Don't allow saving the database to > >>>> a > >>>> >> > network drive under Windows to prevent > >>>> >> > corruption (reported by Brendan > >>>> >> Sinclair). > >>>> >> > -Fix sync error that could occur > >>>> when > >>>> >> adding > >>>> >> > and immediately deleting multiple > >>>> >> > sister cards from the card > >>>> browser. > >>>> >> > -Fix latex / cloze interaction > >>>> corner > >>>> >> case > >>>> >> > (reported by Daniele Parisi). > >>>> >> > -Make sure latex images are always > >>>> in > >>>> >> sync > >>>> >> > when updating text. > >>>> >> > -If adding an extra tag when > >>>> importing a > >>>> >> > 'cards' file, don't keep the tag > >>>> >> > 'Untagged' (patch by crcmail0). > >>>> If you > >>>> >> were > >>>> >> > affected by this issue before, > >>>> >> > 'compact database' will solve > >>>> this. > >>>> >> > > >>>> >> > > >>>> >> > > >>>> >> > > >>>> >> > > >>>> >> > -- > >>>> >> > 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] > <javascript:> <javascript:>. > >>>> >> > >>>> >> > To post to this group, send email to mnemosyne-proj- > >>>> >> > [email protected] <javascript:>. > >>>> >> > To view this discussion on the web visit > >>>> >> > > >>>> https://groups.google.com/d/msgid/mnemosyne-proj- > users/9129b966-efed- <https://groups.google.com/d/msgid/mnemosyne- > proj-users/9129b966-efed-> > >>>> >> > 4884-9990-20944318c9c2%40googlegroups.com > <http://40googlegroups.com> . > >>>> >> > For more options, visit > https://groups.google.com/groups/opt_out > <https://groups.google.com/groups/opt_out> . > >>>> >> > >>>> >> > >>>> >> > >>>> > > >>>> > -- > >>>> > 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- > [email protected] <javascript:> . > >>>> > To post to this group, send email to mnemosyne- > [email protected]. > >>>> > To view this discussion on the web visit > >>>> > > >>>> https://groups.google.com/d/msgid/mnemosyne-proj- > users/0bab47b8-5889-4e09-8a35-681e23beeb11%40googlegroups.com > <https://groups.google.com/d/msgid/mnemosyne-proj-users/0bab47b8- > 5889-4e09-8a35-681e23beeb11%40googlegroups.com> . > >>>> > >>>> > For more options, visit > https://groups.google.com/groups/opt_out > <https://groups.google.com/groups/opt_out> . > >>>> > >>>> > >>>> > >>>> > > > > -- > > 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- > [email protected] <javascript:> . > > To post to this group, send email to mnemosyne- > [email protected] <javascript:> . > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/mnemosyne-proj- > users/c6d4b85f-bf3e-462f-8c71-da3c9aee0ec3%40googlegroups.com > <https://groups.google.com/d/msgid/mnemosyne-proj-users/c6d4b85f- > bf3e-462f-8c71-da3c9aee0ec3%40googlegroups.com> . > > For more options, visit https://groups.google.com/groups/opt_out > <https://groups.google.com/groups/opt_out> . > > > > > > -- > 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 post to this group, send email to mnemosyne-proj- > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/mnemosyne-proj-users/59511c7c-7791- > 4585-b512-f74b5c9400e2%40googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- 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 post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mnemosyne-proj-users/013201cefa4b%2453f30610%24fbd91230%24%40UGent.be. For more options, visit https://groups.google.com/groups/opt_out.
