Summary: | Crash after changing monitor | ||
---|---|---|---|
Product: | [Applications] kdenlive | Reporter: | jamie marchant <jamie.marchant> |
Component: | Rendering & Export | Assignee: | Jean-Baptiste Mardelle <jb> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | wegwerf-1-2-3 |
Priority: | NOR | Keywords: | drkonqi |
Version First Reported In: | 16.04.0 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Output of 'kdenlive' when run from the terminal. |
Description
jamie marchant
2016-09-24 20:35:36 UTC
What graphics card are you using? What OpenGL-related information does Kdenlive report when started in a terminal? Created attachment 101306 [details]
Output of 'kdenlive' when run from the terminal.
Output of 'kdenlive' when run from the terminal.
I have an ATI Radon 5400 and am using the Kernel driver.(not the 'proprietary' ones.) Here is my terminal output in a >> normal run. <<(as I said I had to get the program to work, so I deleted all the Kdenlive stuff in my home folder.) I don't see anything OpenGL related in that log. Do you have OpenGL enabled drivers installed? Kdenlive should report some OpenGL information at startup. Moreover, your crash is trying to open OpenGL. Yes I have OpenGL enabled drivers and to make sure everything still works I ran the Linux port of Portal 2. The OpenGL stuff must have been removed from the Fedora Cora port of kdenlive? Would you like to see the output of 'glxinfo'? No, I don't want to see arbitrary output. You should see Kdenlive startup messages similar to this: OpenGL vendor: "X.Org" OpenGL renderer: "Gallium 0.4 on AMD PITCAIRN (DRM 2.43.0, LLVM 3.8.0)" OpenGL Threaded: false OpenGL ARG_SYNC: true OpenGL OpenGLES: false If Fedora has incorrectly OpenGL stuff, then please tell your distro packagers to correctly package Kdenlive. Thank you very much for your cooperation. This in fact looks like a duplicate of bug #364278. Kdenlive 16.04.2 crashes on some config. So unfortunately there is no easy fix unless your distro packagers prepare 16.04.3 or 16.08.x versions Hmm this does look like a duplicate too me. *** This bug has been marked as a duplicate of bug 364278 *** |