Bug 505254

Summary:	Clip Monitor and Project Monitor are completely grey and do not play any videos
Product:	[Applications] kdenlive	Reporter:	WM <email.but.again>
Component:	Monitors & Playback	Assignee:	Jean-Baptiste Mardelle <jb>
Status:	REPORTED ---
Severity:	grave	CC:	aspotashev, balooii, brigaton, email.but.again
Priority:	NOR
Version First Reported In:	24.12.3
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Compressed video of my issues (because I misread the file size limit twice) Terminal logs when starting kdenlive More terminal logs, this time while opening and attempting to play a clip (two.mp4)

Description WM 2025-06-06 01:56:49 UTC

SUMMARY

STEPS TO REPRODUCE
1. Launch kdenlive
2. Look at big grey boxes on screen
3. Try to add video
4. Look at the boxes remain to be grey
5. Play the grey boxes
6. Listen to the audio while the boxes remain grey

OBSERVED RESULT
The Clip Monitor and Project Monitor boxes are completely grey.

EXPECTED RESULT
The Clip Monitor and Project Monitor boxes display the selected media.

SOFTWARE/OS VERSIONS
(available in the Info Center app, or by running `kinfo` in a terminal window) (Fun bonus bug: This doesn't work for me either. Launches a small window that reads "Could not find plugin kcm_about-distro", a cursory search yielded no results and I cannot deal with this right now.)
Linux/KDE Plasma: 6? Yes??
KDE Plasma Version: 6.3.5 (so says `kwin_wayland -v`)
KDE Frameworks Version: kinfo is broken and I don't know how to find this
Qt Version: 5.15.17 (so says `qmake -v`)

ADDITIONAL INFORMATION
I reinstalled my opposition program sddm (which not having is probably breaking something but I hate it so whatever) just to make it easier to boot into x11, and confirmed that this is happening to me there too.
Put as grave because the program still launches and seems to work fine outside of the fact that this key feature is completely borked and halts almost all potential usage.
I'd make a nice tidy video of the issue, but I'm having issues with my favorite video editor kdenlive (shocking, I know), so you'll have to make due with the raw OBS recording.
I'm very sorry that this bug report is terrible and unprofessional and (probably) not terribly helpful, I just wanna trim videos again

Comment 1 WM 2025-06-06 02:05:26 UTC

Created attachment 182057 [details]
Compressed video of my issues (because I misread the file size limit twice)

Comment 2 balooii 2025-06-06 12:41:43 UTC

Hi,

Can you open the help menu in Kdenlive, click on "Copy Debug Information" and paste it here? It would also be useful if you can attach the log messages you see when you start kdenlive from the command line as well as the output of the command `glxinfo -B`.

Comment 3 Brigaton 2025-06-07 04:59:57 UTC

hello I have found some a report of someone else encountering this bug in 24.12.3 so I have changed the first version reported

Comment 4 Brigaton 2025-06-07 05:02:39 UTC

(In reply to balooii from comment #2)
> Hi,
> 
> Can you open the help menu in Kdenlive, click on "Copy Debug Information"
> and paste it here? It would also be useful if you can attach the log
> messages you see when you start kdenlive from the command line as well as
> the output of the command `glxinfo -B`.

hello I am someone else who is experiencing this so here is the debug info

Kdenlive: 25.04.2
Package Type: Unknown/Default
MLT: 7.32.0
Qt: 6.9.1 (built against 6.9.1 x86_64-little_endian-lp64)
Frameworks: 6.14.0
System: Arch Linux
Kernel: linux 6.14.10-arch1-1
CPU: x86_64
Windowing System: xcb
GPU: 
Movit (GPU): disabled
Track Compositing: qtblend

and here is the output of glxinfo -B

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 12288 MB
    Total available memory: 12288 MB
    Currently available dedicated video memory: 11400 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce RTX 3060/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 575.57.08
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 575.57.08
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 575.57.08
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Comment 5 balooii 2025-06-07 06:59:58 UTC

I can see that "GPU: " is reported as empty. I assume there was a problem in OpenGL Context initialization.
Can you upload your logs also? Which display manager do you use?
(If you did a kernel or nvidia drivers update make sure you restarted your system)

Comment 6 WM 2025-06-08 17:56:18 UTC

Created attachment 182103 [details]
Terminal logs when starting kdenlive

Probably more helpful then most of my inane ramblings from a few days ago. I should have included it then but I forgot about the extra info and didn't know how to put it in a log file (`kdenlive > kdenlive-log.txt 2>&1` btw). Lots of very strange things, mostly related to qml. I don't know what that is, but it seems to be working for everyone else as I still can't find this bug anywhere else (which makes me wonder if marking it as 'grave' was an overreaction. Yes, it prevents almost all usage, but that's just for me. I'm just one guy).

Comment 7 WM 2025-06-08 18:09:42 UTC

(In reply to email.but.again from comment #6)
> Created attachment 182103 [details]
> Terminal logs when starting kdenlive
> 
> Probably more helpful then most of my inane ramblings from a few days ago. I
> should have included it then but I forgot about the extra info and didn't
> know how to put it in a log file (`kdenlive > kdenlive-log.txt 2>&1` btw).
> Lots of very strange things, mostly related to qml. I don't know what that
> is, but it seems to be working for everyone else as I still can't find this
> bug anywhere else (which makes me wonder if marking it as 'grave' was an
> overreaction. Yes, it prevents almost all usage, but that's just for me. I'm
> just one guy).

Oh woah there's like people here asking questions and trying to help. Sorry I didn't realize. Anyway, I coincidentally did the thing you asked for, I can also nab my debug information and glxinfo real quick.
Debug Information:
Kdenlive: 25.04.1
Package Type: Unknown/Default
MLT: 7.32.0
Qt: 6.9.1 (built against 6.9.0 x86_64-little_endian-lp64)
Frameworks: 6.14.0
System: Arch Linux
Kernel: linux 6.14.9-arch1-1
CPU: x86_64
Windowing System: wayland
GPU: 
Movit (GPU): disabled
Track Compositing: qtblend

`glxinfo -B`:name of display: :0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 8188 MB
    Total available memory: 8188 MB
    Currently available dedicated video memory: 7198 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce RTX 4060/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 570.153.02
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 570.153.02
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 570.153.02
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20


My GPU is also empty. I have a RTX 4060 and no iGPU.
I don't use a startup display manger, which could very well be part of the problem, as I used to use SDDM for a while until I realized I didn't particularly like or need it. But I'm pretty sure kdenlive was working for a good while after I uninstalled SDDM (in my head at least a few months), and when I reinstalled it to boot into X11 for this bug report, the same issue still occurred (I haven't booted into wayland with SDDM though). I'll make sure to keep a closer eye on this and try to be more helpful.

Comment 8 Brigaton 2025-06-11 18:01:25 UTC

(In reply to email.but.again from comment #7)
> (In reply to email.but.again from comment #6)
> > Created attachment 182103 [details]
> > Terminal logs when starting kdenlive
> > 
> > Probably more helpful then most of my inane ramblings from a few days ago. I
> > should have included it then but I forgot about the extra info and didn't
> > know how to put it in a log file (`kdenlive > kdenlive-log.txt 2>&1` btw).
> > Lots of very strange things, mostly related to qml. I don't know what that
> > is, but it seems to be working for everyone else as I still can't find this
> > bug anywhere else (which makes me wonder if marking it as 'grave' was an
> > overreaction. Yes, it prevents almost all usage, but that's just for me. I'm
> > just one guy).
> 
> Oh woah there's like people here asking questions and trying to help. Sorry
> I didn't realize. Anyway, I coincidentally did the thing you asked for, I
> can also nab my debug information and glxinfo real quick.
> Debug Information:
> Kdenlive: 25.04.1
> Package Type: Unknown/Default
> MLT: 7.32.0
> Qt: 6.9.1 (built against 6.9.0 x86_64-little_endian-lp64)
> Frameworks: 6.14.0
> System: Arch Linux
> Kernel: linux 6.14.9-arch1-1
> CPU: x86_64
> Windowing System: wayland
> GPU: 
> Movit (GPU): disabled
> Track Compositing: qtblend
> 
> `glxinfo -B`:name of display: :0
> display: :0  screen: 0
> direct rendering: Yes
> Memory info (GL_NVX_gpu_memory_info):
>     Dedicated video memory: 8188 MB
>     Total available memory: 8188 MB
>     Currently available dedicated video memory: 7198 MB
> OpenGL vendor string: NVIDIA Corporation
> OpenGL renderer string: NVIDIA GeForce RTX 4060/PCIe/SSE2
> OpenGL core profile version string: 4.6.0 NVIDIA 570.153.02
> OpenGL core profile shading language version string: 4.60 NVIDIA
> OpenGL core profile context flags: (none)
> OpenGL core profile profile mask: core profile
> 
> OpenGL version string: 4.6.0 NVIDIA 570.153.02
> OpenGL shading language version string: 4.60 NVIDIA
> OpenGL context flags: (none)
> OpenGL profile mask: (none)
> 
> OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 570.153.02
> OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
> 
> 
> My GPU is also empty. I have a RTX 4060 and no iGPU.
> I don't use a startup display manger, which could very well be part of the
> problem, as I used to use SDDM for a while until I realized I didn't
> particularly like or need it. But I'm pretty sure kdenlive was working for a
> good while after I uninstalled SDDM (in my head at least a few months), and
> when I reinstalled it to boot into X11 for this bug report, the same issue
> still occurred (I haven't booted into wayland with SDDM though). I'll make
> sure to keep a closer eye on this and try to be more helpful.

I have a 3060 so maybe it is a problem with the nvidia drivers

Comment 9 WM 2025-10-15 18:20:05 UTC

Created attachment 185814 [details]
More terminal logs, this time while opening and attempting to play a clip (two.mp4)

Hiya, me again, revisiting this because I still miss kdenlive and want it back so bad. When launching from terminal and messing around (instead of just doing nothing like before), I noticed the following lines in this document
> 169 qrc:/qt/qml/org/kde/kdenlive/ClipMonitor.qml:768:21: QML Rectangle: Binding loop detected for property "width"
> 170 qrc:/qt/qml/org/kde/kdenlive/ClipMonitor.qml:768:21: QML Rectangle: Binding loop detected for property "width"
> 171 qrc:/qt/qml/org/kde/kdenlive/ClipMonitor.qml:768:21: QML Rectangle: Binding loop detected for property "width"
and then again later on
> 210 qrc:/qt/qml/org/kde/kdenlive/ClipMonitor.qml:768:21: QML Rectangle: Binding loop detected for property "width"
> 211 qrc:/qt/qml/org/kde/kdenlive/ClipMonitor.qml:768:21: QML Rectangle: Binding loop detected for property "width"
> 212 qrc:/qt/qml/org/kde/kdenlive/ClipMonitor.qml:768:21: QML Rectangle: Binding loop detected for property "width"

These are the only mentions of "ClipMonitor" in my logs, could this cause the issues described? I don't know the first thing about QML, but from my brief googling, binding loops seem like a pretty common yet sneaky issue. That being said, if this was a major problem I don't see why it wouldn't be happening everywhere, not just on two random installs. Quite possibly a completely unrelated and inconsequential problem. If someone with a functional install could check if this occurs in their logs, I could see that being helpful.

Regarding the nvidia drivers theory, it doesn't seem to be the case. I have many friends with similar arch installations to my own that use nvidia GPUs and drivers, and kdenlive works fine for them. One of them even learned about it because I was bemoaning my great loss, and not uses it for video editing. If this is related it nvidia, it isn't as simple as a global driver issue.