>When I start menmosyne, I get these messages:
..
>For each card I review on the desktop, the terminal writes out this message in the terminal: QIODevice::write (QProcess): device not open
These should be harmless.
>Sometimes when I finish a card, it takes about 10 seconds before the question appears. I do not see a pattern in why or how often this happens yet. I >thought it happened mostly with images, but then I saw that it happened with other cards as well.
That's a bit strange.... I noticed that qtwebengine is a bit slower than the previous qtwebkit, but it typically renders in < 0.5 sec on my machine.
>When reviewing images, I sometimes, but not always get messages like this in the terminal "Missing path >/home/me/mnemosyne/default.db_media/maps/1018_Sogne.gif" But reviewing the card seems to work fine, and mnemosyne finds the image.
Does that file actually exist or is Mnemosyne getting it from somewhere else?
What happens if you add
optimise_Q_A_split = False
to your config.py? Does that impact the speed issues?
>Another problem I've had for a while is that latex cards aren't always synced with the mobile app. I mentioned that on the mailing list before, and the >answer was to delete everything on the mobile device and sync again. That didn't work. One strange thing I seem to observe is that when I sync >between my windows box (client) and my ubuntu box (server), the windows box seem to want to generate all the latex images (it takes a while), but >when syncing between my mnemosyne server (ubuntu) and the android app, mnemosyne doesn't seem to be generating any images (of course, it >might be that it's so quick that I'm not noticing it) Output to the terminal indicates that pdfTeX is being run.
On your Ubuntu server, the best way to check if the latex images are being generated is to delete the contents of default.db_media/_latex and then do the initial sync again. This should result in the png files being created in that directory. The directory will also contain the latex log files, which perhaps contain useful info.
>Something funny with the hanging progress bars after sync is that they seem to multiply. First time I sync I get 2. Second time 3. Third time 4.
Seems Qt is not executing the calls to close the progress bar correctly...
Thanks for the feedback!
Peter