mltframework / mltframework/shotcut
Crash on launch on Linux starting with 26.6
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 11h 27m
- Merged PRs (30d)
- 5
Description
- Operating System: Linux
- Shotcut Version: 26.6.25, 26.8.1
Describe the bug
Shotcut crashes on launch. The window appears for a split second then disappears. This happens twice per launch as if the app reattempts to start.
App was compiled from source, tried compiling with make and ninja with same result.
cmake -DCMAKE_INSTALL_PREFIX=/opt/shotcut -DCMAKE_BUILD_TYPE=Release -GNinja ..
Is there a log file that can be checked for more info? Output is
No appenders associated with category qt.qpa.services
[Warning] <> Failed to register with host portal QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name org.freedesktop.portal.Desktop was not provided by any .service files")
libDeckLinkAPI.so: cannot open shared object file: No such file or directory
---
formats:
***long list***
...
---
audio_codecs:
***long list***
...
---
video_codecs:
***long list***
[Info ] <> Using Qt multimedia with FFmpeg version 7.1.5 nonfree and unredistributable
libva info: VA-API version 1.23.0
libva info: Trying to open /usr/X11/lib/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_23
libva info: va_openDriver() returns 0
Steps To Reproduce
- Start Shotcut
- Crash
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the launch crash from a source build using the reported CMake/Ninja configuration and capture the complete output. The issue names no source file, test, or entry point; progress would require identifying the crash location and verifying that Shotcut launches successfully on Linux.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100