Description of problem: I open a 1.5Gb GoPro video, and simply clicking a clip (to view the properties), crashes the application. This crash triggers every time. Version-Release number of selected component: shotcut-25.05.11-1.fc41 Additional info: reporter: libreport-2.17.15 type: CCpp reason: shotcut killed by SIGSEGV journald_cursor: s=7e95efa71411464f937e06cd1b91d478;i=a9782;b=aefa3ffe3b1c4b70aad706dfc5976d64;m=45a9962a;t=635ce41265d36;x=861054eb85f80ef4 executable: /usr/bin/shotcut cmdline: /usr/bin/shotcut cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-org.shotcut.Shotcut-16055.scope rootdir: / uid: 1000 kernel: 6.14.5-200.fc41.x86_64 package: shotcut-25.05.11-1.fc41 runlevel: N 5 dso_list: /usr/bin/shotcut shotcut-25.05.11-1.fc41.x86_64 (Fedora Project) 1748009446 backtrace_rating: 4 crash_function: ___pthread_mutex_lock comment: I open a 1.5Gb GoPro video, and just clicking around, or cropping, crashes the application. There doesn't seem to be a repeatable trigger, but it happens within a few minutes every time. Truncated backtrace: Thread no. 1 (14 frames) #0 ___pthread_mutex_lock at pthread_mutex_lock.c:80 #1 mlt_properties_inc_ref at /usr/src/debug/mlt-7.32.0-1.fc41.x86_64/src/framework/mlt_properties.c:366 #3 Mlt::Service::Service at /usr/src/debug/mlt-7.32.0-1.fc41.x86_64/src/mlt++/MltService.cpp:46 #4 Mlt::Service::consumer at /usr/src/debug/mlt-7.32.0-1.fc41.x86_64/src/mlt++/MltService.cpp:120 #5 Mlt::Controller::saveXML at /usr/src/debug/shotcut-25.05.11-1.fc41.x86_64/src/mltcontroller.cpp:504 #6 MainWindow::saveXML at /usr/src/debug/shotcut-25.05.11-1.fc41.x86_64/src/mainwindow.cpp:3639 #7 MainWindow::doAutosave at /usr/src/debug/shotcut-25.05.11-1.fc41.x86_64/src/mainwindow.cpp:1735 #8 autosaveTask at /usr/src/debug/shotcut-25.05.11-1.fc41.x86_64/src/mainwindow.cpp:1913 #9 QtConcurrent::RunFunctionTaskBase<void>::run at /usr/include/qt6/QtConcurrent/qtconcurrentrunbase.h:83 #10 QThreadPoolThread::run at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/corelib/thread/qthreadpool.cpp:71 #11 operator() at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/corelib/thread/qthread_unix.cpp:375 #12 (anonymous namespace)::terminate_on_exception<QThreadPrivate::start(void*)::<lambda()> > at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/corelib/thread/qthread_unix.cpp:311 #13 QThreadPrivate::start at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/corelib/thread/qthread_unix.cpp:339 #15 __clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 Potential duplicate: bug 2365635
Created attachment 2091231 [details] File: proc_pid_status
Created attachment 2091232 [details] File: maps
Created attachment 2091233 [details] File: limits
Created attachment 2091234 [details] File: environ
Created attachment 2091235 [details] File: open_fds
Created attachment 2091236 [details] File: mountinfo
Created attachment 2091237 [details] File: os_info
Created attachment 2091238 [details] File: cpuinfo
Created attachment 2091239 [details] File: core_backtrace
Created attachment 2091240 [details] File: exploitable
Created attachment 2091241 [details] File: var_log_messages
Created attachment 2091242 [details] File: backtrace
Upon further checks, it appears that I can consistently crash the application by simply accessing the properties of one of the clips.
The issue appears to be somewhat related to Wayland. When I switched to Xorg, the crashing stopped.
I'm seeing what I believe is the same bug. I see it both with the Mate desktop and also with Gnome-xorg. All that is needed to trigger the bug is: 1. Start a new project. 2. Drag a video (a short, 40 second one will do) from the "Recent" panel into the "Playlist" panel. 3. Double-click on the video in the Playlist panel and allow it to play. After about 90 seconds (possibly well after the video has finished playing), the SEGFAULT occurs. Thread 59 "Thread (pooled)" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fe5bbdfe6c0 (LWP 8783)] ___pthread_mutex_lock (mutex=mutex@entry=0x4054c00000000348) at pthread_mutex_lock.c:80 80 unsigned int type = PTHREAD_MUTEX_TYPE_ELISION (mutex); (gdb) bt #0 ___pthread_mutex_lock (mutex=mutex@entry=0x4054c00000000348) at pthread_mutex_lock.c:80 #1 0x00007fe60b83580c in mlt_properties_inc_ref (self=<optimized out>) at /usr/src/debug/mlt-7.32.0-1.fc41.x86_64/src/framework/mlt_properties.c:366 #2 mlt_properties_inc_ref (self=<optimized out>) at /usr/src/debug/mlt-7.32.0-1.fc41.x86_64/src/framework/mlt_properties.c:361 #3 0x00007fe60b86d072 in Mlt::Service::Service (this=<optimized out>, service=<optimized out>, this=<optimized out>, service=<optimized out>) at /usr/src/debug/mlt-7.32.0-1.fc41.x86_64/src/mlt++/MltService.cpp:46 #4 0x00007fe60b86d5f8 in Mlt::Service::consumer ( this=this@entry=0x7fe5bbdfd470) at /usr/src/debug/mlt-7.32.0-1.fc41.x86_64/src/mlt++/MltService.cpp:120 #5 0x00005649c04ca6aa in Mlt::Controller::saveXML (this=0x5649cf47a8c8, filename=..., service=<optimized out>, withRelativePaths=<optimized out>, tempFile=0x0, proxy=false, projectNote=...) at /usr/src/debug/shotcut-25.05.11-1.fc41.x86_64/src/mltcontroller.cpp:504 #6 0x00005649c04a8f0a in MainWindow::saveXML (this=0x5649cf691740, filename=..., withRelativePaths=false) at /usr/src/debug/shotcut-25.05.11-1.fc41.x86_64/src/mainwindow.cpp:3636 #7 0x00005649c0495609 in MainWindow::doAutosave (this=0x5649cf691740) at /usr/src/debug/shotcut-25.05.11-1.fc41.x86_64/src/mainwindow.cpp:1735 --Type <RET> for more, q to quit, c to continue without paging-- #8 autosaveTask (p=0x5649cf691740) at /usr/src/debug/shotcut-25.05.11-1.fc41.x86_64/src/mainwindow.cpp:1913 #9 0x00005649c03a9aea in QtConcurrent::RunFunctionTaskBase<void>::run ( this=0x5649d62df070) at /usr/include/qt6/QtConcurrent/qtconcurrentrunbase.h:83 #10 0x00007fe6088bfbf3 in QThreadPoolThread::run (this=0x5649cfdb73f0) at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/corelib/thread/qthreadpool.cpp:71 #11 0x00007fe6088b67e9 in operator() (__closure=<optimized out>) at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/corelib/thread/qthread_unix.cpp:375 #12 (anonymous namespace)::terminate_on_exception<QThreadPrivate::start(void*)::<lambda()> > (t=...) at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/corelib/thread/qthread_unix.cpp:311 #13 QThreadPrivate::start (arg=0x5649cfdb73f0) at /usr/src/debug/qt6-qtbase-6.8.2-3.fc41.x86_64/src/corelib/thread/qthread_unix.cpp:339 #14 0x00007fe60807dfa8 in start_thread (arg=<optimized out>) at pthread_create.c:448 #15 0x00007fe608101fcc in __GI___clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 (gdb)
The "Linux portable tar" version of Shotcut 25.05.11 downloaded from www.shotcut.org seems to work just fine in my Mate desktop, so it appears the problem is not upstream.
FEDORA-2025-28ee3094a5 (shotcut-25.07.06-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-28ee3094a5
FEDORA-2025-837f0344a0 (shotcut-25.07.07-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-837f0344a0
FEDORA-2025-c9a94763bb (shotcut-25.07.07-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-c9a94763bb
FEDORA-2025-837f0344a0 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-837f0344a0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-837f0344a0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-c9a94763bb has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-c9a94763bb` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-c9a94763bb See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
The following negative karma has been posted on bodhi: Changed, but no improvement. Now the program sometimes SEGFAULTs as before, but often just locks up and becomes totally unresponsive to user input. "ps -l" shows: F UID PID PPID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND 0 1000 2934 2125 20 0 2607472 616952 futex_ Sl+ tty2 0:36 /usr/bin/shotcut With gdb attached, the SIGTERM shows: Thread 1 "shotcut" received signal SIGTERM, Terminated. Downloading 13.57 K source file /usr/src/debug/glibc-2.40-26.fc41.x86_64/nptl/../sysdeps/nptl/futex-internal.h futex_wait (futex_word=0x555ea98c8538, expected=2, private=0) at ../sysdeps/nptl/futex-internal.h:146 146 int err = lll_futex_timed_wait (futex_word, expected, NULL, private); But shotcut does not then terminate. Only SIGKILL is effective.
FEDORA-2025-0abc672c41 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-0abc672c41` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-0abc672c41 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-3044d51e53 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-3044d51e53` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-3044d51e53 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Created attachment 2097750 [details] Backtrace after SEGFAULT. Still SEGFAULTS as before in Fedora-41 (fully updated 2025-07-19).
A quick way to provoke the fault is simply to attempt to try to drag a selected clip in the timeline. The SEGFAULT is immediate.
FEDORA-2025-0abc672c41 (shotcut-25.07.16-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-21faa22f86 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-21faa22f86` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-21faa22f86 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-1583c2553f has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-1583c2553f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-1583c2553f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Created attachment 2098670 [details] Backtrace after SIGSEGV Still fails in Fedora-41. Just open a video file, then click in the clip in the timeline. Program immediately fails. I don't see how this program in this packaging is useful to anyone. The "Linux portable tar" version 25.07.26 works fine in Fedora-41.
FEDORA-2025-8f22f5470e has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-8f22f5470e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-8f22f5470e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
shotcut-25.07.31 from updates-testing solves the SEGFAULT problem I've been seeing in both Fedora 41 and 42. Thanks for fixing this.
FEDORA-2025-8f22f5470e (shotcut-25.07.31-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.