Package Details: dislocker 0.7.3-1

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: 27
Popularity: 1.06
First Submitted: 2014-06-02 17:25
Last Updated: 2020-11-18 00:07

Dependencies (6)

Required by (0)

Sources (1)

Latest Comments

1 2 3 4 Next › Last »

korimitsu commented on 2021-01-21 18:07

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

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

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

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

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

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

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

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

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

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

The source is available at