https://bugs.kde.org/show_bug.cgi?id=521680

            Bug ID: 521680
           Summary: Kdenlive crashes when building sequences of existing
                    projects
    Classification: Applications
           Product: kdenlive
      Version First 26.04.1
       Reported In:
          Platform: Flatpak
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: User Interface & Miscellaneous
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

Created attachment 193317
  --> https://bugs.kde.org/attachment.cgi?id=193317&action=edit
Backtrace for Kdenlive

DESCRIPTION
Whenever I try to open a preexisting Kdenlive project that is more complex than
two clips stitched together or a trimmed video, the software crashes while it's
"building sequences". Kdenlive does not crash when starting a brand new
project. This first happened with 26.04.1 and happens in the current version as
well, and in both the Flatpak and AppImage builds.

STEPS TO REPRODUCE
1. Run Kdenlive
2. Open a complex project file
3. Remove or search for any missing files in the project bin

OBSERVED RESULT
Kdenlive crashes while the loading popup says "Building sequences..."

EXPECTED RESULT
Kdenlive should load the project successfully and allow me to start editing.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 44
KDE Plasma Version: 6.6.5
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.1

ADDITIONAL INFORMATION
The terminal output ends like this:
qrc:/qt/qml/org/kde/kdenlive/Ruler.qml:112: TypeError: Cannot read property
'position' of undefined
==== NO PREVIOUS TIMELINE
::::::::::: connecting timeline: 
QUuid("{ae7a1f6c-c6f5-47dd-8bfd-aa41f80e0d54}") , DUR:  20183
qt.core.qobject.connect: QObject::connect(AudioDevInfo, Unknown): invalid
nullptr parameter
qt.core.qobject.connect: QObject::connect(AudioDevInfo, MediaCapture): invalid
nullptr parameter

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to