How do I record this bug as affecting Lubuntu, I think I was told to
submit bugs to Lubuntu Packages Team (~lubuntu-packaging), I have no
idea how to work launch pad :P
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
Hi Agustin, after a long period of fails, I finally at least can mount
the drive via commandline script like:
> #!/bin/bash
> sudo cryptsetup luksOpen /dev/sdx# sdx#_crypt
Attention: the number "#" is not always the same. Normally it is for
e.g. "/dev/sdb1" something like "sdb5_crypt"
Good luck
Even in 2019 and Ubuntu 18.10 fully updated, I'm getting the exact same
error (on gnome-disks and nautilus)
> "Error unlocking /dev/sdb3: Failed to activate device: Operation not
permitted (udisks-error-quark, 0)".
The package libblockdev-crypto2 was already installed and installing
Hi,
affects me too after update on 18.04. After installing libblockdev-
crypto2 and system restart, I get the error:
"Error unlocking /dev/sdx1. Failed to activate device: Operation not
permitted"
I tried a lot of things:
* Start gnome-disks as root
* Open Luks and mount via cryptsetup on
I think you are experiencing a different issue and recommend you file a
new bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1757321
Title:
udisks2 must depend on
I just tried making a new disk on an 8 GB flash disk, with Ext4 + LUKS,
then tried the Live CD again - this time it worked. So, there is
something going on with both my 1 TB USB HDD, and also my internal 128
GB SSD, both of which give "Operation not permitted". But the newly
created disk does work
This is what I get:
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
seanlano, if you boot the live cd and then run "dpkg -l libblockdev-
crypto2 | cat", what do you see? How about "dpkg -l udisks2 | cat"?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
I just tried the Live CD daily build for Bionic, I still see the error
"Error unlocking /dev/sdc1: Failed to activate device: Operation not
permitted (udisks-error-quark, 0)" (see attached screenshot) when trying
to unlock a LUKS external disk with the Disks program. This comes up
regardless of if
This bug was fixed in the package udisks2 - 2.7.6-3
---
udisks2 (2.7.6-3) unstable; urgency=medium
[ Jeremy Bicha ]
* Update Vcs fields for migration to https://salsa.debian.org/
[ Iain Lane ]
* debian/rules, debian/substvars: Recommend libblockdev-crypto2 in Ubuntu
too
I just want to reiterate that, as mentioned by Stuart Bishop in Comment
#8 above, this bug also affects the Ubuntu Live USB/CD.
I've been using an Ubuntu Live USB for accessing LUKS volumes on my
systems for years. I hope that the Ubuntu 18.04 Live USB continues to
provide this functionality.
This is also being addressed in bug LP: #1754422
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1757321
Title:
udisks2 must depend on libblockdev-crypto2 and libblockdev-mdraid2
** Tags removed: rls-bb-incoming
** Tags added: rls-bb-notfixing
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1757321
Title:
udisks2 must depend on libblockdev-crypto2 and
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1757321
** Tags added: iso-testing
--
You received this bug notification because you are a member of Desktop
Packages,
I installed libblockdev-crypto2, and now I don't get the error "function
bd_crypto_luks_open_blob called but not implemented" - but I now instead
get an "Operation not permitted" error. Does anyone else have this
issue? My external disk is btrfs formatted, but that shouldn't be the
cause, I get
This also affects the Live CD, where attempting to mount encrypted
volumes for testing or rescue purposes fails with this rather scary
error.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
This was the first real shock moment today trying the bionic beta - I
could not believe how good everything seems to be, but then this really
FAT one! Unable to get any files from the backup disks... horrible
moment.
--
You received this bug notification because you are a member of Desktop
jibel, ugh, if we need the mdraid plugin, then we need a MIR for
libbytesize (as I mentioned on LP: #1735499)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1757321
Title:
udisks2
and a MIR for thin-provisioning-tools I think
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1757321
Title:
udisks2 must depend on libblockdev-crypto2 and libblockdev-mdraid2
Installing `libblockdev-crypto2` (and rebooting) worked for me. Thanks
@thejoe.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1757321
Title:
udisks2 must depend on
mdraid support is broken too and requires libblockdev-mdraid2
[8.807194] herm udisksd[1407]: failed to load module crypto:
libbd_crypto.so.2: cannot open shared object file: No such file or directory
[8.807257] herm udisksd[1407]: failed to load module mdraid:
libbd_mdraid.so.2: cannot
21 matches
Mail list logo
