Python3 `libbz2.so` needs soname change for some distros

[jvoisin]

Version and Platform (required):

• Binary Ninja Version: 6.1.10588-dev Personal, fdddf612
• OS: fedora-asahi-remix
• OS Version: 44
• CPU Architecture: arm64

Bug Description:

Looking at the log, I saw the following line:

[ScriptingProvider] Failed to import python plugin: official/Vector35_Sidekick: libbz2.so.1.0: cannot open shared object file: No such file or directory (Details...)

Clicking "Details" shows the following:

Traceback (most recent call last):
  File "/home/jvoisin/bin/binaryninja/plugins/../python/binaryninja/scriptingprovider.py", line 1205, in _load_module
    __import__(module)
    ~~~~~~~~~~^^^^^^^^
  File "/home/jvoisin/.binaryninja/channels/official/plugins/Vector35_Sidekick/__init__.py", line 34, in <module>
    plugin_instance = Plugin()
  File "/home/jvoisin/.binaryninja/channels/official/plugins/Vector35_Sidekick/plugin.py", line 56, in __init__
    self._register_view_types()
    ~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/home/jvoisin/.binaryninja/channels/official/plugins/Vector35_Sidekick/plugin.py", line 539, in _register_view_types
    register_all_view_types()
    ~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/home/jvoisin/.binaryninja/channels/official/plugins/Vector35_Sidekick/gui/__init__.py", line 13, in register_all_view_types
    from .sidekick_view import register_sidekick_view_type
  File "/home/jvoisin/.binaryninja/channels/official/plugins/Vector35_Sidekick/gui/sidekick_view/__init__.py", line 14, in <module>
    from .sidekick_view import (
    ...<14 lines>...
    )
  File "/home/jvoisin/.binaryninja/channels/official/plugins/Vector35_Sidekick/gui/sidekick_view/sidekick_view.py", line 66, in <module>
    from ..resource_browser import showNotebookEntryInResources
  File "/home/jvoisin/.binaryninja/channels/official/plugins/Vector35_Sidekick/gui/resource_browser/__init__.py", line 4, in <module>
    from .widget import (
    ...<7 lines>...
    )
  File "/home/jvoisin/.binaryninja/channels/official/plugins/Vector35_Sidekick/gui/resource_browser/widget.py", line 39, in <module>
    from ._details import (
    ...<5 lines>...
    )
  File "/home/jvoisin/.binaryninja/channels/official/plugins/Vector35_Sidekick/gui/resource_browser/_details.py", line 20, in <module>
    from ..code_maps._detail_widget import GraphicalCodeMapDetailWidget
  File "/home/jvoisin/.binaryninja/channels/official/plugins/Vector35_Sidekick/gui/code_maps/_detail_widget.py", line 41, in <module>
    from ._graph_builder import GraphBuildResult, GraphicalCodeMapGraphBuilder, NodeKey
  File "/home/jvoisin/.binaryninja/channels/official/plugins/Vector35_Sidekick/gui/code_maps/_graph_builder.py", line 8, in <module>
    import networkx as nx
  File "/home/jvoisin/.binaryninja/python313/site-packages/networkx/__init__.py", line 19, in <module>
    from networkx import utils
  File "/home/jvoisin/.binaryninja/python313/site-packages/networkx/utils/__init__.py", line 2, in <module>
    from networkx.utils.decorators import *
  File "/home/jvoisin/.binaryninja/python313/site-packages/networkx/utils/decorators.py", line 1, in <module>
    import bz2
  File "/home/jvoisin/bin/binaryninja/plugins/python/bundled-python3/lib/python313.zip/bz2.py", line 17, in <module>
    from _bz2 import BZ2Compressor, BZ2Decompressor
ImportError: libbz2.so.1.0: cannot open shared object file: No such file or directory

Steps To Reproduce:

• Open Binary Ninja with Sidekick installed
• Open the logs
• See a red error line

Expected Behavior:

• No error

Screenshots:

[fuzyll]

@jvoisin Do you have bzip2-libs installed on your Fedora system? Curious if the issue is a missing package or if we've compiled in a way that's causing it to not find the library that's already installed.

[jvoisin]

root@chernabog 21:16 ~ dnf install bzip2-libs.aarch64
Updating and loading repositories:
Repositories loaded.
Package "bzip2-libs-1.0.8-23.fc44.aarch64" is already installed.

Nothing to do.
root@chernabog 21:16 ~ 

yes I do :)

[fuzyll]

Ah, I think the issue might be that we expect libbz2.so.1.0 and Fedora 44 supplies libbz2.so.1 or libbz2.so.1.0.8 as per this link.

I am not really sure what the right move is here, but are you able to confirm that making a symlink in /usr/lib64 fixes the issue? I sort of expected Fedora to make all 3 (.1, .1.0, and .1.0.8), but we might be able to just rely on .1 ourselves.

[jvoisin]

Creating a symbolic link (ln -s /usr/lib64/libbz2.so.1.0.8 /usr/lib64/libbz2.so.1.0) does indeed fix the issue.

[fuzyll]

Awesome, thanks! It looks like there's a slight packaging difference between Fedora and Ubuntu (what we build on/officially support), but it shouldn't be difficult for us to clean up. Hopefully you're all set for now and anyone that comes across this in the meantime sees the workaround. But, we'll make sure this is fixed in a way that makes it work out-of-the-box again soon.