MX 19 Repository: The Kdenlive Thread

[Stevo]

We have Kdenlive 19.0.8 in the main MX 19 repository, backported from upstream Debian. This is probably the most popular non-linear video editor we have available.

We've put in main for the MX 19 beta perios, but if testers report a critical issue with it, we can move it to our test repo instead, and go with the Buster version.

[Stevo]

Updated to 19.08.1

[Ghost67]

Is this the correct thread for reporting problems with Kdenlive on MX-19?

If so: Kdenlive continues to freeze my machine as it did with the beta 2.1 - which I reported. Hard reboot required when it happens.

Between then and now I have been running Debian Buster with the same kernel (4.19.06) and the same Nvidia driver (418.74) - but with the stock Debian version of Kdenlive - so I know that the problem exists with the more recent Kdenlive that MX-19 supplies and not the kernel or graphics driver.

I've had a look in /var/log but wasn't sure exactly what to look for or in which log, so if you need me to post any info from there I'll be happy to do so.

Code: Select all

System:    Host: mx19 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64 
           root=UUID=c108829c-49d1-48ae-8dbe-aaa6720307fd ro quiet splash 
           Desktop: Xfce 4.14.1 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0 
           Distro: MX-19_x64 patito feo October 21  2019 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: N/A System: Advent product: DT1410 v: N/A serial: <filter> 
           Mobo: Foxconn model: H61MXL/H61MXL-K serial: <filter> BIOS: American Megatrends 
           v: B63D3A04 date: 09/22/2011 
CPU:       Topology: Quad Core model: Intel Core i5-2320 bits: 64 type: MCP arch: Sandy Bridge 
           family: 6 model-id: 2A (42) stepping: 7 microcode: 2F L2 cache: 6144 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 23945 
           Speed: 1596 MHz min/max: 1600/3300 MHz Core speeds (MHz): 1: 1596 2: 1596 3: 1596 
           4: 1596 
           Vulnerabilities: Type: l1tf 
           mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
           Type: mds mitigation: Clear CPU buffers; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass 
           mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, 
           STIBP: disabled, RSB filling 
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics 
           vendor: Foxconn driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0102 
           Device-2: NVIDIA GK107 [GeForce GT 640] vendor: ASUSTeK driver: nvidia v: 418.74 
           bus ID: 01:00.0 chip ID: 10de:0fc1 
           Display: x11 server: X.Org 1.20.4 driver: modesetting,nvidia 
           unloaded: fbdev,nouveau,vesa alternate: nv resolution: 1366x768~60Hz 
           OpenGL: renderer: GeForce GT 640/PCIe/SSE2 v: 4.6.0 NVIDIA 418.74 direct render: Yes 
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Foxconn 
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1c20 
           Device-2: NVIDIA GK107 HDMI Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel 
           bus ID: 01:00.1 chip ID: 10de:0e1b 
           Device-3: Logitech HD Pro Webcam C920 type: USB driver: snd-usb-audio,uvcvideo 
           bus ID: 1-1.1:3 chip ID: 046d:082d serial: <filter> 
           Sound Server: ALSA v: k4.19.0-6-amd64 
Network:   Device-1: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet vendor: Foxconn driver: atl1c 
           v: 1.0.1.1-NAPI port: d000 bus ID: 03:00.0 chip ID: 1969:1083 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 931.51 GiB used: 26.82 GiB (2.9%) 
           ID-1: /dev/sda vendor: Samsung model: HD103SJ size: 931.51 GiB block size: 
           physical: 512 B logical: 512 B speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> 
           rev: 00E4 scheme: MBR 
Partition: ID-1: / raw size: 929.48 GiB size: 913.89 GiB (98.32%) used: 26.82 GiB (2.9%) 
           fs: ext4 dev: /dev/sda1 
           ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60) 
           cache pressure: 100 (default) dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 42.0 C mobo: N/A gpu: nvidia temp: 36 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 10% 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/antix.list 
           1: deb http://iso.mxrepo.com/antix/buster buster main
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
           1: deb http://deb.debian.org/debian buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian buster main contrib non-free
           2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mxrepo.com/mx/repo/ buster main non-free
           No active apt repos in: /etc/apt/sources.list.d/various.list 
Info:      Processes: 216 Uptime: 1h 22m Memory: 7.71 GiB used: 999.5 MiB (12.7%) Init: SysVinit 
           v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 
           running in: quick-system-in inxi: 3.0.36 

[Stevo]

Does it lock up the machine right as it starts up, or when you do some particular operation in it?

[Ghost67]

When I try to launch it.
Once again though, this is only on my Nvidia system. On Intel GFX it works fine.

[Stevo]

I just built the 19.08.2 release for MX 19, and it also runs on my Intel GPU. I would bet it still dies on your Nvidia--do you see any relevant error messages when you start it from the terminal and it dies? Those usually provide good search terms.

[Ghost67]

https://imgur.com/d0HC9Ev

There is a mass of text as the program tries to launch that flies past too quick to read, but this is the last thing displayed before the system locks up.
Hopefully it's useful?

Edit: I ran a search for ffmpeg items in synaptic (just to see what it returns - I didn't install anything), I wonder if 'nv-codec-headers' (not installed) might be relevant to this problem?

[Stevo]

What do you get for

apt policy ffmpeg nv-codec-headers

[Ghost67]

Code: Select all

 root@mx19:/home/ghost# apt policy ffmpeg nv-codec-headers
ffmpeg:
  Installed: 7:4.1.4-1mx19+1
  Candidate: 7:4.1.4-1mx19+1
  Version table:
 *** 7:4.1.4-1mx19+1 500
        500 http://mxrepo.com/mx/repo buster/main amd64 Packages
        100 /var/lib/dpkg/status
     7:4.1.4-1~deb10u1 500
        500 http://deb.debian.org/debian buster/main amd64 Packages
        500 http://deb.debian.org/debian-security buster/updates/main amd64 Packages
nv-codec-headers:
  Installed: (none)
  Candidate: 8.1.24.9-1~mx19+1
  Version table:
     8.1.24.9-1~mx19+1 500
        500 http://mxrepo.com/mx/repo buster/main amd64 Packages
        500 http://mxrepo.com/mx/repo buster/main i386 Packages

I've just been researching dependencies for the version listed in Debian testing (19.08.2) and these recommends are not installed:

dvdauthor
dvgrab
oxygen-icon-theme
recordmydesktop
swh-plugins

Are any required?

[Ghost67]

I see you have added the Sid build of FFMPEG to the MX test repos:

viewtopic.php?f=140&t=53898

Would adding this address my Nvidia problem? Would simply installing the current nv-encoder-headers address it?

It isn't clear to me what I should do and I'm on the horns of a dilemma here.

It seems as though my problem arises from using the later (non- Buster) build of Kdenlive, because under the same kernel and the same Nvidia drivers on the same hardware under 'vanilla' Debian I have encountered no such issues.

I use Kdenlive on a daily basis, and while I'm a long-time fanboy of MX (dating right back to MX-14) I will not use anything from the test repos (I need tried and tested software) and nor will I go the route of Flatpaks or Appimages to 'cure my ills'.

It seems my options are:
1) Try installing the nv-encoder-headers - it may help, I just don't know, but I've heard nothing to indicate there will be added problems doing so.
2) Downgrade to MX-18 and continue to live on the Stretch base
3) Use vanilla Debian and the older build of Kdenlive which presents no such problems on my hardware.

I'll go with option 1 and see what the result is :)