Bug 401941 - Beta3 / beta2 launches but hangs... Now fear for DB!
Summary: Beta3 / beta2 launches but hangs... Now fear for DB!
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Mysql (show other bugs)
Version: 6.0.0
Platform: Microsoft Windows Microsoft Windows
: NOR major
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-10 04:04 UTC by dskx
Modified: 2021-02-13 19:22 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.2.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dskx 2018-12-10 04:04:21 UTC
I've been using digikam 6.0 betas all of autumn - and today I downloaded latest beta 3 build - but now for the first time when launching the app digikam hangs- App windows opens and I see my tags and pics but the app goes "not responding" right away when clicking it. restarting it many times not helping - just hangs.

So I downloaded official beta 2 and I see my content in the app but it just keeps hanging no matter what.

Using latest MariaDB 10.3

What is there left to try? Just two days ago I DL'd and installed previous beta 3 build and digikam worked fine. But this most latest beta 3 build is not responding and now I fear losing DB...

What to try to solve?

Windows 10 x64

Edit: when it starts to hang mysql.exe is killed and it's not relaunching until the app is relaunched.... but then it "dies" again and digikam hangs :/
Comment 1 caulier.gilles 2018-12-10 04:27:40 UTC
What did you see as debug traces when your run DebugView program from Microsoft before to run digiKam ?

See here for details :

https://www.digikam.org/contribute/

Gilles Caulier
Comment 2 Maik Qualmann 2018-12-10 11:24:02 UTC
You may also have a problem with Windows Build 1809. Microsoft is already withdrawing the last shipped updates because of problems. On which Windows Build are you?
Especially the last digiKam build I tested intensively on different computers and no problems occurred. Because we made a change from double-click to single-click for the preview.

Maik
Comment 3 caulier.gilles 2018-12-31 11:50:21 UTC
Can you reproduce the dysfunction using the last digiKam 6.0.0-beta3 just
released ?

https://www.digikam.org/news/2018-12-30-6.0.0-beta3_release_announcement/
Comment 4 caulier.gilles 2019-03-07 05:08:15 UTC
Good news,

After 2 weeks of works, the 6.1.0 bundles are now reconstructed from scratch
with:

- All OpenCV options for CUDA, OPenMP, and OPenCL disabled to prevent crashes
in face management.
- A large upgrade of Qt5 from 5.9.7 to 5.11.3.
- An upgrade to KF5 5.55.
- An upgrade to Ffmpeg 3.3.9
- The fontconfig/freetype integration in the bundle to reduce system
dependencies

Files can be downloaded here :

https://files.kde.org/digikam/

Please test and report.

Gilles Caulier
Comment 5 caulier.gilles 2020-01-19 14:50:01 UTC
Dskx,

We need a fresh feedback using current digiKam 7.0.0-beta2 :

https://files.kde.org/digikam/

Gilles Caulier
Comment 6 caulier.gilles 2020-07-14 09:41:29 UTC
Hi,

Can you check if this problem still exist with last weekly bundle build of digiKam 7.0.0 available here:

https://files.kde.org/digikam/

Thanks in advance

Gilles Caulier
Comment 7 caulier.gilles 2020-07-30 09:45:11 UTC
digiKam 7.0.0 stable release is now published:

https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/

We need a fresh feedback on this file using this version.

Thanks in advance

Gilles Caulier
Comment 8 Maik Qualmann 2021-02-13 19:22:51 UTC
This problem cannot be reproduced with digiKam-7.2.0 under Windows. I close the bug.

Maik