I've committed a fix for this to launchpad (file
mnemosyne/libmnemosyne/configuration.py). If you want a full tarball, just
let me know.
Cheers,
Peter
On Wednesday, 5 November 2014 22:21:34 UTC+1, Chris wrote:
>
> Some more info in addition to the email:
>
> I tested this also on a fresh installation of Ubuntu 14.04 within a
> virtual machine. After installation of Mnemosyne 2.3.1 I tested the
> following command sequence:
>
> 1. mnemosyne --sync-server --web-server
> 2. mnemosyne
> 3. mnemosyne --sync-server --web-server
> 4. mnemosyne
>
> Commands 1, 2, and 4 worked without an error, but with the 3rd command
> the same error occured as before. So it doesn't seem to be possible to
> run Mnemosyne headless after running Mnemosyne GUI once. But Mnemosyne
> with GUI works with web server and sync server enabled.
>
> Cheers,
> Chris
>
>
> Am 05.11.2014 um 15:43 schrieb Peter Bienstman:
> > I'm rather flabbergasted: your config.db contains e.g.
> >
> >
> PyQt4.QtCore.QByteArray('\x01\xd9\xd0\xcb\x00\x01\x00\x00\x00\x00\x02N\x00\x00\x01\x86\x00\x00\x04i\x00\x00\x03\xa3\x00\x00\x02X\x00\x00\x01\xac\x00\x00\x04_\x00\x00\x03\x99\x00\x00\x00\x00\x00\x00')
>
> for the key 'configuration_dlg_state', which indicates a system where
> you've already opened the configuration dialog.
> >
> > The default value for this key upon creation is hard coded to 'None', so
> I don't see any way the key could have gotten the value it did, especially
> since you don't seem to have Qt installed on your headless server.
> >
> > Just to make absolutely sure you're not picking up any old file from a
> different system, try the following experiment
> >
> > mnemosyne --sync-server --web-server -d a_completely_new_and_empty_dir
> >
> > In that case, Mnemosyne will create a new database and config in
> a_completely_new_and_empty_dir
> >
> > Also feel free to run a find command on your entire filesytem and delete
> any 'config', 'config.py' and 'config.db' files you can find.
> >
> > Cheers,
> >
> > Peter
> >
> > Peter
> >
> >
> >> -----Original Message-----
> >> From: [email protected] [mailto:mnemosyne-
> >> [email protected]] On Behalf Of [email protected]
> >> Sent: 05 November 2014 14:03
> >> To: [email protected]
> >> Subject: Re: [mnemosyne-proj-users] Unexpected error occurs when
> >> starting mnemosyne headless
> >>
> >> I deleted the whole config directory ~/.config/mnemosyne so both
> config.db
> >> and config where deleted.
> >>
> >> Is there any other directory to consider?
> >>
> >>
> >> Am 05.11.2014 um 14:00 schrieb Peter Bienstman:
> >>> Hi,
> >>>
> >>> Are you sure you've deleted config.db and config? There seems to be
> still a
> >> Qt object stored in the configuration database which is being picked
> up.
> >>> ~
> >>> Peter
> >>>
> >>>> -----Original Message-----
> >>>> From: [email protected] [mailto:mnemosyne-
> >>>> [email protected]] On Behalf Of Chris
> >>>> Sent: 05 November 2014 13:47
> >>>> To: [email protected]
> >>>> Subject: [mnemosyne-proj-users] Unexpected error occurs when starting
> >>>> mnemosyne headless
> >>>>
> >>>> I upgraded to Mnemosyne 2.3.1 and now I get the following error, when
> >>>> starting Mnemosyne in headless mode:
> >>>>
> >>>>
> >>>> ...:~$ mnemosyne --sync-server --web-server An unexpected error has
> >>>> occurred.
> >>>> Please forward the following info to the developers:
> >>>>
> >>>> Traceback (innermost last):
> >>>> File "/usr/local/bin/mnemosyne", line 5, in <module>
> >>>> pkg_resources.run_script('Mnemosyne==2.3.1', 'mnemosyne')
> >>>> File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 528,
> >>>> in run_script
> >>>> self.require(requires)[0].run_script(script_name, ns)
> >>>> File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line
> >>>> 1401, in run_script
> >>>> exec(script_code, namespace, namespace)
> >>>> File "/usr/local/lib/python2.7/dist-packages/Mnemosyne-2.3.1-
> >>>> py2.7.egg/EGG-INFO/scripts/mnemosyne", line 79, in <module>
> >>>> File "build/bdist.linux-
> >>>> x86_64/egg/mnemosyne/libmnemosyne/__init__.py", line 186, in
> >> initialise
> >>>> self.activate_components()
> >>>> File "build/bdist.linux-
> >>>> x86_64/egg/mnemosyne/libmnemosyne/__init__.py", line 264, in
> >>>> activate_components
> >>>> self.component_manager.current("config").activate()
> >>>> File "build/bdist.linux-
> >>>> x86_64/egg/mnemosyne/libmnemosyne/configuration.py", line 82, in
> >>>> activate
> >>>> self.load()
> >>>> File "build/bdist.linux-
> >>>> x86_64/egg/mnemosyne/libmnemosyne/configuration.py", line 213, in
> >> load
> >>>> self[cursor[0]] = eval(cursor[1])
> >>>> File "<string>", line 1, in <module>
> >>>> AttributeError: 'module' object has no attribute 'QtCore'
> >>>> An unexpected error has occurred.
> >>>> Please forward the following info to the developers:
> >>>>
> >>>> Traceback (innermost last):
> >>>> File "/usr/local/bin/mnemosyne", line 5, in <module>
> >>>> pkg_resources.run_script('Mnemosyne==2.3.1', 'mnemosyne')
> >>>> File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 528,
> >>>> in run_script
> >>>> self.require(requires)[0].run_script(script_name, ns)
> >>>> File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line
> >>>> 1401, in run_script
> >>>> exec(script_code, namespace, namespace)
> >>>> File "/usr/local/lib/python2.7/dist-packages/Mnemosyne-2.3.1-
> >>>> py2.7.egg/EGG-INFO/scripts/mnemosyne", line 79, in <module>
> >>>> File "build/bdist.linux-
> >>>> x86_64/egg/mnemosyne/libmnemosyne/__init__.py", line 186, in
> >> initialise
> >>>> self.activate_components()
> >>>> File "build/bdist.linux-
> >>>> x86_64/egg/mnemosyne/libmnemosyne/__init__.py", line 264, in
> >>>> activate_components
> >>>> self.component_manager.current("config").activate()
> >>>> File "build/bdist.linux-
> >>>> x86_64/egg/mnemosyne/libmnemosyne/configuration.py", line 82, in
> >>>> activate
> >>>> self.load()
> >>>> File "build/bdist.linux-
> >>>> x86_64/egg/mnemosyne/libmnemosyne/configuration.py", line 213, in
> >> load
> >>>> self[cursor[0]] = eval(cursor[1])
> >>>> File "<string>", line 1, in <module>
> >>>> AttributeError: 'module' object has no attribute 'QtCore'
> >>>>
> >>>>
> >>>> This error didn't occur with Mnemosyne 2.3, only after the upgrade to
> >>>> Mnemosyne 2.3.1.
> >>>> The system is Ubuntu 14.04.
> >>>> I also deleted the config directory (~/.config/mnemosyne) but this
> >>>> didn't solve the problem.
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> 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-
> >> [email protected].
> >>>> To post to this group, send email to mnemosyne-proj-
> >>>> [email protected].
> >>>> To view this discussion on the web visit
> >>>> https://groups.google.com/d/msgid/mnemosyne-proj-users/ec32e3dd-
> >>>> 7607-4be2-b997-8afd8b3b8501%40googlegroups.com
> >>>> <https://groups.google.com/d/msgid/mnemosyne-proj-users/ec32e3dd-
> >>>> 7607-4be2-b997-
> >>>>
> >> 8afd8b3b8501%40googlegroups.com?utm_medium=email&utm_source=foo
> >>>> ter> .
> >>>> For more options, visit https://groups.google.com/d/optout.
> >> --
> >> 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 [email protected].
> >> To post to this group, send email to mnemosyne-proj-
> >> [email protected].
> >> To view this discussion on the web visit
> >> https://groups.google.com/d/msgid/mnemosyne-proj-
> >> users/545A2003.4040702%40online.de.
> >> For more options, visit https://groups.google.com/d/optout.
>
>
--
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/mnemosyne-proj-users/858d676d-cdda-4733-b035-a54910dd8185%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
