Arch Linux

ComradeSloth

Member

Registered: 2017-09-25

Posts: 3

Kdenlive failing to render

Whenever I attempt to render a project in any format, this error message is displayed:

mlt_repository_init: failed to dlopen /usr/lib/mlt/libmltopengl.so (libmovit.so.7: cannot open shared object file: No such file or directory)
medium: [ ref=1, _mlt_properties_load=medium, __mlt_properties_load=medium ]
[swscaler @ 0x7fe8480c57c0] Warning: data is not aligned! This can lead to a speedloss
[mp4 @ 0x7fe85400b7a0] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. [mp4 @ 0x7fe85400b7a0] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead.

I am using Kdenlive version 17.08.1 and the packages mlt, sox and vid.stab are up to date (installing sox fixed this error message I was previously having):

mlt_repository_init: failed to dlopen /usr/lib/mlt/libmltsox.so (libsox.so.3: cannot open shared object file: No such file or directory)

Any help would be much appreciated.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,668

Re: Kdenlive failing to render

Well if you figured out that there's a potential sox dependency, you should've also noticed that there's a movit package

ComradeSloth

Member

Registered: 2017-09-25

Posts: 3

Re: Kdenlive failing to render

Well if you figured out that there's a potential sox dependency, you should've also noticed that there's a movit package

I installed the movit package which solved the problem but am getting the following error when trying to render in mp3:

** (melt:12843): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-OfuwivprnN: Connection refused
[mp2 @ 0x7fe538013700] Channel layout not specified

And in mp4:

** (melt:12875): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-OfuwivprnN: Connection refused
medium: [ ref=1, _mlt_properties_load=medium, __mlt_properties_load=medium ]
[swscaler @ 0x7f2e7c0c57c0] Warning: data is not aligned! This can lead to a speedloss
[mp4 @ 0x7f2e8c00b7a0] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. [mp4 @ 0x7f2e8c00b7a0] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead.

Last edited by ComradeSloth (2017-09-28 17:43:32)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,668

Re: Kdenlive failing to render

How are you logging into your system and how do you start X? What are the outputs of

loginctl show-session
systemctl --user status dbus
printenv | grep DBUS

And these errors don't necessarily denote a failure, do you just get the error but the rendering continues or does it abort?

ComradeSloth

Member

Registered: 2017-09-25

Posts: 3

Re: Kdenlive failing to render

How are you logging into your system and how do you start X? What are the outputs of

loginctl show-session
systemctl --user status dbus
printenv | grep DBUS

And these errors don't necessarily denote a failure, do you just get the error but the rendering continues or does it abort?

I use the lightdm display manager to log in and start X.

loginctl show-session outputs this:

EnableWallMessages=no
NAutoVTs=6
KillUserProcesses=no
RebootToFirmwareSetup=no
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0
BlockInhibited=handle-power-key:handle-suspend-key:handle-hibernate-key:handle-lid-switch
DelayInhibited=sleep
InhibitDelayMaxUSec=5s
HandlePowerKey=poweroff
HandleSuspendKey=suspend
HandleHibernateKey=hibernate
HandleLidSwitch=suspend
HandleLidSwitchDocked=ignore
HoldoffTimeoutUSec=30s
IdleAction=ignore
IdleActionUSec=30min
PreparingForShutdown=no
PreparingForSleep=no
Docked=yes
RemoveIPC=yes
RuntimeDirectorySize=1680293888
InhibitorsMax=8192
NCurrentInhibitors=5
SessionsMax=8192
NCurrentSessions=1
UserTasksMax=10813

systemctl --user status dbus outputs this:

● ArchLinux-Desktop
    State: running
     Jobs: 0 queued
   Failed: 0 units
    Since: Sat 2017-09-30 09:19:50 BST; 4min 42s ago
   CGroup: /user.slice/user-1000.slice/user@1000.service
           ├─gnome-terminal-server.service
           │ ├─1195 /usr/lib/gnome-terminal/gnome-terminal-server
           │ ├─1202 bash
           │ ├─1245 systemctl --user status
           │ └─1246 less
           ├─pulseaudio.service
           │ └─660 /usr/bin/pulseaudio --daemonize=no
           ├─at-spi-dbus-bus.service
           │ └─1051 /usr/lib/at-spi2-core/at-spi-bus-launcher
           ├─dbus.service
           │ ├─632 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation
           │ └─723 /usr/lib/dconf/dconf-service
           ├─gvfs-udisks2-volume-monitor.service
           │ └─735 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
           ├─gvfs-metadata.service
           │ └─900 /usr/lib/gvfs/gvfsd-metadata
           ├─gvfs-mtp-volume-monitor.service
           │ └─807 /usr/lib/gvfs/gvfs-mtp-volume-monitor
           ├─init.scope
           │ ├─617 /usr/lib/systemd/systemd --user
           │ └─618 (sd-pam)
           └─gvfs-daemon.service
             ├─636 /usr/lib/gvfs/gvfsd
             ├─641 /usr/lib/gvfs/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
             └─891 /usr/lib/gvfs/gvfsd-trash --spawner :1.3 /org/gtk/gvfs/exec_spaw/0

printenv | grep DBUS outputs this:

DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus

And yes, the rendering crashes.