Bug 499753

Summary: Consistent crash at rendering
Product: [Applications] kdenlive Reporter: David REVOY <info>
Component: Rendering & ExportAssignee: Jean-Baptiste Mardelle <jb>
Status: CONFIRMED ---    
Severity: crash CC: cameronbosch, fritzibaby
Priority: HI Keywords: triaged
Version First Reported In: 24.12.2   
Target Milestone: ---   
Platform: Flatpak   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: An archive with rendering log, ffplay term output, screenshot of the error in the UI, and the kdenlive project.
screenshot of the rendering crash

Description David REVOY 2025-02-10 11:24:03 UTC
Created attachment 178109 [details]
An archive with rendering log, ffplay term output, screenshot of the error in the UI, and the kdenlive project.

Hi, I have a reproducible crash today at the end of the rendering of my videos (as Mp4 or Mkv). The error reads: 
"
Qt: Session management error: Could not open network socket
[matroska @ 0x7693e8000f40] Timestamps are unset in a packet for stream 1. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly [matroska @ 0x7693e8000f40] Encoder did not produce proper pts, making some up.
"
I attach here screenshot of the rendering user interface, and also log, the project file and a ffplay of the rendering. The file looks rendered to completion by the way.

Version Kdenlive/MLT/Qt: 24.12.1 (Flatpak up to date of today) :
FFmpeg extension with extra codecs       org.freedesktop.Platform.ffmpeg-full                                 23.08         system
FFmpeg extension with extra codecs       org.freedesktop.Platform.ffmpeg-full                                 24.08         system
openh264                                 org.freedesktop.Platform.openh264         2.1.0                      2.2.0         system
openh264                                 org.freedesktop.Platform.openh264         2.4.1                      2.4.1         system
Breeze GTK theme                         org.gtk.Gtk3theme.Breeze                  6.2.5                      3.22          system
KDE Application Platform                 org.kde.Platform                                                     5.15-23.08    system
KDE Application Platform                 org.kde.Platform                                                     6.6           system
KDE Application Platform                 org.kde.Platform                                                     6.7           system
KDE Application Platform                 org.kde.Platform                                                     6.8           system
Kdenlive                                 org.kde.kdenlive                          24.12.1                    stable        system

OS: Debian 12 KDE (5.27.5; framework 5.103.0; Qt 5.15.8; X11 )
CPU: 16x AMD Ryzen 7 3700x
Ram: 32GB
GPU: AMD Radeon RX5500 XT
Comment 1 emohr 2025-02-11 17:13:51 UTC
Thank you for reporting. 
Please try with the current Kdenlive AppImage version 24.12.1 to see if there are any packaging issues https://kdenlive.org/en/download/
Comment 2 David REVOY 2025-02-11 17:28:10 UTC
Tested, thank you. I can't reproduce with the appimage. 

It sounds like a Flatpak packaging issue.
Comment 3 David REVOY 2025-02-18 10:17:30 UTC
Created attachment 178510 [details]
screenshot of the rendering crash

Flatpak got an update, and I can still reproduce:

Kdenlive: 24.12.2
MLT: 7.30.0
FFmpeg
KDE Frameworks: 6.11.0
Qt: Using 6.8.2 and built against 6.8.2
KDE Flatpak runtime (Xcb)
Build ABI: x86_64-little_endian-lp64
Kernel: linux 6.8.10-2-liquorix-amd64

Rendering of /home/deevad/video-channel/2025-02-10_straight-line-tool-V-key/straight-line-tool-V-key_output.mp4 crashed
[mp3 @ 0x560c4073bc80] Estimating duration from bitrate, this may be inaccurate
[mp3 @ 0x560c409e3c80] Estimating duration from bitrate, this may be inaccurate
[mp3 @ 0x560c409e3c80] Estimating duration from bitrate, this may be inaccurate
[mp3 @ 0x560c4073bc80] Estimating duration from bitrate, this may be inaccurate
Qt: Session management error: Could not open network socket
[mp3 @ 0x560c40bdee40] Estimating duration from bitrate, this may be inaccurate
[mp3 @ 0x560c40e0b180] Estimating duration from bitrate, this may be inaccurate
[mp3 @ 0x560c40bdee40] Estimating duration from bitrate, this may be inaccurate
[mp3 @ 0x560c40e9cf80] Estimating duration from bitrate, this may be inaccurate
[mp3 @ 0x750f34015280] Estimating duration from bitrate, this may be inaccurate
[mp3 @ 0x750f3401ae40] Estimating duration from bitrate, this may be inaccurate
[mp3 @ 0x750f37dc3d00] Estimating duration from bitrate, this may be inaccurate
[mp3 @ 0x750dc43f2d00] Estimating duration from bitrate, this may be inaccurate
[mp4 @ 0x750f38000f40] Timestamps are unset in a packet for stream 1. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly [mp4 @ 0x750f38000f40] Encoder did not produce proper pts, making some up.
Comment 4 emohr 2025-02-18 16:38:15 UTC
Thank you for testing it. Do you have tested it with our official flatpak from flathub https://flathub.org/apps/org.kde.kdenlive ? If not, please do so.
Comment 5 David REVOY 2025-02-18 16:49:59 UTC
@emohr : Thank you. Yes, this is the official Flatpak, the one signed and verified by KDE.
Comment 6 emohr 2025-02-18 17:06:56 UTC
Thank you for the feedback. I’ll check further steps on our site about the flatpak packaging.
Comment 7 cameronbosch 2025-02-21 02:09:49 UTC
Can confirm that this is happening on Arch Linux as well also with the Flatpak:

"[mp4 @ 0x744d18000f40] Timestamps are unset in a packet for stream 1. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly [mp4 @ 0x744d18000f40] Encoder did not produce proper pts, making some up.

QThreadStorage: Thread 0x56a0722d8670 exited after QThreadStorage 8 destroyed QThreadStorage: Thread 0x56a0722d8670 exited after QThreadStorage 2 destroyed QThreadStorage: Thread 0x56a0722d8670 exited after QThreadStorage 1 destroyed
Rendering of REDACTED/PATH/HERE/Videos/My Video & This.mp4 aborted, resulting video will probably be corrupted.`"