https://bugs.kde.org/show_bug.cgi?id=435660
caulier.gil...@gmail.com changed:
What|Removed |Added
Version Fixed In||8.3.0
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #69 from caulier.gil...@gmail.com ---
@Loic,
What's about this file using current 8.2.0 AppImage Linux bundle ? It's
reproducible ?
https://files.kde.org/digikam/
Thanks in advance
Gilles Caulier
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #68 from caulier.gil...@gmail.com ---
@Loic,
We needs a fresh feedback about this file.
Thanks in advance
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #67 from caulier.gil...@gmail.com ---
@Loic,
digiKam 8.0.0 is out. Problem still reproducible ?
Best regards
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #66 from caulier.gil...@gmail.com ---
Git commit 0e2bc2695efc7d6d0d2ec52731c3f69095554b7f by Gilles Caulier.
Committed on 12/05/2022 at 15:24.
Pushed by cgilles into branch 'master'.
Hide advanced settings for each decoder as nothing is save
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #65 from caulier.gil...@gmail.com ---
Git commit 505bc17cd39702e14446c15d79d44d14d80fe005 by Gilles Caulier.
Committed on 12/05/2022 at 13:56.
Pushed by cgilles into branch 'master'.
Add Setup Video page from digiKam configuration dialog.
Th
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #64 from caulier.gil...@gmail.com ---
Git commit 5aae9b7c21ab662d63b49f165163984809c1d585 by Gilles Caulier.
Committed on 12/05/2022 at 11:10.
Pushed by cgilles into branch 'master'.
Move AVPlayer config widgets to core/QtAV to allow to re-u
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #63 from Jozef Říha ---
Update:
Don't know what happened exactly but currently QtAv's Player plays the file
without issues. Digikam sometimes shows a few frames of the video file,
sometimes it is even play the full video but then it becomes
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #62 from caulier.gil...@gmail.com ---
Jozef,
On QtAv, only 35 files still open as Bugs. The rest are wishes or enhancements.
GilleS Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #61 from caulier.gil...@gmail.com ---
To Jozef,
No it's not a digiKam issue. perhaps a QtAv or more probably a ffmpeg issue due
to hardware acceleration.
Yes a report must be done to QtAV, with the sample mov and the QtAV player
trace in GD
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #60 from Maik Qualmann ---
I don't see any problems with the MOV file on Windows either. Just as a
question in the room, could it also be that ffmpeg uses hardware acceleration
on some computers and that's why there are problems?
ffmpeg -hi
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #59 from Jozef Říha ---
(In reply to caulier.gilles from comment #58)
> If it work for you, well your native package must be compiled with last QtAV
> code from github. It's a DOWNSTREAM bug to report to your Linux distro team.
>
> Gilles C
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #58 from caulier.gil...@gmail.com ---
QtAV 1.13 is older than 2 years...
https://github.com/wang-bin/QtAV/releases/tag/v1.13.0
and it have never been released officially. This is why a prefix -git is
appended.
The code from current Linux A
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #57 from Jozef Říha ---
(In reply to caulier.gilles from comment #56)
> Components Information dialog with qtav + libav versions :
>
> https://i.imgur.com/ddzkUuF.png
Thank you, now I finally see it. It says LibQtAv 1.13.0 (with -git vers
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #56 from caulier.gil...@gmail.com ---
Components Information dialog with qtav + libav versions :
https://i.imgur.com/ddzkUuF.png
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #55 from Jozef Říha ---
(In reply to caulier.gilles from comment #52)
> Hum under Linux, the last backtrace appear with QtAV 1.12.
>
> If i use digiKam 7.6.0 linux AppImage bundle including QtAv rolling release
> code (last one from git rep
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #54 from Maik Qualmann ---
Here under openSUSE Tumbleweed still no problems with the MOV file. Neither
GStreamer bases player nor VLC or digiKam.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #53 from caulier.gil...@gmail.com ---
Oh, nice. Under MacOS, VLC is frozen after to play the MOV file. I must force
to quit from task manager...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #52 from caulier.gil...@gmail.com ---
Hum under Linux, the last backtrace appear with QtAV 1.12.
If i use digiKam 7.6.0 linux AppImage bundle including QtAv rolling release
code (last one from git repository), video is played without crash.
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #51 from caulier.gil...@gmail.com ---
The gdb backtrace of the crash :
digikam.metaengine: ExifToolProcess::readOutput(): ExifTool command completed
digikam.metaengine: ExifTool complete command for action "Load Metadata" with
elasped time (m
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #50 from caulier.gil...@gmail.com ---
Under Linux, with digiKam 7.6.0, i can preview the MOV file, but at end of
preview, digiKam crash :
digikam.metaengine: ExifTool "Load Metadata" "-json -G:0:1:2:4:6 -l
/home/gilles/Images/bug 435660/test
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #49 from caulier.gil...@gmail.com ---
ffmpeg can play the MOV file using ffplay from command line.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #48 from caulier.gil...@gmail.com ---
Report from ffmpeg :
[gilles@localhost testfiles]$ ffmpeg -i vertical.mov
ffmpeg version 4.3.3 Copyright (c) 2000-2021 the FFmpeg developers
built with gcc 10 (Mageia 10.3.0-2.mga8)
configuration: -
https://bugs.kde.org/show_bug.cgi?id=435660
caulier.gil...@gmail.com changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #46 from Jozef Říha ---
(In reply to caulier.gilles from comment #43)
> The problem come from the audio output in your system:
>
> "[ALSOFT] (EE) Failed to set real-time priority for thread: Operation not
> permitted"
>
> Try to search thi
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #45 from caulier.gil...@gmail.com ---
Interesting to read :
https://www.reddit.com/r/archlinux/comments/kfknqr/issue_with_arch_linux_and_using_audio_libs_in_c/
Gilles Caulier
--
You are receiving this mail because:
You are watching all bu
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #44 from caulier.gil...@gmail.com ---
Perhaps there is a solution around ulimit as explained here :
https://stackoverflow.com/questions/10704983/operation-not-permitted-while-setting-new-priority-for-thread
GilleS Caulier
--
You are recei
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #43 from caulier.gil...@gmail.com ---
The problem come from the audio output in your system:
"[ALSOFT] (EE) Failed to set real-time priority for thread: Operation not
permitted"
Try to search this line with google, you will found plenty of
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #42 from Jozef Říha ---
(In reply to caulier.gilles from comment #41)
> Ok.
>
> With your native digiKam package, which libraries version did you use,
> especially ffmpeg libav codecs ?
❯ ldd /usr/bin/digikam | grep -ie libav -e ffmpeg
https://bugs.kde.org/show_bug.cgi?id=435660
caulier.gil...@gmail.com changed:
What|Removed |Added
Version|7.2.0 |7.5.0
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #41 from caulier.gil...@gmail.com ---
Ok.
With your native digiKam package, which libraries version did you use,
especially ffmpeg libav codecs ?
When you run digiKam from a console, reproduce the hang. What do you see as
debug trace on the
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #40 from Jozef Říha ---
(In reply to caulier.gilles from comment #39)
> Loic,
>
> Stable digiKam 7.4.0 is published. Please check if problem is reproducible.
>
> Thanks in advance
>
> Gilles Caulier
Testing with digikam 7.5.0 on Arch Lin
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #39 from caulier.gil...@gmail.com ---
Loic,
Stable digiKam 7.4.0 is published. Please check if problem is reproducible.
Thanks in advance
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #38 from Maik Qualmann ---
Git commit 701855c5455c495bf68b61298344e80828404311 by Maik Qualmann.
Committed on 11/09/2021 at 14:48.
Pushed by mqualmann into branch 'master'.
Use QtAV video output also for the slideshow
Related: bug 382582, b
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #37 from Maik Qualmann ---
Git commit 450d93baf8a059d9e4e0214539bf3810912e0a72 by Maik Qualmann.
Committed on 11/09/2021 at 13:33.
Pushed by mqualmann into branch 'master'.
Use QtAV video output to use hardware acceleration if supported
and
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #36 from Jozef Říha ---
The patched version crashes for me too. But BT looks slightly different (?):
Thread 75 "QtAV::VideoThre" received signal SIGABRT, Aborted.
[Switching to Thread 0x7ffeeaffd640 (LWP 113236)]
0x74f57d22 in raise
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #35 from Maik Qualmann ---
Git commit c9ebd4d03581137d77cc665e183088aff9f1b4ac by Maik Qualmann.
Committed on 21/05/2021 at 06:05.
Pushed by mqualmann into branch 'master'.
try to fix crash in the video slider context
M +1-1core/l
https://bugs.kde.org/show_bug.cgi?id=435660
Maik Qualmann changed:
What|Removed |Added
CC||jose1...@gmail.com
--- Comment #34 from Maik Qu
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #33 from Maik Qualmann ---
I'm linking bug 437328 because both users are using Arch Linux. Both bugs may
be related.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
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 t
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #31 from Maik Qualmann ---
Hi Gilles,
can you test the files from comment 25 on your hardware using the method
described there? I think you should be on FFmpeg-4.3.x already.
Maik
--
You are receiving this mail because:
You are watching
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 becaus
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #29 from caulier.gil...@gmail.com ---
Correction : we don't use Mageia7 to build AppImage, but Mageia6 to preserve
binary compatibility with libc and older Linux distribution.
Mageia7 is used to build the cross compiled version for Windows.
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #28 from Maik Qualmann ---
FFmpeg is used as a metadata parser for video files, i.e. orientation, date,
etc.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #27 from Maik Qualmann ---
I'm on openSUSE Tumbleweed on FFmpeg-4.4.x and have no crashes. The FFmpeg
packages are from Pakman extra repository, as the openSUSE packages are just
"dummies".
Maik
--
You are receiving this mail because:
You
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 same opensuse setup.
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #24 from Maik Qualmann ---
I'm here on FFmpeg-4.4.4 and don't have this problem.
The files under "core/libs/threadimageio/video" have nothing to do with the
video player. These belong to the video thumbnail creator. We use QtAV to play
video
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 libraries, onl
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 Kd
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'm afraid we can
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #20 from Maik Qualmann ---
Yes, you have to switch to Packman for the FFmpeg packages, the openSUSE
packages are more or less dummies. However, Packman packages have been broken
for 2 days after a major openSUSE update. This is rare, but Pac
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 also d
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 /u
https://bugs.kde.org/show_bug.cgi?id=435660
Maik Qualmann changed:
What|Removed |Added
Severity|normal |crash
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #17 from Maik Qualmann ---
Thanks for the test files, but I cannot reproduce the crash. With openSUSE
Tumbleweed, I'm practically on the same level as your component information.
Which graphics card / driver are you using?
Maik
--
You are
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #16 from Maik Qualmann ---
For me the GDB backtraces are not plausible. Since it crashes deep in Qt too. I
also cannot explain to myself why a JPG has to be displayed beforehand. At the
moment I have no explanation for this. Possibly provide
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 then a vertic
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #14 from Maik Qualmann ---
Git commit a109a71df2ede48a5884b9e1f616fa0fad3847d3 by Maik Qualmann.
Committed on 17/04/2021 at 22:12.
Pushed by mqualmann into branch 'master'.
try without locale support
M +8-4core/libs/video/player/m
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 MALLOC_CHECK_ 2".
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 previewing "ver
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #11 from Maik Qualmann ---
Git commit 958126660a7e61417efe42aeaa01c11134c69373 by Maik Qualmann.
Committed on 15/04/2021 at 06:16.
Pushed by mqualmann into branch 'master'.
try to fix crash in the media player
M +15 -2core/libs/vide
https://bugs.kde.org/show_bug.cgi?id=435660
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #10 from Maik
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 cod
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #8 from caulier.gil...@gmail.com ---
The crash is not linked with the Plasma integration of the application.
If it do not crash with the AppImage bundle, it so far a native packaging
problem with your Linux. Typically, a build settings for Q
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
Lens
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #6 from caulier.gil...@gmail.com ---
It crash in QtAV The Qt framework used to play video with ffmpeg codecs.
Which QtAv did you use exactly ? Go to Help/Component info for details.
Also please try to use the digiKam 7.2.0 AppImage Linux bu
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, let me know...
--
https://bugs.kde.org/show_bug.cgi?id=435660
--- Comment #3 from caulier.gil...@gmail.com ---
The trace is just the console output of the program, not the debug trace
generated by gdb. Look well in contribute page, in section "Dealing with
Crashes in digiKam"
Gilles Caulier
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=435660
Loic changed:
What|Removed |Added
CC||loickern...@gmail.com
--
You are receiving this mail be
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 a bit further and f
https://bugs.kde.org/show_bug.cgi?id=435660
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
73 matches
Mail list logo
