https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #32 from Loic ---
Maik, Gilles,
Again, thank you for looking into this issue. I carried another series of tests
yesterday and found that crashes only happen if you want to play the video file
on the very first launch of digikam (i.e. when
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #30 from Loic ---
@Maik : I am sending you a link to the Appimage created with FFMpeg 4.3.x
@Gilles, Sorry for my mistake, I was relying on what is written in the
project/bundles/appimage/README file.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=437260
Bug ID: 437260
Summary: Minor discrepancy in scripts
Product: digikam
Version: 7.2.0
Platform: Mageia RPMs
OS: Linux
Status: REPORTED
Severity: minor
P
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #26 from Loic ---
I further digged into this issue and used your infrastructure into
project/bundles/appimage to build an appimage with an updated version of
ffmpeg. Currently the platform you use to build appimages (Mageia 7) ships a
4.1.x
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #25 from Loic ---
Created attachment 138393
--> https://bugs.kde.org/attachment.cgi?id=138393&action=edit
test files
Thanks for following this issue. I don't know what to say more. You dont'have
crashes, I do with the sa
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #23 from Loic ---
I've done some further investigations on this issue and found what's going
wrong. Basically, it comes down to the version of ffmpeg libraries used to run
(not necessarily build) digikam, and among the various
https://bugs.kde.org/show_bug.cgi?id=376061
Loic changed:
What|Removed |Added
CC||loickern...@gmail.com
--- Comment #19 from Loic ---
To
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #22 from Loic ---
I built digikam with media player support for fedora 34 and Kde Neon (both of
them disable the functionality by default, or at least do not enable it
correctly). I got the same crash for fedora but everything seems ok on
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #21 from Loic ---
I finally managed to get an up and running opensuse virtual machine. digikam
also crahes in this setup.
So the logical conclusion is that the crash comes from a graphical "layer"
failure of some kind. And I&#
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #19 from Loic ---
I was able to set up an opensuse tumbleweed VMware virtual machine. Now,
despite having set up repos to install packman's versions of ffmpeg, I am
facing an issue with QtAV player not playing .mov files (ffmpegthumbs
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #18 from Loic ---
For the record, my plasma/digikam setup runs on :
1/ a vmware virtual machine runnning on a MacOS host, which shows in Xorg.log
as :
(II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so
(II) Loading
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #15 from Loic ---
Created attachment 137678
--> https://bugs.kde.org/attachment.cgi?id=137678&action=edit
New backtrace after rebuild
I applied your new patch with no success in my crash scenario (i.e. preview a
jpg file and
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #13 from Loic ---
Created attachment 137668
--> https://bugs.kde.org/attachment.cgi?id=137668&action=edit
backtrace after MALLOC_CHECK_ 2
Another observation : I started gdb and set the environment with "set
environment MAL
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #12 from Loic ---
Created attachment 137661
--> https://bugs.kde.org/attachment.cgi?id=137661&action=edit
New backtrace after patch
Thank you Maik. I built DigiKam with your patch and had a positive result in
the fact that pre
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #9 from Loic ---
Thank you for your explanations, but I struggle to understand why all files
play nicely with the QtQV standalone player and not when played by the QtAV
framework through digikam. This seems to indicate QtAV framework and
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #7 from Loic ---
Here is the version dump :
digikam version 7.2.0
CPU cores: 2
Eigen: 3.3.9
Exiv2: 0.27.3
Exiv2 supports Base Media: Non
Exiv2 supports XMP metadata: Oui
HEIF encoding support: Oui
ImageMagick codecs: 7.0.11
KF5: 5.80.0
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #5 from Loic ---
Created attachment 137544
--> https://bugs.kde.org/attachment.cgi?id=137544&action=edit
gdb backtrace
I did not include this also...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #4 from Loic ---
Created attachment 137543
--> https://bugs.kde.org/attachment.cgi?id=137543&action=edit
crash gdb log
Sorry, I'm not very familiar with these procedures. I hope this is what you are
looking for. If not,
https://bugs.kde.org/show_bug.cgi?id=435660
Loic changed:
What|Removed |Added
CC||loickern...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #2 from Loic ---
Created attachment 137534
--> https://bugs.kde.org/attachment.cgi?id=137534&action=edit
crash console log
You will find attached a log of my "scenario 2" kind of crash.
In the meantime, I investigated
https://bugs.kde.org/show_bug.cgi?id=435660
Bug ID: 435660
Summary: Strange crashes when previewing .MOV files
Product: digikam
Version: 7.2.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severi
21 matches
Mail list logo
