Since updating my system and Digikam and getting the segfault, I have requested help and also stretched my sqlit database knowledge some. The segfault problem has been reported to the bugtracker with backtrace. Since then I have tried to understand why I am segfaulting. To that end I have looked at the database. The database is not corrupt. The pictures are not corrupt and open in all other photo programs. I have come to believe that the problem is caused by Digikam 3.3.0 not being able to open and convert my database version 4 to the latest version 6. I have been unable find or install a earlier version of the software to attempt conversion. I did follow some advice to change the database version to 5 and try again. That failed. I am at a dead end. Before I abandon Digikam and my photo's and tag's which go back to the 1960's and I am not able to recreate (my 67 year old memory is at fault here) I would like to ask one final time if there is anyone who can take my database and convert it to version 6. My OS is NetrunnerOS version 13.06 and all software has been installed from the official repositories. KDE is at version 4.11.1. Thank you for all your help.

Which bug is that, do you have a link? I'm afraid only the digikam devs will be able to really help you, though. You should for sure comment on the bug that you're affected too (in case it wasn't you who reported it in the first place).

Crashes are always caused by programming errors, a corrupted database or image should not make the application crash... such a crash would be a bug, too, and should be fixed.

Cheers,
Sven

My original bug report was #324350 this was declared as a duplicate of bug #321403 and attached to it. All my software comes from the official repositories and the database was verified using sqlite version 3 as uncorrupted. My digikam internal database is at version 4 and has not been updated in some time. Digikam version 3.3.0 fails to convert my database to version 6 and that seems to cause the segfault. Just my guess. That is why I am looking for someone with database knowledge of Digikam to convert my database to the current version. My check of the database was due only to my luck in finding written insttructions as to how to do it.

Looks pretty clearly like a bug in digikam... you'll have to get the digikam devs to fix it, I guess
Trying to fix the problem yourself will be quite difficult I would guess, unless you find a report of how a similar problem was solved in the past.

Unfortunately I can't do more than recommending what to do to get the bug fixed more quickly:
* First and foremost, you could try to provide a way to reproduce the issue to the developers. Maybe you can offer to send them your database file via email or so, so they can hopefully reproduce the crash themseleves?
* If there's no replies, you can ask on the digikam mailing list (probably the developers' list for such an issue), or ask in their IRC channel (possibly repeatedly in case nobody is there).

Good luck,
Sven

Thanks for your reply. I have continued my testing, I have installed opensuse 12.3 on new partition it has Digikam 3.0.0. I then copied a version of database from backup to a empty partition, I then tried to migrate it to different directory using the Database migration tool and received the following error "Error while creating the database schema" no idea what it means. I then removed the Digikam configuration Folder and config file, then copied my Digikam3-db and Digikam4-db file and tried running Digikam I received the following error "No album library path has been found in the configuration file. Giving up the schema updating process. Please try with an empty database, or repair your configuration." Could it be that even thou sqlit3 states the database is not corrupted that it is or is missing some needed information. Now I am truly confused as to what is wrong having chased down several erroneous paths.

I did attach a note to the bug report in the hope of attracting attention. But still remain in need of help.

As I have worked thru this problem, I have taken instruction and learnt new things, how to use sqlite database browser, how to correct data in the database. Even thou sqlite said the database was not corrupted, I began to think that I had come to the wrong conclusion, and that I did not have sufficient knowledge to judge the true state of current backups of the database, so I went looking and found a two year old backup on a unmounted hard drive. And to my surprise when I restored the old database files Digikam began working. This reinforces the need for having multiple backups, both current and older static ones.

I want to thank all on this forum for your help, you all are more than wonderful, thank you all from the bottom of my heart.

Great, I'm glad it's working again for you! You should mention this in the bug report, it'll indicate that the crash is indeed related to an -- in whatever way -- "corrupted" database, and maybe help people fix it.

Cheers,
Sven