[Digikam-users] Digikam 2.0 runs only once before corrupting the DB

[Marie-Noëlle Augendre]

Gilles, thank you very much for your input and advice.

I have (more or less) read the whole bug report and I understand the problem
is VERY complicate and that it might not be entirely a matter of packaging.

Anyway, as I saw there was a new package in the Fedora repository, I tried
to reinstall Digikam 2.0 from scratch (I had removed the 1.9 version
beforehand). This time I run Digikam from the console from the very first
launch, and  understood 2 things:
 - "thlibdc1394 error: Failed to initialize libdc1394" message is the first
one that appears at the first launch
 - when I closed the Digikam window, I got this message in the console :
"QSqlDatabasePrivate::removeDatabase: connection 'digikamDatabase-30048960'
is still in use, all queries will cease to work." and I had to do a Ctrl-C
after to get the control back (and that might be the incident that corrupts
my DB at every first launch)
I'm not sure the whole trace will be useful for you as you seem to have
plenty on this subject, but I keep it in case you want it.

As for now, I will 'try' to follow your advice and compile by myself; but:
1) I'm not even sure I'll reach the end of this procedure; if there is
somewhere some documentation understable by a newbie, I would very much like
to be pointed at it
2) I understand that even that could not solve the problem, as others - much
more experimented than I am - have already reported in the bug report.

If that fails, I'll have to go back to 1.9 and await for good news about
this problem.

Thanks for helping,
Marie-Noëlle




2011/8/21 Gilles Caulier <caulier.gilles at gmail.com>

> I don't know.
>
> But Francesco Riosa, who work currently on digiKam databse interface
> (especially Mysql) has fixed a lots of problem since 2.0.0.
>
> I recommend to Marie :
>
> 1/ Checkout current code from git master (2.1.0).
> 2/ Compile and install it instead to use a precompiled package.
>
> The advantage to use currrent implementation is to have of course bug fixes
> and to be able to see debug statements that developpers can add in life.
>
> Gilles Caulier
>
> 2011/8/21 Rinus <sleeplessregulus at hetnet.nl>
>
>> But Gilles, has this anything to do with the destroied db, which seems to
>> be his main problem?
>> Rinus
>>
>> Gilles Caulier <caulier.gilles at gmail.com>schreef:
>>
>>
>> Marie Noëlle,
>>
>> The problem with libdc1394 is an in-deep problem (solved in my computer
>> running Mageia). The story is there :
>>
>>    https://bugs.kde.org/show_bug.cgi?id=268267
>> To resume, it's an uncompatibilty between gphoto2 lib and OpenCV. Both use
>> libdc1394 and the initialization must be done in right order.
>>
>> Before to close this entry, i have been able to reproduce the crash. Now i
>> cannot...
>>
>> Read all the story in bugzilla, It's explained.
>>
>> A lots of people report that the crash still exist. So more
>> investiguations need to be done.
>>
>> Gilles Caulier
>>
>> _______________________________________________
>> Digikam-users mailing list
>> Digikam-users at kde.org
>> https://mail.kde.org/mailman/listinfo/digikam-users
>>
>>
>
> _______________________________________________
> Digikam-users mailing list
> Digikam-users at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-users
>
>


-- 
Une galerie photos, un blog ... pourquoi pas ? Webmaster en
herbe<http://www.webmaster-en-herbe.net/>

Parcourez les Cévennes à ma façon : Cévennes
Plurielles<http://www.cevennes-plurielles.com>

Et toutes mes autres publications à partir de ma page d'accueil
générale<http://www.marie-noelle-augendre.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20110822/8d49c56a/attachment.html>