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

            Bug ID: 526311
           Summary: Crashes when laucnhing a new project
    Classification: Applications
           Product: kdenlive
      Version First 26.08.1
       Reported In:
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: critical
          Priority: NOR
         Component: Setup & Installation
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

DESCRIPTION

I installed Kdenlive 26.08.1 on Zorin OS (Ubuntu-based) via the Software Center
(linked to Flathub), and later also tried installing it via Bazaar, which is
also linked to Flathub.

When I launch Kdenlive, it starts normally and I can reach the dialog to create
a new project. However, immediately after creating a new project, Kdenlive
crashes before I can see or use the editor/timeline.

I have tried resetting Kdenlive's configuration, running Kdenlive with software
OpenGL rendering, and checking the graphics/Flatpak configuration. The crash
persists.

The crash appears to occur while Kdenlive is initializing the timeline of the
newly created project.

## STEPS TO REPRODUCE

1. Launch Kdenlive 26.08.1.
2. Select the option to create a new project and choose the desired project
settings.
3. Create the project.
4. Kdenlive crashes before the main editor/timeline becomes visible.

## OBSERVED RESULT

Kdenlive crashes immediately after creating the new project. The main editing
interface and timeline cannot be accessed.

The journal output shows that Kdenlive successfully initializes the Intel
GPU/OpenGL renderer and then starts initializing the project and timeline. The
last relevant messages include:

```text
NO PREVIOUS TIMELINE
...
INVALID BIN PLAYLIST...
...
OPENING FILE WITH TRACKS: 5
FOUND TRACTOR WITH TRACKS: 2
```

The Kdenlive process then exits.

Kdenlive detects the graphics hardware correctly:

```text
OpenGL vendor "Intel"
OpenGL renderer "Mesa Intel(R) UHD Graphics 620 (KBL GT2)"
OpenGL threaded? true
OpenGL ES? false
OpenGL maximum texture size = 16384
OpenGL maximum viewport size = 16384 x 16384
```

I also tested with software rendering:

```bash
flatpak run --env=LIBGL_ALWAYS_SOFTWARE=1 org.kde.kdenlive
```

The crash still occurs.

I also reset the Kdenlive configuration by moving `kdenlive-flatpakrc` out of
the way and allowing Kdenlive to recreate it. This did not resolve the issue.

There are no custom Flatpak overrides:

```bash
flatpak override --show org.kde.kdenlive
```

returns no output.

EXPECTED RESULT

After creating a new project, Kdenlive should open the main editing interface,
including the project bin, monitors and timeline, and allow me to begin
editing.

SOFTWARE/OS VERSIONS

Operating System: Zorin OS (Ubuntu-based), using Wayland/GNOME

Kdenlive version: 26.08.1

Installation: Flatpak from Flathub (system installation)

Flatpak runtime:

```text
org.kde.Platform/x86_64/6.10
```

MLT version:

```text
MLT 7.41.0
```

FFmpeg version:

```text
FFmpeg 9.0.1
```

Kernel:

```text
7.0.0-34-generic
```

GPU:

```text
Intel UHD Graphics 620
```

Graphics driver:

```text
i915
```

Mesa:

```text
25.2.8-0ubuntu0.24.04.2
```

OpenGL:

```text
OpenGL 4.6
Renderer: Mesa Intel(R) UHD Graphics 620 (KBL GT2)
```

Display server:

```text
Wayland
Xwayland 23.2.6
```

KDE Plasma Version: N/A (GNOME desktop)

KDE Frameworks Version: Not applicable / provided by the Flatpak runtime

Qt Version: Provided by the Kdenlive Flatpak runtime (KDE Platform 6.10)

ADDITIONAL INFORMATION

The laptop is a Dell Latitude 7490 with Intel UHD Graphics 620 integrated
graphics and no dedicated GPU.

Kdenlive itself launches successfully; the crash only occurs when creating a
new project.

The Flatpak's bundled MLT and FFmpeg can be executed successfully from inside
the Flatpak environment.

I initially tested forcing the XCB Qt platform with:

```bash
flatpak run --env=QT_QPA_PLATFORM=xcb org.kde.kdenlive
```

but this failed to start because it could not connect to the display:

```text
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb"
```

This test was therefore not representative of the normal Kdenlive crash, which
occurs when creating a project under the normal Wayland environment.

The crash also occurs when forcing software OpenGL, suggesting that it is not
simply caused by hardware OpenGL acceleration.

The Kdenlive configuration was reset, but the crash persisted.

The system's Mesa/OpenGL stack appears to function correctly: Kdenlive detects
the Intel UHD 620 and initializes OpenGL successfully before the crash.

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

Reply via email to