Created attachment 173520 [details] Configure dialog after finding MariaDB *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY I've installed MariaDB (11.4 or 11.1) on a new Windows 11 PC. When I start digikam 8.5.0 and configure it to use MySQL Internal database, using MariaDB, the settings are wiped when I exit the configure dialog. STEPS TO REPRODUCE 1. Install MariaDB. 2. Configure digikam to use MySQL Internal database, using the installed MariaDB programs. 3. Exit configure dialog. OBSERVED RESULT Entering settings again shows 'No entry' icons against the MariaDB programs. digikam scans photos and shows the new album and its folders, then starts to scan for new items. After a time the progress bar stills shows zero progress and no items are shown in the album(s). EXPECTED RESULT Scan shows images in the album's folders. SOFTWARE/OS VERSIONS Windows: 11 Home macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: 6.2.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION I deleted the digikam database and digikamrc and started digikam afresh. It appears to be working, but of course I've lost all of my data.
Hi steve, There is a Qt5 version of the Windows installer. It works better than the Qt6 ? https://files.kde.org/digikam/legacy/ Best Gilles
It's only "cosmetic" that after calling the dialog for the second time the MariaDB files are shown as not found. It still works. The reason is that every Maria version in the path has the version number and we are only looking for a specific version. I will fix the problem, deleting the DB and config was completely unnecessary. Maik
Created attachment 173523 [details] attachment-246200-0.html I left the 'Find new items' process running for several hours yesterday and half an hour, or so, this morning. No new items had been added to the database. Once I reverted to MariaDB 11.1 and a new database the system started running as expected. I tried to produce a debug, but my stupid antivirus blocked Sysinternals from installing. Thanks for your response, Steve On Tue, 10 Sept 2024 at 11:27, Maik Qualmann <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=492937 > > Maik Qualmann <metzpinguin@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |metzpinguin@gmail.com > Severity|critical |normal > > --- Comment #2 from Maik Qualmann <metzpinguin@gmail.com> --- > It's only "cosmetic" that after calling the dialog for the second time the > MariaDB files are shown as not found. It still works. The reason is that > every > Maria version in the path has the version number and we are only looking > for a > specific version. I will fix the problem, deleting the DB and config was > completely unnecessary. > > Maik > > -- > You are receiving this mail because: > You reported the bug.
Git commit 20427ec97b62f482030a9ae1320ee618d850ea49 by Maik Qualmann. Committed on 10/09/2024 at 19:32. Pushed by mqualmann into branch 'master'. fix found status view of mariaDB binary files in setup M +5 -5 core/libs/database/utils/widgets/dbsettingswidget.cpp https://invent.kde.org/graphics/digikam/-/commit/20427ec97b62f482030a9ae1320ee618d850ea49
I will do another test with MariaDB-11.4 under Windows tomorrow, but digiKam-8.5.0 still works without problems with MariaDB-10.x. Maik
Created attachment 173548 [details] attachment-447428-0.html Ok, thanks. It’s working with 11.1 now. Steve On Tue, 10 Sep 2024 at 20:39, Maik Qualmann <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=492937 > > --- Comment #5 from Maik Qualmann <metzpinguin@gmail.com> --- > I will do another test with MariaDB-11.4 under Windows tomorrow, but > digiKam-8.5.0 still works without problems with MariaDB-10.x. > > Maik > > -- > You are receiving this mail because: > You reported the bug.
The binary status found is now displayed correctly. A test with MariaDB-11.4 shows no problems, the MariaDB upgrade is carried out correctly and digiKam runs with this long-term version of MariaDB. I'll close here now, if problems occur, reopen the bug. Maik
Created attachment 173587 [details] attachment-860588-0.html Ok. I will try 11.4 again. Do I need to install the latest prerelease? Thanks Steve On Thu, 12 Sep 2024 at 06:51, Maik Qualmann <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=492937 > > Maik Qualmann <metzpinguin@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Version Fixed In| |8.5.0 > Resolution|--- |FIXED > Status|REPORTED |RESOLVED > > --- Comment #7 from Maik Qualmann <metzpinguin@gmail.com> --- > The binary status found is now displayed correctly. A test with > MariaDB-11.4 > shows no problems, the MariaDB upgrade is carried out correctly and digiKam > runs with this long-term version of MariaDB. I'll close here now, if > problems > occur, reopen the bug. > > Maik > > -- > You are receiving this mail because: > You reported the bug.
Created attachment 173820 [details] attachment-2877602-0.html I have installed digiKam-8.5.0-20240918T070227-Qt6-Win64-debug and the bug doesn't appea. Thanks Steve On Thu, 12 Sept 2024 at 15:46, Steve Franks <stevef48@gmail.com> wrote: > Ok. I will try 11.4 again. Do I need to install the latest prerelease? > Thanks > Steve > > On Thu, 12 Sep 2024 at 06:51, Maik Qualmann <bugzilla_noreply@kde.org> > wrote: > >> https://bugs.kde.org/show_bug.cgi?id=492937 >> >> Maik Qualmann <metzpinguin@gmail.com> changed: >> >> What |Removed |Added >> >> ---------------------------------------------------------------------------- >> Version Fixed In| |8.5.0 >> Resolution|--- |FIXED >> Status|REPORTED |RESOLVED >> >> --- Comment #7 from Maik Qualmann <metzpinguin@gmail.com> --- >> The binary status found is now displayed correctly. A test with >> MariaDB-11.4 >> shows no problems, the MariaDB upgrade is carried out correctly and >> digiKam >> runs with this long-term version of MariaDB. I'll close here now, if >> problems >> occur, reopen the bug. >> >> Maik >> >> -- >> You are receiving this mail because: >> You reported the bug. > >
great thanks for the feedback