Bug 468642 - Render crash (after "sudo flatpak update") -- !! Fixed with new flatpak update (org.kde.Platform/x86_64/5.15-22.08 flathub && 1fb61aab6f87 org.kde.Platform.Locale/x86_64/5.15-22.08 flathub fcb99ae174f9) !!
Summary: Render crash (after "sudo flatpak update") -- !! Fixed with new flatpak updat...
Status: RESOLVED FIXED
Alias: None
Product: kdenlive
Classification: Applications
Component: Rendering & Export (show other bugs)
Version: 22.12.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-04-18 10:54 UTC by fehler-im-programm
Modified: 2023-05-14 18:00 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description fehler-im-programm 2023-04-18 10:54:24 UTC 
Rendern von /home/xxx/Schreibtisch/test.mp4 abgestürzt

qt.gui.icc: fromIccProfile: failed minimal tag size sanity
[AVHWDeviceContext @ 0x7f5788204d80] libva: /usr/lib/x86_64-linux-gnu/dri/intel-vaapi-driver/iHD_drv_video.so has no function __vaDriverInit_1_0
[AVHWDeviceContext @ 0x7f5788204d80] libva: /usr/lib/x86_64-linux-gnu/dri/intel-vaapi-driver/i965_drv_video.so has no function __vaDriverInit_1_0 [AVHWDeviceContext @ 0x7f5788204d80] Failed to initialise VAAPI connection: -1 (unknown libva error). Failed to create VAAPI device.
[consumer avformat] Failed to initialize VA-API: -5
[h264_vaapi @ 0x7f5788205680] A hardware frames reference is required to associate the encoding device.

STEPS TO REPRODUCE
1. Render 
2. Crash

Before "sudo flatpak update" everything had worked.

Debug information:

Kdenlive: 22.12.3
Package Type: flatpak
MLT: 7.13.0
Qt: 5.15.9 (built against 5.15.8 x86_64-little_endian-lp64)
Frameworks: 5.105.0
System: KDE Flatpak runtime
Kernel: linux 4.15.0-208-generic
CPU: x86_64
Windowing System: xcb
Movit (GPU): disabled
Track Compositing: qtblend
Comment 1 fehler-im-programm 2023-05-13 18:51:39 UTC 
Was fixed by next update!
Comment 2 emohr 2023-05-14 18:00:09 UTC 
Thank you for the feedback. It seems it works. We close this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number.