Bug 452508 - Components information crashes digikam
Summary: Components information crashes digikam
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Portability-Runtime (show other bugs)
Version: 7.7.0
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-11 16:07 UTC by Steve Franks
Modified: 2022-06-22 09:05 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.7.0


Attachments
Debugview log (82.02 KB, text/plain)
2022-04-11 16:07 UTC, Steve Franks
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Franks 2022-04-11 16:07:59 UTC
Created attachment 148100 [details]
Debugview log

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Windows 11 digikam crashes when Components information is selected.

STEPS TO REPRODUCE
1.  Start digikam
2.  Click on Help, then Components information
3. 

OBSERVED RESULT
digikam disappears

EXPECTED RESULT
Components information is displayed

SOFTWARE/OS VERSIONS
Windows:  11
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version:  5.15.2

ADDITIONAL INFORMATION
Help | About | Components does not cause crash.
Comment 1 caulier.gilles 2022-04-11 16:21:56 UTC
This must probably crash in KF5::Solid API to discover hardware under Windows.

Can you tell me if this file exist : C:\\Users\\steve\\AppData\\Local\\digikam_crash.log

If yes, please report the contents here.

Gilles Caulier
Comment 2 Maik Qualmann 2022-04-11 18:17:04 UTC
I can confirm the crash. Unfortunately no crash log. Which is probably also due to the fact that the debug version is the same size as the normal version. In the debug version, the debug symbols will probably also be removed.

Maik
Comment 3 Maik Qualmann 2022-04-11 18:33:11 UTC
The component information in digiKam-7.6.0 does not crash.

Maik
Comment 4 Steve Franks 2022-04-12 11:26:40 UTC
I agree with Maik, no crash log
Comment 5 Maik Qualmann 2022-04-13 06:29:23 UTC
Git commit 0ceb59b31c4249e4b3c42af7e64cd5249c93d6d3 by Maik Qualmann.
Committed on 13/04/2022 at 06:28.
Pushed by mqualmann into branch 'qt5-maintenance'.

try to fix crash and correct the Audio Decoders display

M  +9    -6    core/app/views/utils/componentsinfodlg.cpp
M  +1    -1    core/libs/video/helper/ffmpegconfighelper.cpp

https://invent.kde.org/graphics/digikam/commit/0ceb59b31c4249e4b3c42af7e64cd5249c93d6d3
Comment 6 Maik Qualmann 2022-04-19 20:59:36 UTC
Git commit cd69f5d6ddc00be8171d5b2e7b370cbca1cb9626 by Maik Qualmann.
Committed on 19/04/2022 at 20:58.
Pushed by mqualmann into branch 'qt5-maintenance'.

next try to fix crash in the component dialog

M  +6    -1    core/app/views/utils/componentsinfodlg.cpp

https://invent.kde.org/graphics/digikam/commit/cd69f5d6ddc00be8171d5b2e7b370cbca1cb9626
Comment 7 Maik Qualmann 2022-06-21 06:17:15 UTC
Git commit c3023a64cdc654f24255de0462557acc1837a771 by Maik Qualmann.
Committed on 21/06/2022 at 06:16.
Pushed by mqualmann into branch 'qt5-maintenance'.

try to fix crash in the components dialog

M  +11   -2    core/libs/dialogs/libsinfodlg.cpp

https://invent.kde.org/graphics/digikam/commit/c3023a64cdc654f24255de0462557acc1837a771
Comment 8 Maik Qualmann 2022-06-21 17:28:07 UTC
Git commit 84f3de6b55f51f2bbe1044f0deb337c36af11c93 by Maik Qualmann.
Committed on 21/06/2022 at 17:27.
Pushed by mqualmann into branch 'qt5-maintenance'.

use libx265 api to get the version

M  +4    -10   core/libs/dialogs/libsinfodlg.cpp

https://invent.kde.org/graphics/digikam/commit/84f3de6b55f51f2bbe1044f0deb337c36af11c93
Comment 9 Maik Qualmann 2022-06-22 08:46:48 UTC
The crash in the component dialog is now fixed.
As a note, the MXE team is using a legacy libx265 repository.

Here's why the static version variable doesn't always exist, from the doc:

**x265_version_str** is only updated when **cmake** runs. If you are
making binaries for others to use, it is recommended to run
**cmake** prior to **make** in your build scripts.

Maik



Maik