First post here so I hope it is correct section .
Does anyone got Blackmagic Fusion (non-foss, but free of charge, compositing software) running on Leap 42.2? When I try on my workstation (with gtx 980) it crashes on start with :
sh: ldconfig: nie znaleziono polecenia
sh: ldconfig: nie znaleziono polecenia
FusionScript Server [5834] Started
Host 'FusionServer' [5837] Added
libDeckLinkAPI.so: cannot open shared object file: No such file or directory
*** Error in `/opt/BlackmagicDesign/Fusion8/Fusion': free(): invalid pointer: 0x00007f513bf00fa0 ***
(the output is a bit longer but I"m not sure howto paste it in a way that will be readable).
When I uninstall Nvidia proprietary driver (Nouveau disabled as well) the application starts - but of course without it video editing/compositing makes little sense.
The same package , with the same driver works on Centos 7 and Fedora 24 . At the same time it crashes similarly on Fedora 25.
Any ideas whatās going on?
Iām getting crazy about it as Iāve spent last couple of days trying to set up my workstation and it fails big time. Centos - Fusion works, my wacom does not and software availability is bad (no Steam either to help a bit, had to pull lots of packages from Github and am still missing a lot). Fedora 25 - Fusion fails, wacom is funky (works, but setting for it does not so I canāt map it to specific monitor). Opensuse Leap 42.2 - Fusion fails, wacom is perfect, software choice very good.
So all in all Iād be super happy if I could stick with Leap - just need to get my tools working and Fusion is a tricky bit.
According to Google Translate, your native language is Polish, and the first two entries you posted translate to āldconfig command not foundā
So,
Iād recommend first that your system isnāt broken and run the following command to verify functionality
ldconfig --help
That should return a result without error, which will then mean that the problem is in the Blackmagic Fusion codeā¦ most likely someone hardcoded a path to ldconfig instead of relying on the systemās PATH.
In other words, almost certainly a bug you should submit to Blackmagic Fusion.
Only as root (or with sudo) though, itās in /sbin so it wonāt work as a normal user - itāll either return a command not found (if you donāt have command-not-found installed) or āAbsolute path to āldconfigā is ā/sbin/ldconfigā, so running it may require superuser privileges (eg. root).ā if you do.
ThxTsu.
On Fedora 25 it does not show ldconfig related message , but still crashes identically:
FusionScript Server [3554] Started
Host āFusionServerā [3557] Added
libDeckLinkAPI.so: cannot open shared object file: No such file or directory
*** Error in `/opt/BlackmagicDesign/Fusion8/Fusionā: free(): invalid pointer: 0x00007f11901c1fa0 ***
I doubt Blackmagic will fix it anytime soon - SUSE isnāt currently on their list of ātestedā distros. Basically they test agains RHEL/CentOS (and as mentioned Fusion works on CentOS 7, Fedora 24 ). But due to extremely limited desktop software availability and problems with my tablet those are not good fit for me.
So Iām forced to look for workarounds.
The app also starts when I remove Nvidia driver.
And just in case hereās the full output from Fedora 25 (I have it on email as Iāve filed a report to Blackmagic) , Iāll post the one from OpenSUSE when I get access to my workstation:
they pointed me towards looking for help on the forumsā¦
And are there big differences in the way folders are worked out between those major distros?
On top of that I donāt think things changed on Fedora side - but while Fusion runs on Fedora 24, it crashes on 25.
On OpenSUSE the error looks very similar to the one from F25 (plus ldconfig). And as mentioned Fusion starts on OpenSUSE when I remove Nvidia driver (note - the same driver does not cause problems with Fusion on Centos), even though it shows this ldconfig message. So while I donāt rule that out, I think path to ldconfig is not high on the possible culprit list.
So is there something different that happens when installing Nvidia driver between the distros?
Iām quite desparate on that one as I donāt have much choices on Linux when it comes to professional grade video / compositing apps .
The good news is that on my Tumbleweed ( latest, up to date )test box with an nVidia GPU and proprietary drivers 375.39 it works fine. Screenshot here; http://i.imgur.com/0BZI1To.png
The bad news is I have no idea why it doesnāt for you - the ldconfig is an not an issue here.
Thank you for checking it out Miuku!
I see youāre running Tumbleweed - so not all hope is lost. In worst case scenario Iāll try to make a switch to Tumbleweed (even though Iād prefer Leap) and check there. And maybe someone will figure this out and Iāll be able to stay on Leap .
@Miuku : BTW - which kernel do you have on your Tumbleweed install? Iāve read that Nvidia driver does not install on kernel 4.10 - at least not without patching (but sadly havenāt found more info about patches and howto apply them).
On 03/03/2017 04:26 PM, Pshemas wrote:
>
> @Miuku : BTW - which kernel do you have on your Tumbleweed install? Iāve
> read that Nvidia driver does not install on kernel 4.10 - at least not
> without patching (but sadly havenāt found more info about patches and
> howto apply them).
>
>
Iām using the GeForce GT 610 card and did the following:
code:
This what I did as best as I can remember using the
NVIDIA-Linux-x86_64-378.09 driver, I was informed that the same patch
works for the 378.13 driver:
Make sure you have compiling tools, sources etc. installed
Thank you @kensch ! You rock - I was able to install Nvidia driver on Tumbleweed thx to your tutorial .
The bad news - Fusion crashes on my workstation, even with Tumbleweed . Again as soon as I remove Nvidia proprietary driver it starts to work againā¦
Dump from Tumbleweed here: http://pastebin.com/ixqn4uD0
Got to admit I completely cluelessā¦ Why the heck on some distros (****, in fact not even distros, but versions of distros) it works with the very same setup (the same driver on the same workstation) while on others it crashes? Arghhhā¦
.
.
.
.
. Again as soon as I remove Nvidia proprietary driver it starts to work againā¦