Package Details: mnemosyne 2.3.6-2

Git Clone URL: https://aur.archlinux.org/mnemosyne.git (read-only)
Package Base: mnemosyne
Description: A flash-card tool with a sophisticated card review algorithm
Upstream URL: http://www.mnemosyne-proj.org
Keywords: Anki flashcard learn memorize
Licenses: GPL
Conflicts: mnemosyne-bzr
Submitter: wide-eyed
Maintainer: smls
Last Packager: smls
Votes: 70
Popularity: 1.176214
First Submitted: 2007-11-04 20:08
Last Updated: 2016-05-19 02:55

Latest Comments

smls commented on 2016-05-19 02:55

@marmistrz Sorry about that. Fixed now.

marmistrz commented on 2016-05-18 13:06

The md5sum check fails as of 2016-05-18.

smls commented on 2014-10-20 16:59

It looks like russo79's patch was committed upstream, so after the next Mnemosyne release it will no longer need to be bundled with the PKGBUILD... :)

shuu commented on 2014-10-12 02:51

It looks like python2-distribute should be changed to python2-setuptools in the extra repo. Python2-distribute is not in the AUR anymore.

shuu commented on 2014-10-08 23:03

python2-distribute doesn't appear to be in the AUR anymore.

russo79 commented on 2014-09-03 19:51

Here [1] (in the mnemosyne directory) you'll find a PKGBUILD that fix this issue.

The only thing to do is to force matplotlib to use the Qt4 backend.
By default it chooses the Qt5 one and that conflicts with mnemosyne.

[1] https://cloud.russo79.com/public.php?service=files&t=f00d660f9ae6001dd09276e960a02e9d

Feel free to take it!

russo79 commented on 2014-09-03 19:51

Here [1] you'll find a PKGBUILD that fix this issue.

The only thing to do is to force matplotlib to use the Qt4 backend.
By default it chooses the Qt5 one and that conflicts with mnemosyne.

[1] https://cloud.russo79.com/public.php?service=files&t=f00d660f9ae6001dd09276e960a02e9d

Feel free to take it!

joelsc commented on 2014-09-03 17:45

Note that you can get the basic functionality (without plotting) by commenting line 9 from the file /usr/lib/python2.7/site-packages/mnemosyne/pyqt_ui/statistics_wdgts_plotting.py:

- from matplotlib.backends.backend_qt4agg import FigureCanvasQTAgg as FigureCanvas
+ #from matplotlib.backends.backend_qt4agg import FigureCanvasQTAgg as FigureCanvas

vagyok commented on 2014-08-30 18:54

Thanks for your quick and helpful response. I can confirm that downgrading to python2-matplotlib 1.3.1-4 fixed the issue for me.

As far as I can see, though, the current version of python2-matplotlib in [community] has been 1.4.0-1 since 2014-08-28.

smls commented on 2014-08-30 14:15

For now, you can make it work by downgrading python2-matplotlib to version 1.3.x (which is still the current version in [community] -- only version 1.4.0 from [community-testing] is causing the issue).

As for the python2-pyqt -> python2-pyqt4 rename, I've updated the PKGBUILD now to reflect this.

Still investigating the issue with matplotlib 1.4 though.

smls commented on 2014-08-30 13:06

@vagyok: Thanks for reporting; I see the same errors. For what it's worth, python2-pyqt4 is the correct dependency as Mnemosyne is a Qt4 program; the fact that the matplotlib dependency tries to load Qt5 is strange. I'll investigate.

vagyok commented on 2014-08-30 12:09

python2-pyqt , which is currently a dependency of this package, no longer seems to exist - it is apparently either python2-pyqt4 (which replaced python2-pyqt ) or python2-pyqt5 in [extra] now.

Trying it with python2-pyqt4 (and its pyqt4-common dependency) gave me the following error:

File "/usr/lib/python2.7/site-packages/matplotlib/backends/qt_compat.py", line 91, in <module>
from PyQt5 import QtCore, QtGui, QtWidgets
ImportError: No module named PyQt5

(in full: http://pastebin.com/FMT3WFsB )

Trying it with both python2-pyqt4 (and its pyqt4-common dependency) and python2-pyqt5 (and its pyqt5-common dependency) installed before rebuilding the package gave me the following error:

File "/usr/lib/python2.7/site-packages/matplotlib/backends/qt_compat.py", line 91, in <module>
from PyQt5 import QtCore, QtGui, QtWidgets
RuntimeError: the PyQt5.QtCore and PyQt4.QtCore modules both wrap the QObject class

(in full: http://pastebin.com/6aMr6es9 )

Trying to remove python2-pyqt4 (and/or pyqt4-common) so as to use only python2-pyqt5 and pyqt5-common failed because this package depends on python2-matplotlib in [community], which requires python2-pyqt4 explicitly, which, in turn, requires pyqt4-common.

Any suggestions?

smls commented on 2013-08-24 11:39

Glad it worked out :)

gojun077 commented on 2013-08-24 05:05

You are a godsend, smls!!! Thanks to the path info you gave me for latex tmp files created by Mnemosyne, I was able to track down tmp.tex and open it in Gummi, my LaTeX editor. The problem was that tmp.tex failed to build at all due to a missing font!

My LaTeX preamble in Mnemosyne was as follows:

\documentclass[12pt]{article}
\usepackage{amsmath, amsfonts, amssymb, cancel}
...

Unfortunately the LaTeX font package cancel.sty in \usepackage above was missing from my Arch install! The font is provided by the package texlive-extralatex

Now creating LaTeX cards works perfectly when running Mnemosyne as a local user. I wonder why running Mnemosyne as root allowed LaTeX to render despite missing one font file, however...

gojun077 commented on 2013-08-24 05:00

You are a godsend, smls!!! Thanks to the path info you gave me for latex tmp files created by Mnemosyne, I was able to track down tmp.tex and open it in Gummi, my LaTeX editor. The problem was that tmp.tex failed to build at all due to a missing font!

My LaTeX preamble in Mnemosyne was as follows:

\documentclass[12pt]{article}
\usepackage{amsmath, amsfonts, amssymb, cancel}
...

Unfortunately the LaTeX font package cancel.sty in \usepackage above was missing from my Arch install! The font is provided by the package texlive-extralatex

Now creating LaTeX cards works perfectly when running Mnemosyne as a local user. I wonder why running Mnemosyne as root allowed LaTeX to render despite missing one font file, however...

smls commented on 2013-08-23 11:36

@gojun077
If the problem persists, try manually following the individual steps that Mnemosyne performs, to see where exactly the problem lies:

1) Create a file called tmp.tex with the following content:

\documentclass[12pt]{article}
\pagestyle{empty}
\begin{document}
$\sqrt{x^3}$
\end{document}

2) Execute the command...

latex tmp.tex

...which will try to create a file called tmp.dvi in the same folder. Be sure to also check the console output for errors.

3) Execute the command...

dvipng -D 200 -T tight tmp.dvi

...which will try to create a file called tmp1.png in the same folder.

smls commented on 2013-08-23 11:29

@gojun077
That's strange, there should not be any need for special permissions or groups - for me it just works.

Mnemosyne creates its LaTeX related temporary tex/dvi/png files in this folder (insert the name of your Mnemosyne database in place of "___TMP___", if you have given it an explicit name.):

~/.local/share/mnemosyne/___TMP___.db_media/_latex

Make sure that there are no permission problems with this folder, and if there are old files there that may cause problems, remove them.

gojun077 commented on 2013-08-23 06:01

Thanks for your help in the dvipng / LaTeX thread on the main Arch Linux forums (https://bbs.archlinux.org/viewtopic.php?pid=1315420#p1315420) -- Now dvipng LaTeX rendering works in mnemosyne if I run it as root. When I run mnemosyne as regular user and try to create a card with LaTeX, however, the CLI output says "tmp.dvi: No such file or directory" and Mnemosyne complains, "Problem with latex. Are latex and dvipng installed?"

This seems to be a file permission issue, but ls -l shows dvipng as r-x for regular users. Does my regular user need to be member of some group (i.e. tex) to be able to run LaTeX as non-root? After the texlive update I accidentally overwrote my /etc/group file when merging .pacnew files but have mostly recovered my original settings.

I'm not sure if this is the right place to post this issue, as mnemosyne AUR package works just fine -- I seem to be having problems with texlive which is just an optional dependency for mnemosyne...

Note: LaTeX editors like Gummi, which render to PDF, are working just fine for me (I can run it as local user).

smls commented on 2013-03-29 18:56

@gojun077
Thanks, I've bumped the version number of the mnemosyne-bzr package.
For the mnemosyne package, I prefer to stick to stable releases only.

gojun077 commented on 2013-03-29 17:21

According to main developer Peter Bienstman 2.2.1 RC1 released yesterday:
https://groups.google.com/forum/?fromgroups=#!topic/mnemosyne-proj-users/AIUxvJ3a1Sw

smls commented on 2013-01-08 03:01

done

prettyvanilla commented on 2013-01-08 02:00

2.2a was released (http://mnemosyne-proj.org/whats-new), and even though the changelog only concerns windows, the tarball on sourceforge has also been renamed accordingly, so the PKGBUILD needs updating.

Anonymous comment on 2012-08-03 06:05

Working reliably now with version 2.0.1, thank you.

smls commented on 2012-08-02 20:41

Version 2.0.1 was just released - package updated accordingly.

smls commented on 2012-08-01 22:36

No crashes here.
Anyways, according to the upstream mailinglist, a new version (2.0.1) which supposedly fixes certain crashes will be released soon. A release candidate is already available, you can install it using the following PKGBUILD: http://pastebin.com/YXNv9ajv - can you try that one and see if it solves your issue?

Anonymous comment on 2012-08-01 16:40

Is anyone else experiencing random crashes with 2.0? I am crashing the program using the same database on two different Arch systems. The developer has acknowledged a problem but it does not seem to be prevalent on Linux. It's been a couple of weeks now and I'm thinking about going back to the old program.

smls commented on 2012-07-15 14:11

I've updated the package to the current stable version 2.0 now. In case of problems or suggestions, please leave a comment.

smls commented on 2012-07-15 14:08

@dsr: Thanks...

Anonymous comment on 2012-07-14 20:45

Sorry I had forgotten I was the maintainer. I am disowning it now so you can adopt it. :)

smls commented on 2012-06-16 08:08

@Maintainer: See my "mnemosyne-bzr" package for build instructions for the 2.x version, and a useful post-install message for users who upgrade from 1.x ...

I think it makes sense to let "mnemosyne-bzr" continue to point the head of the main development branch, and let this package ("mnemosyne") install the newest stable version of that branch, i.e. currently 2.0...

In case anybody wants to keep using Mnemosyne 1.2 (why would they?), a legacy "mnemosyne1" package could be created.

What do you think?

(PS: If you don't want to maintain this package anymore, I'd be happy to take it over.)

smls commented on 2012-06-16 08:03

Version 2.0 is finally out! (Announcement at http://www.mnemosyne-proj.org/news.php)

smls commented on 2012-02-11 17:41

FYI, I just created the AUR package mnemosyne-bzr, which installs the latest development snapshot of Mnemosyne 2 (which finally uses Qt4 instead of Qt3, and provides several cool new features) from the official bazaar repository.

The current state is already past version 2.0-beta10, and is already stable enough for normal usage.

Anonymous comment on 2010-10-24 20:28

All right, just did.

bostonvaulter commented on 2010-10-21 23:06

Thanks dsr, I've adopted and updated the package. Although I don't use mnemosyne anymore (I use Anki), maybe you'd like to adopt the package instead?

Anonymous comment on 2010-10-21 17:36

Now that python was changed to python2 and python3 was changed to python, the line in the PKGBUILD that reads ``python setup.py install --root=${pkgdir}" should be changed to ``python2 setup.py install --root=${pkgdir}"