Problem with 8.5.0 locally compiled

[Maik Qualmann]

A local installation is a bit difficult to handle. Some environment variables 
have to be set. The database config file (dbconfig.xml) is not found. Look at the 
bootstrap.local file at the end.

Maik

Am Montag, 14. Oktober 2024, 23:38:27 MESZ schrieb Jim Cunning:
> As Maik suggested, I created a Qt debug log in which I could see an error
> message something like
> 
> Cannot open configuration file ""
> 
> There was also some text with a similar message followed by <b></b>
> (apparently html) where one would have expected a filename to appear. 
> 
> 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.
> 
> 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.
> 
> Jim
> 
> 
> On 10/13/24 03:16, leoutation at gmx.fr wrote:
> 
>  I didn't notice  any problem with Mariadb (external server) and
> digikam git versions compiled on my Arch Linux system. It works fine,
> much faster than before.
> 
> 
> On 10/12/24 10:04 PM, Maik Qualmann wrote:
> 
> There are no known problems with digiKam-8.5.0 and MySQL. There are also no
> relevant changes between digiKam-8.4.0 and 8.5.0 in the database interface.
> I am using digikam-8.5.0 with MySQL and SQLite. It is a known problem that
> the database connection is lost during standby.
> 
> > To identify the problem, create a Qt debug log as described here:>
> 
> https://www.digikam.org/contribute/
> 
> Maik
> 
> Am Samstag, 12. Oktober 2024, 20:57:25 MESZ schrieb Jim Cunning:
> 
> Hello,
> 
> I had been using a locally compiled copy of 8.2 for some time, but wanted to
> update to a later version.  Without paying enough attention, I downloaded
> the development version (8.5.0) from the git repository instead of the
> latest official release (8.4.0).  It compiled without problem, and I began
> using it to modify the DateTimeOriginal metadata of some scanned images
> from the date scanned to the actual event date of the images.
> 
> I had modified quite a few images and left the application up at the end of
> the day, intending to resume the next morning.  The next day when I clicked
> Apply in the Edit Metadata window for the image that had been open the
> previous evening, there was a brief delay and then an error message
> indicating a problem connecting to the MySQL server (as I recall anyway).
> I tried to exit and restart digikam, but got an error message window with
> "Could not open the configuration file.  .....  Please check the database
> settings in this dialog."
> 
> Concerned I may have lost a lot of work on my collections, I created backups
> then renamed the digikamrc file and restarted, entering the same
> configuration parameters as before.  The program again displayed the same
> error window and would not proceed.  I then downloaded the 8.4.0 appimage
> and was able to open all the existing albums with no apparent loss of
> data.  I am continuing to use 8.4.0 appimage, and 8.5.0 still refuses to
> start with the same configuration file.
> 
> The 8.5.0 git repository has probably changed since I downloaded it.  The
> last commit in the version I have is:
> 
> commit b2981ed41e43ab2ad9305e19b129fb11b335384d (HEAD -> master,
> origin/master, origin/HEAD)
> Author: Gilles Caulier <caulier.gilles at gmail.com>
> Date:   Sat Sep 28 13:50:30 2024 +0200
> 
> I don't know what information I could provide to assist in diagnosing this
> problem other than this:
> 
> Client: Linux Ubuntu 24.04.1 LTS
> Remote:  Debian GNU/Linux 10 (buster)
> 
> Database: Ver 15.1 Distrib 10.3.39-MariaDB, for debian-linux-gnu (x86_64)
> using readline 5.2 I am content to continue with 8.4.0, but would like to
> help resolve what is happening with 8.5.0, if possible.
> 
> Jim Cunning