Problem with starting digiKam 5.4.0

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Problem with starting digiKam 5.4.0

Markwart Lindenthal
Happy Easter!

Please excuse my lousy English – I am over 70, that means school English
has gone since mor than half a century.

I liked to work with digiKam – I should better say: digiKam worked for
me for some years, with about 50 000 pictures. But it was interrupted
long time ago.

When starting it now, it asks for Drive A:, put a disk in it and close.
That's all, it does not run.

Drive A: never had been working in my PC. But I have an external
3½"-drive A: with cable and USB2. Nevertheless digiKam is not ready to
go, even after de- and newly re-installation.

Is there anyone able to help me getting started?

It would be a fine easter-gift for me.

Thanks and greetings from Markwart Lindenthal.



EPL-0113.png (327K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Problem with starting digiKam 5.4.0

Markwart Lindenthal
Please excuse my lousy English – I am over 70, that means school English
has gone since more than half a century.

I liked to work with digiKam – I should better say: digiKam worked for
me for some years, with about 50 000 pictures. But it was interrupted
long time ago.

When starting it now, it asks for Drive A:, put a disk in it and close.
That's all, it does not run.

Drive A: never had been working in my PC. But I have an external
3½"-drive A: with cable and USB2. Nevertheless digiKam is not ready to
go, even after de- and newly re-installation.

Is there anyone able to help me getting started?

It would be a fine after-easter-gift for me.

Thanks and greetings from Markwart Lindenthal.



Reply | Threaded
Open this post in threaded view
|

Re: Problem with starting digiKam 5.4.0

Gilles Caulier-4
Somebody has already reported this problem few week ago. I think it's relevant of KF5::Solid interface from KDE which handle devices.

Try to use new 5.5.0 available at usual download page or the pre-release installer 5.6.0 when Solid have been updated :


Gilles Caulier

2017-04-20 17:50 GMT+02:00 Markwart Lindenthal <[hidden email]>:
Please excuse my lousy English – I am over 70, that means school English
has gone since more than half a century.

I liked to work with digiKam – I should better say: digiKam worked for
me for some years, with about 50 000 pictures. But it was interrupted
long time ago.

When starting it now, it asks for Drive A:, put a disk in it and close.
That's all, it does not run.

Drive A: never had been working in my PC. But I have an external
3½"-drive A: with cable and USB2. Nevertheless digiKam is not ready to
go, even after de- and newly re-installation.

Is there anyone able to help me getting started?

It would be a fine after-easter-gift for me.

Thanks and greetings from Markwart Lindenthal.




Reply | Threaded
Open this post in threaded view
|

Re: Problem with starting digiKam 5.4.0

Markwart Lindenthal

Dear Gilles Caulier!
Many thanks for your very quick response.
But unluckyly both new installations (at first the v 5.6.0 of your link, afterwards v 5.5.0 via "Chip") failed, the failure-message is "Drive A: not found" occurs even now.

How could I try to update "Solid"? Might this bring the solution?

Another question is: where does digikam store its databases? are they in folder .../digikam/database? I would like to save digiKams datafiles and afterwards de-install the whole program and sweep off all the programm folders, but would not like to loose the data of nearly 50000 pictures.

Could a complete new installation repair my digiKam?

Best regards! Markwart Lindenthal.

Am 2017-04-20 um 17:56 schrieb Gilles Caulier:
Somebody has already reported this problem few week ago. I think it's relevant of KF5::Solid interface from KDE which handle devices.

Try to use new 5.5.0 available at usual download page or the pre-release installer 5.6.0 when Solid have been updated :


Gilles Caulier

2017-04-20 17:50 GMT+02:00 Markwart Lindenthal <[hidden email]>:
Please excuse my ...

Reply | Threaded
Open this post in threaded view
|

Re: Problem with starting digiKam 5.4.0

Mica Semrick
We were seeing this problem in GTK3 on windows systems with the RawTherapee application as well. The solution in that case was to disable the A: drive in your computer's BIOS/EFI.

-m

On April 20, 2017 1:25:21 PM PDT, Markwart Lindenthal <[hidden email]> wrote:

Dear Gilles Caulier!
Many thanks for your very quick response.
But unluckyly both new installations (at first the v 5.6.0 of your link, afterwards v 5.5.0 via "Chip") failed, the failure-message is "Drive A: not found" occurs even now.

How could I try to update "Solid"? Might this bring the solution?

Another question is: where does digikam store its databases? are they in folder .../digikam/database? I would like to save digiKams datafiles and afterwards de-install the whole program and sweep off all the programm folders, but would not like to loose the data of nearly 50000 pictures.

Could a complete new installation repair my digiKam?

Best regards! Markwart Lindenthal.

Am 2017-04-20 um 17:56 schrieb Gilles Caulier:
Somebody has already reported this problem few week ago. I think it's relevant of KF5::Solid interface from KDE which handle devices.

Try to use new 5.5.0 available at usual download page or the pre-release installer 5.6.0 when Solid have been updated :


Gilles Caulier

2017-04-20 17:50 GMT+02:00 Markwart Lindenthal <[hidden email]>:
Please excuse my ...

Reply | Threaded
Open this post in threaded view
|

Re: Problem with starting digiKam 5.4.0

Gilles Caulier-4
In reply to this post by Markwart Lindenthal


2017-04-20 22:25 GMT+02:00 Markwart Lindenthal <[hidden email]>:

Dear Gilles Caulier!
Many thanks for your very quick response.
But unluckyly both new installations (at first the v 5.6.0 of your link, afterwards v 5.5.0 via "Chip") failed, the failure-message is "Drive A: not found" occurs even now.

How could I try to update "Solid"? Might this bring the solution?


You cannot. It's a software component that it's included in DK Windows bundle. I compile myself all dependencies for DK. Solid is one of the huge list.
 

Another question is: where does digikam store its databases?


Where you said to DK to store it. Look in DK/setup/database. There is a path to configure it.
In this folder you will found  .db files which are sqlite database : one for the image proerties, one for thumbnaisl, and one for face tags.

Gilles Caulier
Reply | Threaded
Open this post in threaded view
|

Re: Problem with starting digiKam 5.4.0

Gilles Caulier-4
In reply to this post by Mica Semrick
This is certainly the best way to fix the A: problem. After all A: drive is definitively obsolete now (:=)))...

Gilles Caulier

2017-04-20 23:03 GMT+02:00 Mica Semrick <[hidden email]>:
We were seeing this problem in GTK3 on windows systems with the RawTherapee application as well. The solution in that case was to disable the A: drive in your computer's BIOS/EFI.

-m


On April 20, 2017 1:25:21 PM PDT, Markwart Lindenthal <[hidden email]> wrote:

Dear Gilles Caulier!
Many thanks for your very quick response.
But unluckyly both new installations (at first the v 5.6.0 of your link, afterwards v 5.5.0 via "Chip") failed, the failure-message is "Drive A: not found" occurs even now.

How could I try to update "Solid"? Might this bring the solution?

Another question is: where does digikam store its databases? are they in folder .../digikam/database? I would like to save digiKams datafiles and afterwards de-install the whole program and sweep off all the programm folders, but would not like to loose the data of nearly 50000 pictures.

Could a complete new installation repair my digiKam?

Best regards! Markwart Lindenthal.

Am 2017-04-20 um 17:56 schrieb Gilles Caulier:
Somebody has already reported this problem few week ago. I think it's relevant of KF5::Solid interface from KDE which handle devices.

Try to use new 5.5.0 available at usual download page or the pre-release installer 5.6.0 when Solid have been updated :


Gilles Caulier

2017-04-20 17:50 GMT+02:00 Markwart Lindenthal <[hidden email]>:
Please excuse my ...