An unexpected error has occurred on startup

Bug #1508881 reported by themusicgod1
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mnemosyne (Ubuntu)
Fix Committed
Undecided
Unassigned

Bug Description

Error in config:

Traceback (innermost last):
  File "/usr/lib/python2.7/dist-packages/mnemosyne/libmnemosyne/configuration.py", line 186, in load
    for key, value in cPickle.load(config_file).iteritems():
 EOFError

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

Traceback (innermost last):
  File "/usr/bin/mnemosyne", line 155, in <module>
    debug_file=options.debug_file)
  File "/usr/lib/python2.7/dist-packages/mnemosyne/libmnemosyne/__init__.py", line 171, in initialise
    self.activate_components()
  File "/usr/lib/python2.7/dist-packages/mnemosyne/libmnemosyne/__init__.py", line 251, in activate_components
    self.component_manager.current(component).activate()
  File "/usr/lib/python2.7/dist-packages/mnemosyne/libmnemosyne/logger.py", line 22, in activate
    self.archive_old_log()
  File "/usr/lib/python2.7/dist-packages/mnemosyne/libmnemosyne/logger.py", line 175, in archive_old_log
    if not self.config()["upload_science_logs"]:
 KeyError: 'upload_science_logs'

I did run out of hard disk space yesterday so I'm guessing something got a short read.
After closing the above two error messages, mnemosyne no longer starts.

Ubuntu 15.10
mnemosyne: 2.2.1-3

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: mnemosyne 2.2.1-3
Uname: Linux 4.1.0-040100rc1-generic x86_64
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Oct 22 06:38:01 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-07-09 (469 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708)
PackageArchitecture: all
SourcePackage: mnemosyne
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
themusicgod1 (themusicgod1) wrote :
Revision history for this message
Peter Bienstman (peter-bienstman) wrote :

This bug has been fixed a long time ago in more recent versions of Mnemosyne.

As a workaround, delete the file 'config' in Mnemosyne's configuration directory (typically ~/.config/Mnemosyne )

Changed in mnemosyne (Ubuntu):
status: New → Fix Released
Revision history for this message
themusicgod1 (themusicgod1) wrote :

That works but I appear to be running the most current version available for wily.

Changed in mnemosyne (Ubuntu):
status: Fix Released → Fix Committed
Changed in mnemosyne (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Peter Bienstman (peter-bienstman) wrote :

The packages in Ubuntu are probably not up to date, you need to install from source to get the latest version.

Revision history for this message
themusicgod1 (themusicgod1) wrote :

reproduced in ubuntu 16.04 / mnemosyne 2.2.1-3

Changed in mnemosyne (Ubuntu):
status: Fix Released → Fix Committed
no longer affects: mnemosyne (Debian)
tags: added: xenial
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.