[digiKam-users] DigiKam not responding

[Gilles Caulier]

Le lun. 20 mars 2023 à 08:48, Nadine Helkenn <cnhelkenn at comcast.net> a écrit :
>
>
>
> ________________________________
> From: Digikam-users <digikam-users-bounces at kde.org> on behalf of Gilles Caulier <caulier.gilles at gmail.com>
> Sent: Sunday, March 19, 2023 11:05 PM
> To: digikam-users at kde.org <digikam-users at kde.org>
> Subject: Re: [digiKam-users] DigiKam not responding
>
> 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 ?
>
> -- the SSD is the primary system drive
>
> 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 ?
>
> -- after I noticed issues with not responding, I downloaded and installed the official 7.9.0 from digikam.org. This replaced 7.7.0. When you requested the log files, I downloaded and installed the debug version of 7.9.0 from digikam.org. I have not done anything with 8.0.0.
>
> >
> > 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.
>
> -- as stated above, that has been done twice now.
>
> For the config file (which is a text INI file), did you backup all
> files listed in online doc :
>
> -- is this the digikamrc file?

yes it is...

Have you seen the previous mail from Maik. The mess in the digikamrc
file is due to a bug from a KDE library that we use in the background.
This have been fixed
now with the last stable release published.

You can open this file in a text editor. It's a simple INI format with
plenty of sections and parameters inside. The file is huge but human
readable.

Please copy and paste the contents from this file at lines given in
startup traces, eg. :

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\"."

It will be easy to double check the content to see if your DK
dysfunction is relevant to these settings.


Gilles