incompatible library version - /usr/lib/libdislocker.so on Ubuntu Jammy

Bug #1955446 reported by Steven Shiau
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
dislocker (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

The latest version of dislocker on Ubuntu Jammy is 0.7.3-2ubuntu1:
# dpkg -l dislocker
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-==============-============-================================>
ii dislocker 0.7.3-2ubuntu1 amd64 read/write encrypted BitLocker v>

However, when running "dislocker-find", it gives:
Traceback (most recent call last):
        2: from /usr/bin/dislocker-find:26:in `<main>'
        1: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': incompatible library version - /usr/lib/libdislocker.so (LoadError)

There is no such issue when running dislocker-find (from dislocker 0.7.3-2) on Ubuntu Impish (21.10), it gives the result correctly:
# dislocker-find
No BitLocker volume found.

Tags: jammy
Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Thanks for taking your time to report this isue and help making Ubuntu better.

Marking confirmed since I get the same error message when attempting to run dislocker-find on Ubuntu Jammy.

Changed in dislocker (Ubuntu):
status: New → Confirmed
tags: added: jammy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.