Your message dated Thu, 14 Jul 2022 11:36:42 +0200 with message-id <[email protected]> and subject line Obsolete - sorry has caused the Debian Bug report #873313, regarding mnemosyne: "NameError: name 'file' is not defined" to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 873313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873313 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: mnemosyne Version: 2.4-0.1 Severity: normal Hi, When trying to start mnemosyne, I'm getting/got the following error message right at the beginning: ~~~~~~ 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 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/dist-packages/mnemosyne/libmnemosyne/__init__.py", line 190, in initialise Upgrade3(self.component_manager).run() File "/usr/lib/python3/dist-packages/mnemosyne/libmnemosyne/upgrades/upgrade3.py", line 21, in run file(os.path.join(self.config().config_dir, "config"), "rb") NameError: name 'file' is not defined ~~~~~~ I tried removing my old "~/.mnemosyne" config folder, but that did not help. What did help though: Removing "~/.config/mnemosyne. See the attachment, mnemosyne.tar.xz, for a copy of the ~/.config/mnemosyne causing the crash. I hadn't used mnemosyne for quite a while. In fact, the configs were probably from back when I had them on an x86 machine (now it's armhf). Regards, Linus -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: armhf (armv7l) Kernel: Linux 4.2.3-00234-g11acd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mnemosyne depends on: ii libjs-sphinxdoc 1.5.6-2 ii libqt5sql5-sqlite 5.9.1+dfsg-9 ii python3 3.5.3-3 ii python3-cherrypy3 3.5.0-2 ii python3-matplotlib 2.0.0+dfsg1-2+b1 ii python3-pyqt5 5.7+dfsg-6 ii python3-pyqt5.qtsql 5.7+dfsg-6 ii python3-pyqt5.qtwebchannel 5.7+dfsg-6 ii python3-pyqt5.qtwebengine 5.7+dfsg-6 ii python3-webob 1:1.6.2-2 mnemosyne recommends no packages. mnemosyne suggests no packages. -- no debconf information
mnemosyne.tar.xz
Description: application/xz
--- End Message ---
--- Begin Message ---Hi, this bug report looks like it's for a long-gone mnemosyne version ; it's probably obsolete now. Thanks for the report, J.Puydt
--- End Message ---
