Package Details: dislocker 0.7.3-2

Git Clone URL: (read-only, click to copy)
Package Base: dislocker
Description: Read/write BitLocker-encrypted volumes
Upstream URL:
Licenses: GPL2
Conflicts: dislocker-git
Submitter: mrxx
Maintainer: mrxx
Last Packager: mrxx
Votes: 33
Popularity: 0.107929
First Submitted: 2014-06-02 17:25 (UTC)
Last Updated: 2021-04-29 22:23 (UTC)

Dependencies (6)

Required by (0)

Sources (1)

Latest Comments

mrxx commented on 2021-08-02 12:41 (UTC)

@korimitsu: try to uninstall and then reinstall the package.

Btw. please do not misuse the "Flag package out of date" function for reporting problems. (Install dislocker-git instead if you want to use the latest version.)

korimitsu commented on 2021-07-30 22:35 (UTC)

dislocker-fuse: error while loading shared libraries: cannot open shared object file: No such file or directory

VERSION: pamac search dislocker dislocker-noruby 0.7.3-1 AUR Read/write BitLocker-encrypted volumes (no ruby bindings/dependency) dislocker-git 0.7.1.r0.g3939a18-1 AUR FUSE driver to read/write Windows' BitLocker-ed volumes dislocker [Installed] 0.7.3-2 AUR Read/write BitLocker-encrypted volumes

jackdanielz commented on 2021-04-29 17:36 (UTC)

There is an issue to build with ruby 3.0. I suppose a tag has to be created in git and the package be updated.


korimitsu commented on 2021-04-26 09:19 (UTC) (edited on 2021-04-26 09:19 (UTC) by korimitsu)

Fix this library issues:

sudo ln -s /usr/lib/ /usr/lib/

mrxx commented on 2021-02-01 18:27 (UTC)

Seems to be a Manjaro-specific problem then, I've got no problems on an up-to-date Arch system.

ignilux commented on 2021-02-01 18:16 (UTC)

Thanks for that, I can confirm that the fix in korimitsu's comment worked for me as well. Running 5.10.7 kernel via Manjaro.

korimitsu commented on 2021-01-21 18:07 (UTC)

Error: dislocker-fuse: error while loading shared libraries: cannot open shared object file: No such file or directory

Fix with: sudo ln -s /usr/lib/ /usr/lib/

luckdragon commented on 2020-05-24 00:32 (UTC)

This did not compile for me, I had to update the /usr/include/ruby-2.6.0/ path to 2.7.0

mrxx commented on 2019-09-29 12:42 (UTC)

haobinnan's fix has already been backported to Aorimn's git repo:

Therefore, there is no need to use some third-party repo. Just install dislocker-git to fix the issue.

This package (dislocker) was created to provide stable releases; unfortunately, the last upstream release package is from 2017. There is already a request for a new release:

ManU commented on 2019-09-29 07:40 (UTC)

here is the updated package build in addition to @Tom-1234 comment:

Maintainer: mrxx <mrxx at cyberhome dot at>

pkgname=dislocker pkgver=20190929 pkgrel=5 pkgdesc="Read/write BitLocker-encrypted volumes" arch=('i686' 'x86_64') url="" license=('GPL2') depends=('fuse' 'mbedtls' 'ruby') makedepends=('make' 'cmake') conflicts=('dislocker-git') optdepends=('ntfs-3g: NTFS file system support') source=('dislocker::git+') sha1sums=('SKIP')

build() { cd "$srcdir/$pkgname"

cmake -DCMAKE_INSTALL_PREFIX=/usr \ -Dlibdir=/usr/lib \ -DC_INCLUDE_PATH="$C_INCLUDE_PATH:/usr/include/ruby-2.6.0/" \ -D WARN_FLAGS:STRING="-Wall -Wextra" \ . make }

package() { cd "$srcdir/$pkgname" make DESTDIR="$pkgdir/" install

install -Dm644 ${pkgdir}/usr/share/doc/${pkgname}/README install -Dm644 ${pkgdir}/usr/share/doc/${pkgname}/CHANGELOG install -Dm644 LICENSE.txt ${pkgdir}/usr/share/licenses/${pkgname}/LICENSE }

Tom-1234 commented on 2019-07-26 11:10 (UTC)

Hello, there were problems (segmentation fault) after the upgrade to Win10 19.03, see Thankfully a fixed was prepared by haobinnan and is now available in the develop branch. I made a brief test and at least it works for me. Just as info for those running in the same issue. Kudos to haobinnan and Aorimn.

mrxx commented on 2019-07-23 16:59 (UTC)

alu1, I still can't reproduce the problem neither on my production machines nor on fresh test installations, it compiles fine with current ruby-2.6.3 everywhere.

Maybe this problem occurs only on systems with multiple (possibly outdated) versions of ruby installed in parallel. Because of this, I have added the path to the 2.6.0 includedir of ruby. Thank you for your feedback on this issue and kudos to GI_Jack for the fix.

alu1 commented on 2019-07-23 14:09 (UTC)

Package doesn't build with current Ruby2.6. Appreciate dependency is listed as legacy Ruby1.8, but that package doesn't build from AUR either. Can confirm GI_Jack's kludge to the PKGBUILD from March fixes inability to find <ruby.h>

mrxx commented on 2019-06-06 01:01 (UTC)

Thanks, BoneTone. Dislocker was not able to write to all types of Bitlocker volumes for some time after I created the package. This has changed over time, nowadays the upstream description states it is able to write to most versions of Bitlocker volumes.

As both the package description and upstream url were outdated, I've updated the PKGBUILD to reflect these changes.

BoneTone commented on 2019-06-05 18:32 (UTC)

Thanks mrxx. One other quick question, the description for this package states that it is to create a read only mount of dislocker encrypted volumes (there is even another package on the AUR for read/write capabilities). However, using this (your) package I am able to write to the encrypted volume once I've decrypted & mounted it. Should the description be updated, or is there a bug? Personally, I am pleased that it is able to write to the volume, and would prefer to keep it that way.

mrxx commented on 2019-06-04 13:19 (UTC)

Indeed, the upstream URL is no longer valid. I'll update it when there is a new upstream release.

The source is available at

BoneTone commented on 2019-06-04 03:16 (UTC)

Is the upstream URL correct? It seems to be redirecting me to an unrelated page. Was hoping to take a look at the code and see if I can improve some error handling when the user submits the wrong user password for a volume.

mrxx commented on 2019-03-11 10:21 (UTC)

GI_Jack, no problems here compiling dislocker on multiple production machines as well as on fresh test VMs.

GI_Jack commented on 2019-03-10 22:43 (UTC)

Looks like it fails compile trying to find ruby.h. Have some kludge:

mrxx commented on 2019-01-23 01:48 (UTC)

pacman calls ldconfig when updating libraries, so most probably it recreated the cache for you.

auroq commented on 2019-01-22 20:23 (UTC)

Hmm. I haven't had a chance to look at this for a while, but today I updated again and re-built and reinstalled dislocker. Now I have no issues. Didn't even have to recreate the linker cache...

mrxx commented on 2019-01-17 15:38 (UTC)

auroq, no problems here with ruby 2.6. Maybe your linker cache is broken. Try to recreate it (as root: ldconfig) Then rebuild the package.

auroq commented on 2019-01-17 01:14 (UTC)

This broke for me after ruby updated to 2.6. I got a message about being missing when trying to mount my drives.

I downgraded back to 2.5 to fix the issue. I haven't investigated enough to know if this could be fixed in the package here or if it's an issue with the source, but I thought I'd comment here in case anyone else has issues.

madman_xxx commented on 2018-11-25 23:09 (UTC)

My bad, was missing that package... Sorry. Classic 'Layer 8 problem' :)

mrxx commented on 2018-11-25 13:13 (UTC)

madman_xxx, please follow "Ensure the base-devel package group is installed"

madman_xxx commented on 2018-11-24 18:25 (UTC) (edited on 2018-11-24 18:25 (UTC) by madman_xxx)

I have just tried to build this package on a fairly fresh Arch installation and couldn't: "No CMAKE_C_COMPILER could be found." Please include gcc as build-time dependency.

mrxx commented on 2017-02-09 17:19 (UTC)

In v0.7.1, upstream made a mistake in the build script for the man pages. I noticed that and put a workaround in the PKGBUILD. 15 hours later, upstream discovered their error, too. Unfortunately, they decided to do the commit without a new version number, resulting in a tar.gz with the same name, but different sha1sum.

nticompass commented on 2017-02-09 15:31 (UTC) (edited on 2017-02-09 15:31 (UTC) by nticompass)

sha1sum isn't correct. I downloaded the file manually and the sha1 was 0c5c62f63ba587663eb0474f1bd6ca7e345fe977

mrxx commented on 2017-02-08 19:21 (UTC)

Updated to 0.7.1.

mrxx commented on 2017-01-11 21:03 (UTC)

Fixed potential compilation issue due to useless warnings as reported by misty.

misty commented on 2017-01-11 13:43 (UTC) (edited on 2017-01-11 13:50 (UTC) by misty)

I'm unable to make the pkg. Getting this error: In file included from /usr/include/ruby-2.4.0/ruby.h:33:0, from /home/user/builds/dislocker/src/dislocker-0.6.1/include/dislocker/ruby.h:35, from /home/user/builds/dislocker/src/dislocker-0.6.1/include/dislocker/accesses/accesses.h:38, from /home/user/builds/dislocker/src/dislocker-0.6.1/src/dislocker.c:36: /usr/include/ruby-2.4.0/ruby/ruby.h: In function ‘rb_scan_args_set’: /usr/include/ruby-2.4.0/ruby/ruby.h:2339:8: error: unused parameter ‘varc’ [-Werror=unused-parameter] int varc, VALUE *vars[]) ^~~~ cc1: all warnings being treated as errors make[2]: *** [src/CMakeFiles/dislocker.dir/build.make:63: src/CMakeFiles/dislocker.dir/dislocker.c.o] Error 1 make[1]: *** [CMakeFiles/Makefile2:203: src/CMakeFiles/dislocker.dir/all] Error 2 make: *** [Makefile:128: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting... Any help or pointer is appreciated. EDIT: added: -D WARN_FLAGS:STRING="-Wall -Wextra" as per INSTALL.rm from github and now it compiles.

mrxx commented on 2016-03-13 19:39 (UTC)

Updated to 0.6.1.

mrxx commented on 2016-01-06 20:49 (UTC)

Updated to 0.5.1.

guzzard commented on 2015-10-01 21:44 (UTC)

thanks mrxx! working fine again now

parnmatt commented on 2015-09-28 15:41 (UTC)

Confirmed, successful build Thanks for the swift response.

mrxx commented on 2015-09-27 23:29 (UTC)

Fixed regression caused by transition from polarssl to mbedtls.

guzzard commented on 2015-09-27 20:34 (UTC)

I think some issue started to occur with the update of package mbedtls 2.1.1-1 on the 21th of Sept. After that date dislocker stopped working with this error message "error while loading shared libraries: cannot open shared object file: No such file or directory". I manually added a symlink " ->", and then the error message dislocker error message changed to "symbol lookup error: /usr/lib/ undefined symbol: sha256" So seems like some incompatibility was introduced when the mbedtls package was updated. I sent a mail to Romain, the creator of dislocker.

parnmatt commented on 2015-09-27 15:15 (UTC)

Dislocker was working last time I used it [Fri 24 Apr 22:56:08 BST 2015], however today it failed to find a library. I rebuilt it to be given a build failure: ==> Starting build()... In file included from ./dislocker.h:29:0, from accesses/accesses.h:27, from dislocker.c:28: ./encommon.h:34:26: fatal error: polarssl/aes.h: No such file or directory compilation terminated. make: *** [dislocker.o] Error 1 make: *** Waiting for unfinished jobs.... make: *** wait: No child processes. Stop. ==> ERROR: A failure occurred in build(). Aborting... cc -Wall -Werror -Wextra -Wconversion -DPROGNAME=\"dislocker\" -DVERSION=\"0.4.0\" -D_FILE_OFFSET_BITS=64 -DAUTHOR="\"Romain Coltel\"" -D__OS=\"Linux\" -D__ARCH=\"x86_64\" -D__ARCH_X86_64 -D__LINUX -I. -I/usr/local/include -fstack-protector -fPIC -D_FORTIFY_SOURCE=2 -O1 -c -o dislocker.o dislocker.c cc -Wall -Werror -Wextra -Wconversion -DPROGNAME=\"dislocker\" -DVERSION=\"0.4.0\" -D_FILE_OFFSET_BITS=64 -DAUTHOR="\"Romain Coltel\"" -D__OS=\"Linux\" -D__ARCH=\"x86_64\" -D__ARCH_X86_64 -D__LINUX -I. -I/usr/local/include -fstack-protector -fPIC -D_FORTIFY_SOURCE=2 -O1 -c -o common.o common.c cc -Wall -Werror -Wextra -Wconversion -DPROGNAME=\"dislocker\" -DVERSION=\"0.4.0\" -D_FILE_OFFSET_BITS=64 -DAUTHOR="\"Romain Coltel\"" -D__OS=\"Linux\" -D__ARCH=\"x86_64\" -D__ARCH_X86_64 -D__LINUX -I. -I/usr/local/include -fstack-protector -fPIC -D_FORTIFY_SOURCE=2 -O1 -c -o config.o config.c Makefile:115: recipe for target 'dislocker.o' failed It looks like something is missing from the build.