Package Details: mnemosyne 2.8-3

Git Clone URL: https://aur.archlinux.org/mnemosyne.git (read-only, click to copy)
Package Base: mnemosyne
Description: A flash-card tool with a sophisticated card review algorithm
Upstream URL: https://www.mnemosyne-proj.org
Keywords: Anki flashcard learn memorize
Licenses: GPL
Conflicts: mnemosyne-bzr
Submitter: wide-eyed
Maintainer: billypilgrim
Last Packager: billypilgrim
Votes: 86
Popularity: 0.002539
First Submitted: 2007-11-04 20:08 (UTC)
Last Updated: 2022-05-09 10:56 (UTC)

Latest Comments

colluphid commented on 2022-05-03 20:03 (UTC) (edited on 2022-05-03 20:03 (UTC) by colluphid)

I also ran into the the checksum issue. Using yay, the checksum verification can be skipped with:

yay -S mnemosyne --mflags '--skipchecksums'

j18318 commented on 2022-05-01 16:31 (UTC)

This patch file now has a sha256sum of 086691d23ab73354af338ba69c42d7facf36c2a6663271c95e242b35679a8ead - https://github.com/mnemosyne-proj/mnemosyne/commit/b0e85fbb54a23add1fe8a0d56123b2ddb056b325.patch

The package build refers to a different hash: c5a57b1486dda325d53c3692fdd63778d8224efa0774ac750434e04f2162f3a2

Not sure if the commit was ever c5a57..... maybe the author force-pushed a new commit?

Anyways, pacman is failing to install with the PKGBUILD as it is currently..

billypilgrim commented on 2021-09-25 07:43 (UTC)

@Lukas1818: I've followed your suggestion and updated the PKGBUILD accordingly. Let me know if you have any issues :-)

LuckyTurtleDev commented on 2021-09-14 12:06 (UTC) (edited on 2021-09-14 12:37 (UTC) by LuckyTurtleDev)

@billypilgrim I do not think waiting until the next release make sense. At the current state the application can not be used by anyone who has not already installed python-googletrans. So this package is useless for many users at the moment.

Furthermore the pull-request was already merged to the upstream.

billypilgrim commented on 2021-09-13 13:58 (UTC)

Hi CI-Lukas1818. Thanks for doing this. I think I'll hold off on updating the PKGBUILD until the upstream maintainer releases a new version though (hopefully incorporating these patches) before updating.

CI-Lukas1818 commented on 2021-09-11 22:02 (UTC) (edited on 2021-09-11 22:04 (UTC) by CI-Lukas1818)

@billypilgrim if you make the following change to this package, it can be build again:

diff --git a/PKGBUILD b/PKGBUILD
index f2d0c04..bf63528 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -8,28 +8,36 @@ pkgver=2.8
 pkgrel=1
 pkgdesc="A flash-card tool with a sophisticated card review algorithm"
 arch=('any')
-url='http://www.mnemosyne-proj.org'
+url='https://www.mnemosyne-proj.org'
 license=('GPL')
 depends=('python-pyqt5' 'qt5-webengine' 'python-argon2_cffi'
          'python-pillow' 'python-matplotlib' 'python-cherrypy' 'python-webob'
-         'python-pyqtwebengine' 'python-googletrans' 'python-google_trans_new' 'python-gtts')
+         'python-pyqtwebengine')
 makedepends=('python-setuptools')
 optdepends=('texlive-core: support for mathematical formulae in cards'
             'ttf-ms-fonts: support for non-latin labels on statistic plots'
             'python-cheroot: support for starting a sync server'
             'python-opengl: mentioned in a non-fatal warning'
-       'mplayer: for playing audio and video externally')
+            'mplayer: for playing audio and video externally'
+            'python-google_trans_new: support for google translate (googletrans is also needed)'
+            'python-googletrans: support for google translate (python-google_trans_new is also needed)'
+            'python-gtts: support for text to speach')
 conflicts=('mnemosyne-bzr')
 install='mnemosyne.install'

-source=("http://downloads.sourceforge.net/mnemosyne-proj/Mnemosyne-${pkgver}.tar.gz")
-sha256sums=('63949ad4b44188501915a0465f32d3ca066698c58f86c46cf3196f9d601f6900')
+source=("https://downloads.sourceforge.net/mnemosyne-proj/Mnemosyne-${pkgver}.tar.gz"
+        "https://github.com/mnemosyne-proj/mnemosyne/commit/b0e85fbb54a23add1fe8a0d56123b2ddb056b325.patch")
+sha256sums=('63949ad4b44188501915a0465f32d3ca066698c58f86c46cf3196f9d601f6900'
+            'c5a57b1486dda325d53c3692fdd63778d8224efa0774ac750434e04f2162f3a2')

 prepare() {
   cd "Mnemosyne-${pkgver}/"

   # Fix windows line endings
-  sed -i "s/\r//g" mnemosyne/pyqt_ui/mnemosyne
+  sed -i "s/\r//g" mnemosyne/pyqt_ui/mnemosyne mnemosyne/libmnemosyne/__init__.py
+
+  # patch to make google transate and goole text to speak optional
+  patch --forward --strip=1 --input="$srcdir/b0e85fbb54a23add1fe8a0d56123b2ddb056b325.patch"
 }

 build() {
@@ -42,4 +50,3 @@ package() {
   cd "Mnemosyne-${pkgver}/"
   python setup.py install --root="${pkgdir}" --optimize=1
 }
-

LuckyTurtleDev commented on 2021-09-09 13:18 (UTC) (edited on 2021-09-09 13:18 (UTC) by LuckyTurtleDev)

@billypilgrim I have created a pull request, which make both packages optional.#201

Using the following patch should fix the python-httpx issue: https://github.com/mnemosyne-proj/mnemosyne/pull/201/commits/b0e85fbb54a23add1fe8a0d56123b2ddb056b325.patch

LuckyTurtleDev commented on 2021-09-08 17:11 (UTC)

@billypilgrim I had already create an issue for this: #200

They do not have any interest to implementate this. So if we would like to have this features, we must create our own path. May the mnemosyne maintainer will accept a merge request.

billypilgrim commented on 2021-09-08 13:03 (UTC)

Thanks for the clarification @Lukas1818.

Neither of the issues you raise involve any changes I could make to this package, however. It looks like the python-httpx issue has already been mentioned on the python-googletrans page, so hopefully a fix is in hand. You're right that this should be optional functionality though -- how about raising an issue with the mnemosyne folks upstream?

LuckyTurtleDev commented on 2021-09-08 12:53 (UTC) (edited on 2021-09-08 12:57 (UTC) by LuckyTurtleDev)

@billypilgrim I think n1ghtmare does mean the python-httpx package, which is a dependency of python-googletrans. The problem is that python-googletrans is not compatible with the current python-httpx package and need an outdated version of it.

It would be very nice if python-googletrans and python-gtts will be only optimal dependencies, but sadly mnemosyne does not allow this.

May user can apply this patch manual, if they do not need google translate: https://salsa.debian.org/debian/mnemosyne/-/blob/master/debian/patches/disable_google_translator.patch

billypilgrim commented on 2021-08-21 20:15 (UTC)

@n1ghtmare: Your comment is a bit vague. What exact error message are you getting? Which dependencies seem to be missing?

n1ghtmare commented on 2021-08-21 16:43 (UTC)

Does not build because of missing dependencies.

billypilgrim commented on 2021-07-12 06:23 (UTC)

Weird. It did build on my local machine before, but you're right that the checks aren't passing anymore. I've fixed that now.

kachelaqa commented on 2021-07-12 00:58 (UTC)

The sha256 sum fails the validity check.

Jaaan commented on 2021-05-31 06:42 (UTC) (edited on 2021-05-31 06:43 (UTC) by Jaaan)

I believe that mplayer should be an optional dependency for sound playback in cards

billypilgrim commented on 2020-12-11 16:07 (UTC) (edited on 2020-12-11 16:12 (UTC) by billypilgrim)

Thanks @jmehne! I've updated the package to v2.7.3 now and I'll report the bug to upstream.

Edit: Oh, it seems like you're an upstream maintainer! Nvm then :-p

jmehne commented on 2020-10-31 20:14 (UTC)

I flagged the package out of date, but the commit I linked was flawed. Somehow the bin file now has windows line endings ... I fixed that here: https://git.sr.ht/~jmehne/mnemosyne-aur/commit/722745200346087cedc1528783617e5898c84e2d

LuckyTurtleDev commented on 2020-05-02 13:36 (UTC)

Does the sound of the cards work for you? I can not hear anything, if i add sound. In the webinterface it does work.

billypilgrim commented on 2019-11-28 13:47 (UTC)

Ta!

marmistrz commented on 2019-11-28 00:45 (UTC)

I disowned the package so that you can pick it up :) Have fun! :)

billypilgrim commented on 2019-11-27 22:39 (UTC)

Sure!

marmistrz commented on 2019-11-27 18:40 (UTC)

@billypilgrim: do you want to become a new maintainer of Mnemosyne? I switched to Anki TBH, so I can give the maintainership to you :)

billypilgrim commented on 2019-11-27 18:07 (UTC)

Ok, so somewhat embarrassingly I forgot that this wasn't my package and fixed up the PKGBUILD with the patch + new version and only noticed when I tried to push the changes. So @marmistrz, feel free to do: git pull https://github.com/alexdewar/mnemosyne master

...if you'd like my updated PKGBUILD.

jaudet commented on 2019-11-26 23:15 (UTC)

Looks like my custom repo somehow produced a borked build of mnemosyne. Forcing it to rebuild the package fixed my issue. I then hit the issue described by Hal5000, and the urllib-related fix detailed there worked for me. Thanks for submitting an upstream patch!

Hal5000 commented on 2019-11-19 20:17 (UTC) (edited on 2019-11-20 20:54 (UTC) by Hal5000)

Resolved it for me -- edited the file

/usr/lib/python3.8/site-packages/openSM2sync/server.py

by adding 

import urllib

and changing

        args = cgi.parse_qs(environ["QUERY_STRING"])

 in line 155 to:

        args = urllib.parse.parse_qs(environ["QUERY_STRING"])

Works for me again...

jaudet commented on 2019-11-17 18:29 (UTC) (edited on 2019-11-26 04:18 (UTC) by jaudet)

@Hal5000 can you wrap your console output in markdown code fences (triple backticks)? It's unreadable. (EDIT: Thank you!)

I can no longer start mnemosyne at all, whether the GUI client or the sync server. Both fail with the same error:

$ mnemosyne 
Traceback (most recent call last):
  File "/usr/bin/mnemosyne", line 46, in <module>
    from mnemosyne.libmnemosyne import Mnemosyne
ModuleNotFoundError: No module named 'mnemosyne'

Hal5000 commented on 2019-11-17 11:31 (UTC) (edited on 2019-11-18 20:08 (UTC) by Hal5000)

Yesterdays update of python broke the ability to start a sync server, please see the error message below. Has anyone else faced this problem an can suggest a fix?

Thank you and best regards,

hal

Edit: Thank you for the pointer regardin the code wrap, jerebear!


hal@shorty ~ % mnemosyne             
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
QIODevice::write (QProcess): device not open
QIODevice::write (QProcess): device not open
AttributeError("module 'cgi' has no attribute 'parse_qs'")
Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/cheroot/server.py", line 1280, in communicate
    req.respond()
  File "/usr/lib/python3.8/site-packages/cheroot/server.py", line 1083, in respond
    self.server.gateway(self).respond()
  File "/usr/lib/python3.8/site-packages/cheroot/wsgi.py", line 143, in respond
    response = self.req.server.wsgi_app(self.env, self.start_response)
  File "/usr/lib/python3.8/site-packages/openSM2sync/server.py", line 115, in wsgi_app
    status, method, args  = self.get_method(environ)
  File "/usr/lib/python3.8/site-packages/openSM2sync/server.py", line 155, in get_method
    args = cgi.parse_qs(environ["QUERY_STRING"])
AttributeError: module 'cgi' has no attribute 'parse_qs'
Log body:
 An unexpected error has occurred.
Please forward the following info to the developers:

Traceback (innermost last):
  File "/usr/lib/python3.8/site-packages/mnemosyne/pyqt_ui/main_wdgt.py", line 251, in configure
    self.controller().show_configuration_dialog()
  File "/usr/lib/python3.8/site-packages/mnemosyne/libmnemosyne/controllers/default_controller.py", line 962, in show_configuration_dialog
    self.component_manager.current("configuration_dialog")\
  File "/usr/lib/python3.8/site-packages/mnemosyne/pyqt_ui/configuration_dlg.py", line 27, in __init__
    widget = widget(component_manager=self.component_manager, parent=self)
  File "/usr/lib/python3.8/site-packages/mnemosyne/pyqt_ui/configuration_wdgt_servers.py", line 27, in __init__
    self.sync_server_initially_running = self.is_server_running(sync_port)
  File "/usr/lib/python3.8/site-packages/mnemosyne/pyqt_ui/configuration_wdgt_servers.py", line 54, in is_server_running
    assert b"OK" in con.getresponse().read()
 AssertionError

An unexpected error has occurred.
Please forward the following info to the developers:

Traceback (innermost last):
  File "/usr/lib/python3.8/site-packages/mnemosyne/pyqt_ui/main_wdgt.py", line 251, in configure
    self.controller().show_configuration_dialog()
  File "/usr/lib/python3.8/site-packages/mnemosyne/libmnemosyne/controllers/default_controller.py", line 962, in show_configuration_dialog
    self.component_manager.current("configuration_dialog")\
  File "/usr/lib/python3.8/site-packages/mnemosyne/pyqt_ui/configuration_dlg.py", line 27, in __init__
    widget = widget(component_manager=self.component_manager, parent=self)
  File "/usr/lib/python3.8/site-packages/mnemosyne/pyqt_ui/configuration_wdgt_servers.py", line 27, in __init__
    self.sync_server_initially_running = self.is_server_running(sync_port)
  File "/usr/lib/python3.8/site-packages/mnemosyne/pyqt_ui/configuration_wdgt_servers.py", line 54, in is_server_running
    assert b"OK" in con.getresponse().read()
 AssertionError
QIODevice::write (QProcess): device not open
b'Waiting for uploader thread to stop...'
b'Done!'
QIODevice::write (QProcess): device not open

billypilgrim commented on 2019-09-24 04:54 (UTC)

I believe that arch should be any for this package, rather than x86_64. It doesn't seem to contain any architecture-specific code.

marmistrz commented on 2019-04-14 08:22 (UTC)

@lchimonji10 thanks!

jaudet commented on 2019-02-14 20:09 (UTC)

Mnemosyne failed to start for me, with the console output listed here. Installing python-opengl fixed the initial warning. Installing python-pyqtwebengine fixed the crash error. Perhaps these should be added to optdepends and depends, respectively.

marmistrz commented on 2018-10-15 17:00 (UTC) (edited on 2018-10-15 17:00 (UTC) by marmistrz)

Updated PKGBUILD: https://gist.github.com/f0ea7000b121fe6bad6c6b50f18256ae

smls you can add me as a co-maintainer if you wish, I'm quite an active Mnemosyne user :)

XuLin commented on 2018-09-05 10:54 (UTC)

Contacted the author about the crash issues and here’s the reply: “Perhaps changing the minor version of Qt5 helps. Anyway, 2.6-2 is not an official Mnemosyne version number, I guess it has been packaged by your specific Linux distribution. I would contact the packagers, as they will probably better be able to figure what exactly is going wrong in your distribution.”

With that being said, can someone please repackage Mnemosyne to use version 2.6-1 please. Maybe that’ll get rid of the problems. Thanks.

macxcool commented on 2018-08-08 11:39 (UTC)

@Perico This looks like something that should be reported upstream. Have a look at https://mnemosyne-proj.org/getting_help.php for details. This is not an bug with the PKGBUILD.

Perico commented on 2018-03-08 13:39 (UTC)

mnemosyne 2.6 crashes as soon as I hit "add card". The rest of the program seems to work correctly. I paste the errors from the console. Thanks.

<hr>

libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile [0308/143136.672737:WARNING:stack_trace_posix.cc(648)] Failed to open file: /tmp/.glzxYHr1 (deleted) Error: No existe el fichero o el directorio QIODevice::write (QProcess): device not open QIODevice::write (QProcess): device not open QIODevice::write (QProcess): device not open QXcbShmImage: shmget() failed (22: Argumento inválido) for size -102507248 (367428x157441) QWidget::paintEngine: Should no longer be called QPainter::begin: Paint device returned engine == 0, type: 1 QPainter::pen: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QWidget::paintEngine: Should no longer be called QPainter::begin: Paint device returned engine == 0, type: 1 QPainter::setPen: Painter not active QPainter::save: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::setClipRect: Painter not active QPainter::pen: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::restore: Unbalanced save/restore QWidget::paintEngine: Should no longer be called QPainter::begin: Paint device returned engine == 0, type: 1 QPainter::pen: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QWidget::paintEngine: Should no longer be called QPainter::begin: Paint device returned engine == 0, type: 1 QPainter::setPen: Painter not active QPainter::save: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::setClipRect: Painter not active QPainter::restore: Unbalanced save/restore QWidget::paintEngine: Should no longer be called QPainter::begin: Paint device returned engine == 0, type: 1 QPainter::setClipRect: Painter not active QPainter::setPen: Painter not active QPainter::pen: Painter not active QPainter::pen: Painter not active QPainter::setPen: Painter not active QWidget::paintEngine: Should no longer be called QPainter::begin: Paint device returned engine == 0, type: 1 QPainter::save: Painter not active Received signal 11 SEGV_MAPERR 000000000000

0 0x7ff3bc10fe76 <unknown></unknown>
1 0x7ff3bad8d88c <unknown></unknown>
2 0x7ff3bc1101ec <unknown></unknown>
3 0x7ff3cad70dd0 <unknown></unknown>
4 0x7ff3c1caefce qDrawBorderPixmap()
5 0x7ff3c1d1ac20 QFusionStyle::drawPrimitive()
6 0x7ff3c1d21007 QFusionStyle::drawComplexControl()
7 0x7ff3c1d7bac6 QGroupBox::paintEvent()
8 0x7ff3a6b1a514 <unknown></unknown>
9 0x7ff3c1c82188 QWidget::event()
10 0x7ff3c1d7ce94 QGroupBox::event()
11 0x7ff3a6b19034 <unknown></unknown>
12 0x7ff3c1c41fec QApplicationPrivate::notify_helper()
13 0x7ff3c1c499c6 QApplication::notify()
14 0x7ff3a6a3433f <unknown></unknown>
15 0x7ff3c0ec3da0 QCoreApplication::notifyInternal2()
16 0x7ff3c1c7aa6c QWidgetPrivate::sendPaintEvent()
17 0x7ff3c1c7b123 QWidgetPrivate::drawWidget()
18 0x7ff3c1c7be45 QWidgetPrivate::paintSiblingsRecursive()
19 0x7ff3c1c7bfd6 QWidgetPrivate::paintSiblingsRecursive()
20 0x7ff3c1c7bfd6 QWidgetPrivate::paintSiblingsRecursive()
21 0x7ff3c1c7bfd6 QWidgetPrivate::paintSiblingsRecursive()
22 0x7ff3c1c7ac4f QWidgetPrivate::drawWidget()
23 0x7ff3c1c5190b <unknown></unknown>
24 0x7ff3c1c520d3 <unknown></unknown>
25 0x7ff3c1c9f5ca <unknown></unknown>
26 0x7ff3c1c9feef <unknown></unknown>
27 0x7ff3c1c41fec QApplicationPrivate::notify_helper()
28 0x7ff3c1c499c6 QApplication::notify()
29 0x7ff3a6a3433f <unknown></unknown>
30 0x7ff3c0ec3da0 QCoreApplication::notifyInternal2()
31 0x7ff3c1438383 QGuiApplicationPrivate::processExposeEvent()
32 0x7ff3c143900e QGuiApplicationPrivate::processWindowSystemEvent()
33 0x7ff3c141029c QWindowSystemInterface::sendWindowSystemEvents()
34 0x7ff3a5f3848d <unknown></unknown>
35 0x7ff3c0ec23db QEventLoop::exec()
36 0x7ff3c1e3969b QDialog::exec()
37 0x7ff3a6a70f69 <unknown></unknown>
38 0x7ff3ca5a9ad0 _PyCFunction_FastCallDict
39 0x7ff3ca5cfd1b <unknown></unknown>
40 0x7ff3ca563b5a _PyEval_EvalFrameDefault
41 0x7ff3ca5cf85b <unknown></unknown>
42 0x7ff3ca5cfdde <unknown></unknown>
43 0x7ff3ca563b5a _PyEval_EvalFrameDefault
44 0x7ff3ca5cf85b <unknown></unknown>
45 0x7ff3ca5cfdde <unknown></unknown>
46 0x7ff3ca563b5a _PyEval_EvalFrameDefault
47 0x7ff3ca5cf36b _PyFunction_FastCallDict
48 0x7ff3ca5b30bf _PyObject_FastCallDict
49 0x7ff3ca5b3e03 _PyObject_Call_Prepend
50 0x7ff3ca5b3eeb PyObject_Call
51 0x7ff3a7cc4011 <unknown></unknown>
52 0x7ff3a7cc4501 <unknown></unknown>
53 0x7ff3a7cc4793 <unknown></unknown>
54 0x7ff3a7cc5128 <unknown></unknown>
55 0x7ff3c0ef4792 QMetaObject::activate()
56 0x7ff3c1c3b533 QAction::triggered()
57 0x7ff3c1c3ddb6 QAction::activate()
58 0x7ff3c1d390ec <unknown></unknown>
59 0x7ff3c1d3935e QAbstractButton::mouseReleaseEvent()
60 0x7ff3c1e1f6ab QToolButton::mouseReleaseEvent()
61 0x7ff3c1c82188 QWidget::event()

r8: 00007ffe9f6714e0 r9: 00007ffe9f6714c0 r10: 00007ffe9f6714c0 r11: 007900740073002f r12: 00007ffe9f671490 r13: 00007ffe9f6714a0 r14: 0000000000000006 r15: 0000000000000002 di: 00007ffe9f671a70 si: 0000000000000004 bp: 0000000000059b28 bx: 0000000000059b22 dx: 0000000000000010 ax: 0000000000000000 cx: 0000000000000056 sp: 00007ffe9f670700 ip: 00007ff3c1caefce efl: 0000000000010246 cgf: 002b000000000033 erf: 0000000000000004 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000000 [end of stack trace] Calling _exit(1). Core file will not be generated.

marmistrz commented on 2018-02-15 13:59 (UTC)

smls, can you either cherry-pick for the package or take the release from git until 2.6 is released? See https://groups.google.com/forum/#!topic/mnemosyne-proj-users/FuxpQ4079w0

smls commented on 2017-12-14 20:58 (UTC)

@marmistrz Fixed now. (The upstream package had received a small post-release bugfix update without a new version number.)

marmistrz commented on 2017-12-14 19:26 (UTC)

I get an integrity check fail

smls commented on 2017-08-09 21:34 (UTC)

@marmistrz: An oversight. I added it now. Thanks!

marmistrz commented on 2017-08-08 16:30 (UTC)

Why is --optimize=1 not passed to setup.py? https://wiki.archlinux.org/index.php/Python_package_guidelines#distutils

Kanjelman commented on 2017-07-14 18:25 (UTC)

@smls I can also confirm that the font-changing crash no longer happens with the latest version. Many thanks for your help and the hard work you do in maintaining this package. Cheers!

smls commented on 2017-07-14 14:22 (UTC) (edited on 2017-07-14 14:22 (UTC) by smls)

@Kanjelman: With the new Mnemosyne version (2.5), the font-changing crash no longer happens for me. Just re-install the package to get that version. @marmistrz: I switched to sha256 now for this package. But I'm wondering, if this is best practice, why does `makepkg -g` still generate an md5sum by default?

marmistrz commented on 2017-07-14 12:26 (UTC)

Btw. it may be a good idea to move on to sha256/512sums. md5 collisions are so easy nowadays.

smls commented on 2017-07-03 15:25 (UTC)

@Kanjelman I can confirm that error. Will investigate.

Kanjelman commented on 2017-07-01 21:26 (UTC)

@smls This is my first time installing Mnemosyne. Here are my observations when looking for the three locations you describe ~/.local/share/mnemosyne -there are two folders, 'Mnemosyne' and 'mnemosyne' -Mnemosyne contains QtWebEngine (folder) -mnemosyne contains: backups (folder) default.db_media (folder) history (folder) plugins (folder) default.db (SQLite3 database) default.db-journal (unknown) ~/.config/mnemosyne/ -there is one folder, 'mnemosyne' which contains _pycache_ (folder) config.db (SQLite3 database) config.py (Python script) machine.id (plain text document) ~/.Mnemosyne/ -could not be found I went ahead and deleted the mnemosyne folders in the two locations (backing up first). Afterwards, I tried to launch mnemosyne from the launcher icon, and now it loads! I was also able to successfully import my .cards file from backup. Unfortunately, a new problem occurs when I try to change the font style or size: An unexpected error has occurred. Please forward the following info to the developers: Traceback (innermost last): File "/usr/lib/python3.6/site-packages/mnemosyne/pyqt_ui/configuration_dlg.py", line 54, in accept self.tab_widget.widget(index).apply() File "/usr/lib/python3.6/site-packages/mnemosyne/pyqt_ui/configuration_wdgt_card_appearance.py", line 206, in apply update(card_type) File "/usr/lib/python3.6/site-packages/mnemosyne/libmnemosyne/renderers/html_css.py", line 94, in update self.card_type_css(card_type, **render_args) File "/usr/lib/python3.6/site-packages/mnemosyne/libmnemosyne/renderers/html_css.py", line 71, in card_type_css family,size,x,x,w,i,u,s,x,x = font_string.split(",") ValueError: too many values to unpack (expected 10) However, if this is the only problem...I can live with it for now. Many thanks for your time and help.

smls commented on 2017-06-30 20:44 (UTC)

@Kanjelman I'm not getting that error on Arch Linux / KDE. However, the Mnemosyne mailing list seems to have a report of the same error by a Linux Mint user a few months ago: https://groups.google.com/forum/#!topic/mnemosyne-proj-users/OEI50SSlzf4 Apparently it was solved by "making sure leftovers from a previous partial install were deleted", though no details are given. Did you have an existing ~/.local/share/mnemosyne/ or ~/.config/mnemosyne/ or ~/.Mnemosyne/, and if so, does removing those folders fix the problem? (Be sure to make backup first of course.)

Kanjelman commented on 2017-06-30 02:06 (UTC) (edited on 2017-06-30 02:11 (UTC) by Kanjelman)

Hello, I just installed Mnemosyne 2.4.1 via AUR in Manjaro Linux xfce. Upon launching the program, the following error occurred. Any assistance is appreciated. An unexpected error has occurred. Please forward the following info to the developers: Traceback (innermost last): File "/usr/bin/mnemosyne", line 247, in <module> debug_file=options.debug_file) File "/usr/lib/python3.6/site-packages/mnemosyne/libmnemosyne/__init__.py", line 226, in initialise raise e File "/usr/lib/python3.6/site-packages/mnemosyne/libmnemosyne/__init__.py", line 217, in initialise self.log().started_program() File "/usr/lib/python3.6/site-packages/mnemosyne/libmnemosyne/loggers/database_logger.py", line 26, in started_program self.database().log_started_program(self.timestamp, version_string) File "/usr/lib/python3.6/site-packages/mnemosyne/libmnemosyne/databases/SQLite_logging.py", line 30, in log_started_program self.con.execute(\ File "/usr/lib/python3.6/site-packages/mnemosyne/libmnemosyne/databases/SQLite.py", line 256, in con self._connection = _Sqlite3(self.component_manager, self._path) File "/usr/lib/python3.6/site-packages/mnemosyne/libmnemosyne/databases/_sqlite3.py", line 53, in __init__ self.connection = sqlite3.connect(path) TypeError: argument 1 must be str, not None

smls commented on 2017-04-28 09:50 (UTC)

@jsh6789: I've added it to optdepends for now, since not every Mnemosyne installation needs to support starting a sync server.

jsh6789 commented on 2017-04-04 00:05 (UTC)

In order to start the sync server, the package python-cheroot must be installed; please add it as a dependency. Relevant error message: Traceback (innermost last): File "/usr/lib/python3.6/site-packages/mnemosyne/pyqt_ui/configuration_dlg.py", line 54, in accept self.tab_widget.widget(index).apply() File "/usr/lib/python3.6/site-packages/mnemosyne/pyqt_ui/configuration_wdgt_servers.py", line 84, in apply self.component_manager.current("sync_server").activate() File "/usr/lib/python3.6/site-packages/mnemosyne/pyqt_ui/qt_sync_server.py", line 193, in activate component_manager=self.component_manager) File "/usr/lib/python3.6/site-packages/mnemosyne/pyqt_ui/qt_sync_server.py", line 65, in __init__ super().__init__(ui=self, **kwds) File "/usr/lib/python3.6/site-packages/mnemosyne/libmnemosyne/sync_server.py", line 31, in __init__ port=config["sync_server_port"], **kwds) File "/usr/lib/python3.6/site-packages/mnemosyne/libmnemosyne/component.py", line 48, in __init__ super().__init__(**kwds) File "/usr/lib/python3.6/site-packages/openSM2sync/server.py", line 98, in __init__ from cheroot import wsgi ModuleNotFoundError: No module named 'cheroot' Thanks in advance, JSH

bonob commented on 2017-01-11 15:16 (UTC)

Support for Fcitx input method requires fcitx-qt5 when upgrading to Mnemosyne 2.4. Not sure if that deserves an optional dependency here, or maybe a note on the wiki page? In any case, if someone runs into the same problem as me, my comment may be of help.

smls commented on 2016-12-21 00:47 (UTC)

@bialou: Added.

bialou commented on 2016-12-20 23:32 (UTC)

@smls So we probably should put that python-pillow package as a dependency. .... or any other package that has pillow and/or(?) image in it. P.S. I run i3wm, if it matters.

bialou commented on 2016-12-20 23:26 (UTC) (edited on 2016-12-20 23:32 (UTC) by bialou)

@Ichimonji10 "pip3 install --user image" installed 3 packages: django-1.10.4 image-1.5.5 pillow-3.4.2; I uninstalled them manually and tried python-pillow package instead. Everything still works good now and I don't have that error on "Browse Cards" button you have. So, it must be something else going on. The only thing I did before installing python-pillow is to uninstall django, image, and pillow with "pip uninstall ..."

jaudet commented on 2016-12-20 22:57 (UTC) (edited on 2016-12-20 23:11 (UTC) by jaudet)

@smls, thanks for the fix! Mnemosyne no longer suffers from the error I outlined. I now suffer from the same error described by @bialou: PIL (python imaging library) is not installed. The suggested solution is to install image with pip. I *think* a more generic solution is to install the python-pillow package with pacman. It works well enough to let mnemosyne start. Edit: I'm now suffering from a new issue. It's probably an issue with mnemosyne itself. @smls, can you take a look, and let the maintainers know about it if appropriate? This error log pops up when I press the "Browse cards" button. http://i.imgur.com/Ekie5SU.png

bialou commented on 2016-12-20 06:16 (UTC)

@hongleong: Installing it manually "pip3 install --user image" takes care of that problem. Hopefully, this can be fixed correctly later. Thank you, for help.

hongleong commented on 2016-12-20 03:28 (UTC)

@bialou: pip3 install --user image

bialou commented on 2016-12-20 03:03 (UTC) (edited on 2016-12-20 03:14 (UTC) by bialou)

mnemosyne 2.4-2 fails to start. /usr/bin/python ==> Python 3.5.2 --------------------------------------------------- ~]$ mnemosyne libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile QIODevice::write (QProcess): device not open An unexpected error has occurred. Please forward the following info to the developers: Traceback (innermost last): File "/usr/bin/mnemosyne", line 229, in <module> debug_file=options.debug_file) File "/usr/lib/python3.5/site-packages/mnemosyne/libmnemosyne/__init__.py", line 234, in initialise self.main_widget().activate() File "/usr/lib/python3.5/site-packages/mnemosyne/pyqt_ui/main_wdgt.py", line 52, in activate self.start_review() File "/usr/lib/python3.5/site-packages/mnemosyne/libmnemosyne/component.py", line 121, in start_review self.review_controller().reset() File "/usr/lib/python3.5/site-packages/mnemosyne/libmnemosyne/review_controllers/SM2_controller.py", line 62, in reset self.show_new_question() File "/usr/lib/python3.5/site-packages/mnemosyne/libmnemosyne/review_controllers/SM2_controller.py", line 123, in show_new_question self.update_dialog() File "/usr/lib/python3.5/site-packages/mnemosyne/libmnemosyne/review_controllers/SM2_controller.py", line 200, in update_dialog self.update_qa_area(redraw_all) File "/usr/lib/python3.5/site-packages/mnemosyne/libmnemosyne/review_controllers/SM2_controller.py", line 237, in update_qa_area w.clear_answer() File "/usr/lib/python3.5/site-packages/mnemosyne/pyqt_ui/review_wdgt.py", line 248, in clear_answer self.update_stretch_factors() File "/usr/lib/python3.5/site-packages/mnemosyne/pyqt_ui/review_wdgt.py", line 145, in update_stretch_factors self.estimate_height(self.question_text) File "/usr/lib/python3.5/site-packages/mnemosyne/pyqt_ui/review_wdgt.py", line 114, in estimate_height from PIL import Image ImportError: No module named 'PIL' -------------------------------------

smls commented on 2016-12-16 12:21 (UTC)

@Ichimonji10 It turns out `qt5-webengine` needed to be explicitly specified as a dependency. The package has been updated. (I thought `python-pyqt5` pulls in all the Qt stuff, but apparently Qt is more modular now than it was during Qt4 times.)

smls commented on 2016-12-16 11:57 (UTC)

@Ichimonji10 It starts fine for me. Maybe I forgot to explicitly specify a dependency or something? Please ensure that your Arch Linux is fully upgraded, and that /usr/bin/python points to python3. Meanwhile, I'll try to investigate the issue on my end.

jaudet commented on 2016-12-15 18:40 (UTC)

The current version of mnemosyne fails to start. Downgrading to version 2.3.6 (git checksum a35a25f) allows mnemosyne to start. See: http://pastebin.com/LRcq7Epx

smls commented on 2016-05-19 02:55 (UTC)

@marmistrz Sorry about that. Fixed now.

marmistrz commented on 2016-05-18 13:06 (UTC)

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

smls commented on 2014-10-20 16:59 (UTC)

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 (UTC)

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

russo79 commented on 2014-09-03 19:51 (UTC)

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!

joelsc commented on 2014-09-03 17:45 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

@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 (UTC)

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 (UTC)

Glad it worked out :)

gojun077 commented on 2013-08-24 05:00 (UTC)

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 (UTC)

@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 (UTC)

@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 (UTC)

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 (UTC)

@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 (UTC)

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 (UTC)

done

prettyvanilla commented on 2013-01-08 02:00 (UTC)

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.

commented on 2012-08-03 06:05 (UTC)

Working reliably now with version 2.0.1, thank you.

smls commented on 2012-08-02 20:41 (UTC)

Version 2.0.1 was just released - package updated accordingly.

smls commented on 2012-08-01 22:36 (UTC)

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?

commented on 2012-08-01 16:40 (UTC)

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 (UTC)

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 (UTC)

@dsr: Thanks...

commented on 2012-07-14 20:45 (UTC)

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 (UTC)

@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 (UTC)

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

smls commented on 2012-02-11 17:41 (UTC)

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.

commented on 2010-10-24 20:28 (UTC)

All right, just did.

bostonvaulter commented on 2010-10-21 23:06 (UTC)

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?

commented on 2010-10-21 17:36 (UTC)

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}"