[digiKam-users] DigiKam not responding

[Maik Qualmann]

The wrong entries in the config file come from an (older) KXMLGui. When writing 
window positions, the monitor name and more should be used. Since the monitor 
device names were not always resolved under Windows, but also under Wayland, 
the sprintf placeholders were written as config keys.

Some plugins not loading looks like a mix of digiKam-7/8 in the system.

Maik

Am Montag, 20. März 2023, 07:04:43 CET schrieb Gilles Caulier:
> Le lun. 20 mars 2023 à 01:32, Nadine Helkenn <cnhelkenn at comcast.net> a écrit 
:
> > Thank you, Gilles
> > 
> > All of those files are on an SSD that does not appear to have any
> > failures. My virus protection is up to date. But no matter.
> The SSD is a removable one or installed on your computer ?
> 
> Did you install more than one digiKam version on your computer ? didi
> you use only the official installer from the 7.x digiKam.org web site
> or did you try the 8.0.0 pre release installer ?
> 
> > The question now is how do I recover or replace those files to make it
> > work again?
> For the binary files, a re-install of digiKam must solve the problem
> if the same location is used to install and replace the old one.
> 
> For the config file (which is a text INI file), did you backup all
> files listed in online doc :
> 
> https://docs.digikam.org/en/getting_started/installation.html#configuration-> files
> 
> If not, do it, and send me by mail an archive for investigation.
> 
> > You are a treasure,
> 
> (:=)))
> Best regards
> 
> Gilles
> 
> > Nadine H
> > 
> > ________________________________
> > From: Digikam-users <digikam-users-bounces at kde.org> on behalf of Gilles
> > Caulier <caulier.gilles at gmail.com> Sent: Sunday, March 19, 2023 3:02 PM
> > To: digikam-users at kde.org <digikam-users at kde.org>
> > Subject: Re: [digiKam-users] DigiKam not responding
> > 
> > Hi,
> > 
> > I see 2 problems from the log. first one is the most important:
> > 
> > 00000025 297.93386841 [3132] kf.config.core: "KConfigIni: In
> > file C:/Users/Mom/AppData/Local/digikamrc, line 1296: " "Invalid
> > escape sequence \"\\D\"."
> > 00000026 297.93399048 [3132] kf.config.core: "KConfigIni: In
> > file C:/Users/Mom/AppData/Local/digikamrc, line 1334: " "Invalid
> > escape sequence \"\\.\"."
> > 00000027 297.93405151 [3132] kf.config.core: "KConfigIni: In
> > file C:/Users/Mom/AppData/Local/digikamrc, line 1334: " "Invalid
> > escape sequence \"\\I\"."
> > 00000028 297.93411255 [3132] kf.config.core: "KConfigIni: In
> > file C:/Users/Mom/AppData/Local/digikamrc, line 1335: " "Invalid
> > escape sequence \"\\S\"."
> > 00000029 1974.45385742 [3132] kf.config.core: "KConfigIni: In
> > file C:/Users/Mom/AppData/Local/digikamrc, line 1294: " "Invalid
> > escape sequence \"\\D\"."
> > 00000030 1974.45385742 [3132] kf.config.core: "KConfigIni: In
> > file C:/Users/Mom/AppData/Local/digikamrc, line 1296: " "Invalid
> > escape sequence \"\\D\"."
> > 00000031 1974.45385742 [3132] kf.config.core: "KConfigIni: In
> > file C:/Users/Mom/AppData/Local/digikamrc, line 1299: " "Invalid
> > escape sequence \"\\D\"."
> > 00000032 1974.45410156 [3132] kf.config.core: "KConfigIni: In
> > file C:/Users/Mom/AppData/Local/digikamrc, line 1301: " "Invalid
> > escape sequence \"\\D\"."
> > 00000033 1974.45410156 [3132] kf.config.core: "KConfigIni: In
> > file C:/Users/Mom/AppData/Local/digikamrc, line 1337: " "Invalid
> > escape sequence \"\\.\"."
> > 00000034 1974.45422363 [3132] kf.config.core: "KConfigIni: In
> > file C:/Users/Mom/AppData/Local/digikamrc, line 1337: " "Invalid
> > escape sequence \"\\I\"."
> > 00000035 1974.45422363 [3132] kf.config.core: "KConfigIni: In
> > file C:/Users/Mom/AppData/Local/digikamrc, line 1338: " "Invalid
> > escape sequence \"\\P\"."
> > Your digikamrc file is corrupted. this one hosts all settings,
> > including the collections. I don't know how you arrives at this stage,
> > but this can explain why digiKam fails to run.
> > 
> > Look also the second one :
> > 
> > 00000004 4.03615141 [3132] digikam.general: Ignoring to load the
> > following file since it doesn't look like a valid digiKam external
> > plugin: "C:/Program
> > Files/digiKam/plugins/digikam/bqm/Bqm_Assigncaptions_Plugin.dll"
> > 00000005 4.03615141 [3132] Reason: "Cannot load library
> > C:\\Program
> > Files\\digiKam\\plugins\\digikam\\bqm\\Bqm_Assigncaptions_Plugin.dll: The
> > specified procedure could not be found."
> > 00000006 4.06181002 [3132] digikam.general: Ignoring to load the
> > following file since it doesn't look like a valid digiKam external
> > plugin: "C:/Program
> > Files/digiKam/plugins/digikam/bqm/Bqm_AssignLabels_Plugin.dll"
> > 00000007 4.06181002 [3132] Reason: "Cannot load library
> > C:\\Program
> > Files\\digiKam\\plugins\\digikam\\bqm\\Bqm_AssignLabels_Plugin.dll: The
> > specified procedure could not be found."
> > 00000008 4.37046480 [3132] digikam.general: Ignoring to load the
> > following file since it doesn't look like a valid digiKam external
> > plugin: "C:/Program
> > Files/digiKam/plugins/digikam/bqm/Bqm_ConvertToAVIF_Plugin.dll"
> > 00000009 4.37046480 [3132] Reason: "Cannot load library
> > C:\\Program
> > Files\\digiKam\\plugins\\digikam\\bqm\\Bqm_ConvertToAVIF_Plugin.dll: The
> > specified procedure could not be found."
> > 00000010 4.50869894 [3132] digikam.general: Ignoring to load the
> > following file since it doesn't look like a valid digiKam external
> > plugin: "C:/Program
> > Files/digiKam/plugins/digikam/bqm/Bqm_ConvertToJXL_Plugin.dll"
> > 00000011 4.50869894 [3132] Reason: "Cannot load library
> > C:\\Program
> > Files\\digiKam\\plugins\\digikam\\bqm\\Bqm_ConvertToJXL_Plugin.dll: The
> > specified procedure could not be found."
> > 00000012 4.62113047 [3132] digikam.general: Ignoring to load the
> > following file since it doesn't look like a valid digiKam external
> > plugin: "C:/Program
> > Files/digiKam/plugins/digikam/bqm/Bqm_ConvertToWEBP_Plugin.dll"
> > 00000013 4.62113047 [3132] Reason: "Cannot load library
> > C:\\Program
> > Files\\digiKam\\plugins\\digikam\\bqm\\Bqm_ConvertToWEBP_Plugin.dll: The
> > specified procedure could not be found."
> > 00000014 4.92783213 [3132] digikam.general: Ignoring to load the
> > following file since it doesn't look like a valid digiKam external
> > plugin: "C:/Program
> > Files/digiKam/plugins/digikam/bqm/Bqm_QualitySort_Plugin.dll"
> > 00000015 4.92783213 [3132] Reason: "Cannot load library
> > C:\\Program
> > Files\\digiKam\\plugins\\digikam\\bqm\\Bqm_QualitySort_Plugin.dll: The
> > specified procedure could not be found."
> > 00000016 5.15791130 [3132] digikam.general: Ignoring to load the
> > following file since it doesn't look like a valid digiKam external
> > plugin: "C:/Program
> > Files/digiKam/plugins/digikam/bqm/Bqm_Translate_Plugin.dll"
> > 00000017 5.15791130 [3132] Reason: "Cannot load library
> > C:\\Program
> > Files\\digiKam\\plugins\\digikam\\bqm\\Bqm_Translate_Plugindll:
> > The specified procedure could not be found."
> > 00000018 7.84661818 [3132] digikam.general: Ignoring to load the
> > following file since it doesn't look like a valid digiKam external
> > plugin: "C:/Program
> > Files/digiKam/plugins/digikam/generic/Generic_TextConverter_Plugin.dll"
> > 00000019 7.84661818 [3132] Reason: "Cannot load library
> > C:\\Program
> > Files\\digiKam\\plugins\\digikam\\generic\\Generic_TextConverter_Plugin.d
> > ll: The specified procedure could not be found."
> > 
> > plugins binary files from digiKam are corrupted. How is it possible ?
> > Hard drive failure ? virus ???
> > 
> > Best
> > 
> > Gilles Caulier
> > 
> > Le dim. 19 mars 2023 à 20:18, Nadine Helkenn <cnhelkenn at comcastnet> a 
écrit :
> > > Did the file not come through?
> > > 
> > > I try again.
> > > 
> > > Nadine H
> > > 
> > > ________________________________
> > > From: Gilles Caulier <caulier.gilles at gmail.com>
> > > Sent: Sunday, March 19, 2023 2:06 AM
> > > To: Nadine Helkenn <cnhelkenn at comcast.net>
> > > Cc: digikam-users at kde.org <digikam-users at kdeorg>
> > > Subject: Re: [digiKam-users] DigiKam not responding
> > > 
> > > Hi Nadine,
> > > 
> > > Download the "DebugView" program from Microsoft. This is what i mean.
> > > 
> > > Run it before digiKam to catch debug traces from the application. It's
> > > explained on the "contribute" page from the project, in the "Freezes
> > > and Other Run-Time Issues/Windows" section...
> > > 
> > > Gilles Caulier
> > > 
> > > Le dim. 19 mars 2023 à 10:02, Nadine Helkenn <cnhelkenn at comcastnet> a 
écrit :
> > > > Hi, Gilles,
> > > > 
> > > > I hope I have done this correctly.
> > > > 
> > > > I have downloaded & installed the debug version of DigiKam 7.90 & done
> > > > the same with DebugView.
> > > > 
> > > > It doesn't seem to matter what operation I request. In this case it
> > > > was just to assign a color label to an image. It is a .tif scan of a
> > > > drawing. The progress bar stays at 0% & I have to force close
> > > > DigiKam.
> > > > 
> > > > Let me know what else I need to do.
> > > > 
> > > > The log file just confuses me.
> > > > 
> > > > Thank you, Gilles
> > > > 
> > > > Nadine H
> > > > 
> > > > ________________________________
> > > > From: Digikam-users <digikam-users-bounces at kde.org> on behalf of
> > > > Gilles Caulier <caulier.gilles at gmail.com> Sent: Sunday, March 19,
> > > > 2023 1:11 AM
> > > > To: digikam-users at kde.org <digikam-users at kde.org>
> > > > Subject: Re: [digiKam-users] DigiKam not responding
> > > > 
> > > > Hi,
> > > > 
> > > > It sounds like the metadata writing pipeline is locked somewhere.
> > > > Which kind of files do you want to tag exactly ?
> > > > 
> > > > Also, we need to see the debug traces done in background while tag
> > > > operation. download Microsoft DebugView program, and run it before the
> > > > digiKam session. See here for details :
> > > > 
> > > > https://www.digikam.org/contribute/
> > > > 
> > > > Best
> > > > 
> > > > Gilles Caulier
> > > > 
> > > > Le dim. 19 mars 2023 à 01:42, Nadine Helkenn <cnhelkenn at comcastnet> a 
écrit :
> > > > > 18 March 2023
> > > > > 
> > > > > 
> > > > > All right. I've broken DigiKam once again.
> > > > > 
> > > > > 
> > > > > I wish I knew how I do this so I can avoid doing it. It has been
> > > > > more than a year since the last time it broke, and I can't remember
> > > > > how to fix it. And I don't think it broke the same way.
> > > > > 
> > > > > 
> > > > > I'm working in Windows 10 using SQLite. I recently updated from
> > > > > DigiKam 7.7.0 to 7.9.0 to see if that would fix the problem. It did
> > > > > not. I had to manually update exiftool from 12.42 to 12.58.
> > > > > 
> > > > > 
> > > > > Symptom: adding tags to images appears to work, but the progress bar
> > > > > for "Writing metadata to file:" stays at 0% and never finishes
> > > > > Thumbnail images don't display. Images can be seen in preview.
> > > > > DigiKam app says it is not responding.
> > > > > 
> > > > > 
> > > > > Efforts: rebooted Windows. Restored database files to previous
> > > > > version (only two days ago was available).
> > > > > 
> > > > > 
> > > > > Have I corrupted the database files? Can I get Digikam to rebuild
> > > > > them? Are all 4-5 of them compromised? What is my best course of
> > > > > action?
> > > > > 
> > > > > 
> > > > > Thanks for all of your collective knowledge & assistance.
> > > > > 
> > > > > Nadine H