<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
As Maik suggested, I created a Qt debug log in which I could see an
error message something like<br>
<blockquote>Cannot open configuration file ""<br>
</blockquote>
There was also some text with a similar message followed by
<b></b> (apparently html) where one would have expected
a filename to appear. <br>
<br>
Since digikam would not start, I decided to do another "make
install/fast" from the build directory of the previously compiled
8.5.0 version. Digikam then started without any problem and all of
my collections were visible and intact. I've been using 8.5.0 now
without any more problems. Unfortunately, I didn't save the Qt
debug log file before restarting digikam and mistakenly overwrote
the one having the error message I mentioned above, so I cannot show
the specific error messages.<br>
<br>
I haven't yet experienced any lost database connections, so I can't
report whether that could have been the source of my original
problem. I don't do "standby" or "sleep" when I leave my laptop for
the night. All I do is let the screen lock automatically, but
network connections remain active.<br>
<br>
Jim<br>
<br>
<div class="moz-cite-prefix">On 10/13/24 03:16, <a
class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:leoutation@gmx.fr" moz-do-not-send="true">leoutation@gmx.fr</a>
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:105da744-e3bb-4d27-a775-6dda519c56e3@gmx.fr"> I didn't
notice any problem with Mariadb (external server) and <br>
digikam git versions compiled on my Arch Linux system. It works
fine, <br>
much faster than before. <br>
<br>
<br>
On 10/12/24 10:04 PM, Maik Qualmann wrote: <br>
<blockquote type="cite">There are no known problems with
digiKam-8.5.0 and MySQL. There are also no <br>
relevant changes between digiKam-8.4.0 and 8.5.0 in the database
interface. I <br>
am using digikam-8.5.0 with MySQL and SQLite. It is a known
problem that the <br>
database connection is lost during standby. <br>
</blockquote>
> To identify the problem, create a Qt debug log as described
here:> <br>
<blockquote type="cite"><a class="moz-txt-link-freetext"
href="https://www.digikam.org/contribute/"
moz-do-not-send="true">https://www.digikam.org/contribute/</a>
<br>
<br>
Maik <br>
<br>
Am Samstag, 12. Oktober 2024, 20:57:25 MESZ schrieb Jim Cunning:
<br>
<blockquote type="cite">Hello, <br>
<br>
I had been using a locally compiled copy of 8.2 for some time,
but wanted to <br>
update to a later version. Without paying enough attention, I
downloaded <br>
the development version (8.5.0) from the git repository
instead of the <br>
latest official release (8.4.0). It compiled without problem,
and I began <br>
using it to modify the DateTimeOriginal metadata of some
scanned images <br>
from the date scanned to the actual event date of the images.
<br>
<br>
I had modified quite a few images and left the application up
at the end of <br>
the day, intending to resume the next morning. The next day
when I clicked <br>
Apply in the Edit Metadata window for the image that had been
open the <br>
previous evening, there was a brief delay and then an error
message <br>
indicating a problem connecting to the MySQL server (as I
recall anyway). <br>
I tried to exit and restart digikam, but got an error message
window with <br>
"Could not open the configuration file. ..... Please check
the database <br>
settings in this dialog." <br>
<br>
Concerned I may have lost a lot of work on my collections, I
created backups <br>
then renamed the digikamrc file and restarted, entering the
same <br>
configuration parameters as before. The program again
displayed the same <br>
error window and would not proceed. I then downloaded the
8.4.0 appimage <br>
and was able to open all the existing albums with no apparent
loss of <br>
data. I am continuing to use 8.4.0 appimage, and 8.5.0 still
refuses to <br>
start with the same configuration file. <br>
<br>
The 8.5.0 git repository has probably changed since I
downloaded it. The <br>
last commit in the version I have is: <br>
<br>
commit b2981ed41e43ab2ad9305e19b129fb11b335384d (HEAD ->
master, <br>
origin/master, origin/HEAD) <br>
Author: Gilles Caulier <a class="moz-txt-link-rfc2396E"
href="mailto:caulier.gilles@gmail.com"
moz-do-not-send="true"><caulier.gilles@gmail.com></a>
<br>
Date: Sat Sep 28 13:50:30 2024 +0200 <br>
<br>
I don't know what information I could provide to assist in
diagnosing this <br>
problem other than this: <br>
<br>
Client: Linux Ubuntu 24.04.1 LTS <br>
Remote: Debian GNU/Linux 10 (buster) <br>
<br>
Database: Ver 15.1 Distrib 10.3.39-MariaDB, for
debian-linux-gnu (x86_64) <br>
using readline 5.2 I am content to continue with 8.4.0, but
would like to <br>
help resolve what is happening with 8.5.0, if possible. <br>
<br>
Jim Cunning <br>
</blockquote>
<br>
<br>
<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>