openlp-core team mailing list archive
-
openlp-core team
-
Mailing list archive
-
Message #24559
[Bug 1388227] Re: Crash upgrading from 2.0.3 to 2.1.0.2435
Note, installing 2.1 into a brand new location is fine
--
You received this bug notification because you are a member of OpenLP
Core, which is subscribed to OpenLP.
https://bugs.launchpad.net/bugs/1388227
Title:
Crash upgrading from 2.0.3 to 2.1.0.2435
Status in OpenLP - Worship Presentation Software:
New
Bug description:
Windows 7
In my case the Portable package, but has occurred for normal package too.
I installed OpenLPPortable_2.0.3.paf.exe into a new location, and ran OpenLP.
I then installed OpenLPPortable_2.1.0.2435.paf into the same location.
Installation went fine. During first run it asked if I wanted to backup the database. I clicked OK.
Following this, a crash occurred with this error.
Traceback (most recent call last):
File "c:\Python33\lib\site-packages\sqlalchemy\engine\base.py", line 940, in _execute_context
statement,
File "c:\Python33\lib\site-packages\sqlalchemy\engine\default.py", line 435, in do_execute
if not parameters:
sqlite3.OperationalError: no such column: authors_songs_1.author_type
(See attached for full log)
OpenLP then started, however exiting later the same error occurred.
To manage notifications about this bug go to:
https://bugs.launchpad.net/openlp/+bug/1388227/+subscriptions
References