Problem upgrading to 7.51 or 7.52

[speakingtohe]

I upgraded to 7.51 and calibre could not load library
I then upgraded to 7.52 with the same result.
I tried many things, including renaming /moving library directories running in debug mode etc. Leaving Calibre running overnight and had no luck

Calibre loads Splash screen. Splash screen disappears and nothing happens.
Windows task manager shows Calibre running with 6 parallel processes.
No cpu usage showing and the memory usage for Calibre.exe increments by 4k every 5-10 seconds.

After failing to get either version to work I went back to 7.47

Calibre said the database was corrupted so I tried another library which loaded.

I deleted the Calibre config directory and then it would load the original library

I thought it would be a good time to just start a new library and import all books. This went surprisingly well and was much faster than I expected. Missed a few hundred but that can be fixed.

Database check passed.

Installed 7.52 again and back where I started.

Calibre loads Splash screen. Splash screen disappears and nothing happens.
Windows task manager shows Calibre running with 6 parallel processes.
No cpu usage showing and the memory usage for Calibre.exe increments by 4k every 5-10 seconds.

I am running Windows 7 on I7 system and have had no previous problems with Calibre.
I assume it is a problem that only I am having as I have been reading the forum looking for a clue.

Any advice greatly appreciated.

Thanks
Helen

[ldolse]

You could try launching from the command line using this command:
calibre-debug -g

And then paste the debug output here.

[speakingtohe]

Alright
Thanks Helen

C:\Program Files (x86)\Calibre2>calibre-debug -g
Starting up...
Traceback (most recent call last):
File "site-packages\calibre\gui2\main.py", line 253, in initialize
File "site-packages\calibre\gui2\main.py", line 234, in initialize_db
File "site-packages\calibre\gui2\main.py", line 203, in initialize_db_stage2
File "site-packages\calibre\gui2\main.py", line 159, in start_gui
File "site-packages\calibre\gui2\ui.py", line 228, in initialize
File "site-packages\calibre\gui2\init.py", line 58, in __init__
File "site-packages\calibre\gui2\library\views.py", line 412, in set_database
File "site-packages\calibre\gui2\library\models.py", line 154, in set_database

File "site-packages\calibre\gui2\library\models.py", line 699, in build_data_c
onvertors
AttributeError: 'NoneType' object has no attribute 'get'

[DoctorOhh]

The first time you run calibre after upgrading beyond version 0.7.47 it will take longer to start because of a database change that requires the database to be adjusted.

So the question is did you let it run long enough before you killed it? Since it was running and the memory usage was increasing I'm guessing you didn't let it finish the database changes.

From Calibre's Change Log

Release: 0.7.48 [04 Mar, 2011]

New Features

• Changes to the internal database structure used by calibre "These changes will allow calibre, in the future, to support book language, arbitrary book identifiers and keep track of when the metadata for a book was last modified. WARNING: Because of these changes, if you downgrade calibre versions after upgrading to 0.7.48, you will lose any changes you make to the ISBN of book entries in your calibre database, so do not downgrade unless you really have to. Also note that the first time you start calibre after this update, the startup will be slow as the database structure is being changed."

[Lady Fitzgerald]

Is it necessary to install 0.7.48 before installing a later version if installing from a version earlier than 0.7.48? How long does it typically take for calibre to convert to the new database?

[speakingtohe]

I did run it overnight first time (about 10 hours) and was doing it again.
I stupidly thought it should be done as my computer is very fast.
It is now running in debug mode I will just leave it go I guess?

Thanks Helen

[DoctorOhh]

Originally Posted by Lady Fitzgerald

Is it necessary to install 0.7.48 before installing a later version if installing from a version earlier than 0.7.48? How long does it typically take for calibre to convert to the new database?

No, I don't believe installing 0.7.48 is required. I don't recall it taking too long for these changes to the database but everyone's setups are different.

[DoctorOhh]

Originally Posted by speakingtohe

I did run it overnight first time (about 10 hours) and was doing it again.
I stupidly thought it should be done as my computer is very fast.
It is now running in debug mode I will just leave it go I guess?

Thanks Helen

It shouldn't take that long. Hopefully someone with more insight will check out your situation.

You could open a bug ticket.

[chaley]

That debug log says that there is something wrong with a custom column.

How much of calibre comes up? In particular, can you see the toolbar and use the preferences dialogs? If so, then go to preferences -> add your own columns, then for each custom column, select it, press the I button to look at its properties, then press OK having changed nothing. After doing this to all columns, press Apply. My strong suspicion is that the error will disappear.

[chaley]

I looked at the code, and there isn't any obvious way that the custom columns can get broken in the way they seem to have been. I would like to understand how it got that way. Could you give me a copy of your database (metadata.db)? Zip it first, please, then send it to calibre-bugs at charles dot haleys dot org.

Thanks

BTW: letting it run won't do anything useful...

EDIT: I can probably fix the db, in which case I will send it back to you.

[speakingtohe]

Nothing comes up but the splash screen which disappears in 10 seconds.
Calibre is not listed in the task manager under applications tab as it would normally be.
Windows task manager process tab shows Calibre running with 6 parallel processes.

Thanks Helen

[speakingtohe]

BTW: letting it run won't do anything useful

I stopped it, deleted config directory and started calibre with empty library
That was fine
I tried opening library I created 2 days ago and got
-------------
calibre, version 0.7.52
ERROR: Unhandled exception: <b>AttributeError</b>:'NoneType' object has no attribute 'get'

Traceback (most recent call last):
File "site-packages\calibre\gui2\dialogs\choose_library.py", line 97, in accept
File "site-packages\calibre\gui2\dialogs\choose_library.py", line 72, in perform_action
File "site-packages\calibre\gui2\actions\choose_library.py", line 387, in choose_library_callback
File "site-packages\calibre\gui2\ui.py", line 439, in library_moved
File "site-packages\calibre\gui2\library\views.py", line 412, in set_database
File "site-packages\calibre\gui2\library\models.py", line 154, in set_database
File "site-packages\calibre\gui2\library\models.py", line 699, in build_data_convertors
AttributeError: 'NoneType' object has no attribute 'get'


--------------------------
I tried creating a custom column and got

calibre, version 0.7.52
ERROR: Unhandled exception: <b>KeyError</b>:u'#err'

Traceback (most recent call last):
File "site-packages\calibre\gui2\preferences\main.py", line 275, in show_plugin
File "site-packages\calibre\gui2\preferences\columns.py", line 38, in initialize
File "site-packages\calibre\gui2\preferences\columns.py", line 65, in init_columns
File "site-packages\calibre\gui2\preferences\columns.py", line 65, in <lambda>
KeyError: u'#err'

----------------------------------

It is 3:30 AM here so I will have to try tomorrow.
I will reinstall 7.47 again and see if I can sort out the custom column issue using that release.

Thanks for your help.
Helen

[speakingtohe]

The problem is mostly resolved and was caused by corrupted database which Charles (chaley) repaired.
Thanks all
Helen

[chaley]

Thanks for the database. I identified the symptom, and have added code to repair the problem when it occurs. This change will be in the next release.

Unfortunately, I haven't identified how it happened. The four suspects, check_database, create_library, restore_database, and modify column, all do the right thing.