﻿id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	blockedby	blocking	notify_on_close	platform	project
5314	Movie encode on Redhat Enterprise Linux 8 fails to find libbz2.so	guillaume.gaullier@…	Greg Couch	"

Begin forwarded message:

From: Guillaume Gaullier via ChimeraX-users <chimerax-users@cgl.ucsf.edu>
Subject: [chimerax-users] movie encode bug on Rocky Linux 8.4
Date: September 29, 2021 at 3:32:52 AM PDT
To: ChimeraX Users Help <chimerax-users@cgl.ucsf.edu>
Reply-To: Guillaume Gaullier

Hello,

This time I am reporting what looks almost certainly like a bug.

Using ChimeraX version 1.2.5 on Rocky Linux 8.4 (installed from the RHEL/CentOS 8 RPM package), I get the following error in the Log when trying to use the movie encode command (I attached a copy of the full error message in the Log):

/usr/libexec/UCSF-ChimeraX/bin/ffmpeg: error while loading shared libraries: libbz2.so.1.0: cannot open shared object file: No such file or directory

Turns out I definitely have libbz2 on my system, but not under the filename ChimeraX (or ffmpeg bundled with ChimeraX) is looking for:

$ ls -l /usr/lib64/ | grep libbz2
lrwxrwxrwx.  1 root root           11 Apr  7 03:44 libbz2.so -> libbz2.so.1
lrwxrwxrwx.  1 root root           15 Apr  7 03:44 libbz2.so.1 -> libbz2.so.1.0.6
-rwxr-xr-x.  1 root root        73008 Apr  7 03:44 libbz2.so.1.0.6

If I create a symlink to libbz2.so.1.0.6 and name it libbz2.so.1.0, my movie encode command finishes fine and produces a movie file. So it was easy to work around this problem, but obviously it would be a lot better if it worked out of the box and the user did not have to mess with system files as root.

Thank you in advance,

Guillaume
"	defect	closed	moderate	1.3	Platform		fixed						all	ChimeraX
