"bad interpreter: /usr/bin/python^M" error with Mnemosyne 2.6

57 views
Skip to first unread message

sml...@gmail.com

unread,
Dec 12, 2017, 2:53:24 AM12/12/17
to mnemosyne-proj-users
After building and installing the just-released Mnemosyne 2.6, it failed to start on my Arch Linux system, with the following error message written to the terminal:

    zsh: /bin/mnemosyne: bad interpreter: /usr/bin/python^M: no such file or directory

It turns out this is because the start-up script (called `Mnemosyne-2.6/mnemosyne/pyqt_ui/mnemosyne` in the release bundle and installed to `/usr/bin/mnemosyne`) uses CRLF line endings, and the shell stupidly thinks the CR is part of the interpreter path.
I'm not sure if it's only Arch Linux and/or the zsh shell that is so strict about line endings, but the issue was easily worked around by removing that first CR character, which I did here in my Arch Linux install script for Mnemosyne:

    https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=mnemosyne#n27

Posting here in case this issue affects others, as well.

Peter Bienstman

unread,
Dec 12, 2017, 7:28:16 AM12/12/17
to mnemosyne-...@googlegroups.com

Thanks, I’ve uploaded a new tarball with the correct line endings.

 

Cheers,

 

Peter

 

--
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-u...@googlegroups.com.
To post to this group, send email to mnemosyne-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mnemosyne-proj-users/448dbd34-0e91-459f-8285-d0861f48386b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages