** Changed in: udev (Debian)
Status: New = Fix Released
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It worked for me in Hardy - until recently. Now I got the same problem
as csoler.
Created https://bugs.launchpad.net/ubuntu/+source/gnome-
mount/+bug/217749 about it.
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug
csoler, since you probably have a different problem then, can you please
open a new bug against gnome-mount and do the steps on
http://wiki.ubuntu.com/DebuggingRemovableDevices?
Do you have the chance to try this on a current Hardy live CD?
--
mounting Luks encrypted USB-HDD does not work
I'm not seeing new volumeid or udev packages in gutsy-proposed either.
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
With the new package I had success for a couple of days, but this
morning my drive did not mount, I had to manually remove (dmsetup
remove) a temp_cryptsetup_x mapping and then reattach the drive. I
still had to run gnome-mount manually to get the device to mount after
that (gnome-mount -d
Quick question: should I install updated package by myself or is it
pushed through updates? Because I didn't see any update and still have
problems.
However, I am solving the problem by entering the following command in
console:
sudo /etc/init.d/hal restart
--
mounting Luks encrypted USB-HDD
Seems that the German mirror (de.archive) is out of date (last update
from Feb 19). It's definitively on http://archive.ubuntu.com. It's also
on other mirrors (like nl.archive). Sorry, we can't do anything about
the German mirror ATM, that has to be fixed by its local admins.
--
mounting Luks
The new packages solved this problem for me.
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I installed voluemid, libvolume-id0, and udev from gutsy-proposed. My
initial testing shows it's working well for me.
For others getting this to work, add the following lines to your
/etc/apt/sources.list:
deb http://archive.ubuntu.com/ubuntu gutsy-proposed main restricted universe
multiverse
The same applies for me:
I installed a new gusty from scratch, updated to get
libvolume-id0-113-0ubuntu17
volumeid-113-0ubuntu17
udev-113-0ubuntu17
The behavior is still the same (I rebooted since then, of course):
when I insert my luks-encrypted usb key, the passwd dialog pops up, I
enter my
I just wanted to add that I do get a passwd promt every time. The device
only never gets mounted in /media although it actually gets mapped in
/dev/mapper.
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because
It seems this bug is still not fixed yet.
Today I connected external LUKS encrypted USB drive and got password
prompt.
Then I unmounted device, diconnected and connected again.
Nothing happened. However, when I sais sudo /etc/init.d/hal restart, I
got password prompt and then drive mounted
Copied to gutsy-updates.
** Changed in: udev (Ubuntu Gutsy)
Status: Fix Committed = Fix Released
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Successfully tested by at least three people (Nikolaus, Michael, Robert,
and also myself). Considering verified.
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Nikolaus, thank you for testing! This is a long-standing bug in gnome-
volume-manager and not a regression introduced by this udev update.
** Tags added: verification-done
** Tags removed: verification-needed
--
mounting Luks encrypted USB-HDD does not work reliably
Although the volume can now be properly mounted as I said above, it
seems that the patch introduces a new bug: Upon unmounting I now
occasionally get the warning about Unsafe Device Removal - even though
I didn't touch the device. This sounds very much like another race
condition to me.
--
The new packages solved this problem for me.
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs, which is a subscriber of a duplicate bug.
--
ubuntu-bugs mailing list
I installed voluemid, libvolume-id0, and udev from gutsy-proposed. My
initial testing shows it's working well for me.
For others getting this to work, add the following lines to your
/etc/apt/sources.list:
deb http://archive.ubuntu.com/ubuntu gutsy-proposed main restricted universe
multiverse
Seems that the German mirror (de.archive) is out of date (last update
from Feb 19). It's definitively on http://archive.ubuntu.com. It's also
on other mirrors (like nl.archive). Sorry, we can't do anything about
the German mirror ATM, that has to be fixed by its local admins.
--
mounting Luks
With the new package I had success for a couple of days, but this
morning my drive did not mount, I had to manually remove (dmsetup
remove) a temp_cryptsetup_x mapping and then reattach the drive. I
still had to run gnome-mount manually to get the device to mount after
that (gnome-mount -d
Quick question: should I install updated package by myself or is it
pushed through updates? Because I didn't see any update and still have
problems.
However, I am solving the problem by entering the following command in
console:
sudo /etc/init.d/hal restart
--
mounting Luks encrypted USB-HDD
** Description changed:
Binary package hint: gnome-mount
I'm using a luks encryped USB-HDD, which worked perfectly with Feisty.
But with Gutsy the HDD does not get automounted reliably.
- Most oft the time it just works for the first time when the HDD is plugged
in. Which means:
- *
I sponsored Michael's debdiff (thanks!) and accepted it into gutsy-
proposed. Please test the updated packages and give feedback here. Thank
you!
** Changed in: udev (Ubuntu Gutsy)
Status: In Progress = Fix Committed
--
mounting Luks encrypted USB-HDD does not work reliably
I can't find any updated packages even though I have
deb http://de.archive.ubuntu.com/ubuntu gutsy-proposed main restricted
universe multiverse
in my sources.list. Do I need to do something else?
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
It seems to have fixed the problem for me (I tested with the version
from http://ppa.launchpad.net/mh21/ubuntu though)
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm not seeing new volumeid or udev packages in gutsy-proposed either.
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs, which is a subscriber of a duplicate bug.
--
** Changed in: devmapper (Ubuntu Gutsy)
Status: New = Invalid
** Changed in: udev (Ubuntu Gutsy)
Importance: Undecided = High
Assignee: (unassigned) = Martin Pitt (pitti)
Status: New = In Progress
--
mounting Luks encrypted USB-HDD does not work reliably
Michael Hofmann wrote:
I didn't have any problems anymore after I installed the new packages,
but I will test it further.
I installed the update with no problem here. USB drive now works.
Haven't had time to check firewire. Thanks to all who contributed to
this fix!
--
John Ross,
I didn't have any problems anymore after I installed the new packages,
but I will test it further.
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
As long as Martin is not uploading a backport to gutsy-proposed, you can
get the necessary packages from my PPA with the following lines in your
sources.list:
deb http://ppa.launchpad.net/mh21/ubuntu gutsy main
deb-src http://ppa.launchpad.net/mh21/ubuntu gutsy main
You only need the volumeid
Michael Hofmann wrote:
Attached is the debdiff of the straightforward backport to gutsy that
seems to work for me.
** Attachment added: Debdiff of the backport to gutsy
http://launchpadlibrarian.net/11889991/udev-cryptsetup-backport-hardy.diff
Thanks a lot. How should I use this ? Do I
Attached is the debdiff of the straightforward backport to gutsy that
seems to work for me.
** Attachment added: Debdiff of the backport to gutsy
http://launchpadlibrarian.net/11889991/udev-cryptsetup-backport-hardy.diff
--
mounting Luks encrypted USB-HDD does not work reliably
Sorry to insist on a matter that may be simple to you, but:
- I installed packages udev and volumeid 113-0ubuntu16mh1 from these
repositories (checked with dpkg -l)
- I rebooted
But the behavior is still the same: when I insert my luks usb key, I get a
label in /dev/mapper, but nothing in
Thanks a million, Jan!
** Changed in: udev (Ubuntu)
Sourcepackagename: hal = udev
Status: Confirmed = In Progress
** Also affects: udev (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457616
Importance: Unknown
Status: Unknown
--
mounting Luks encrypted
This bug was fixed in the package udev - 117-4
---
udev (117-4) hardy; urgency=low
* Add debian/patches/00upstream-RUN-for-remove.patch:
- Execute RUN rules for device removals even if the device is not present
any more (like for USB devices).
- This restores the
** Changed in: udev (Debian)
Status: Unknown = New
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Seems something like my proposed patch was already in the upstream udev
git development tree...
http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=a0092d28dbb2c1c75c2fac17303b703343f03a35
See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457616 where
the original upstream
WARNING
A word of warning to those who have removed the file 65-dmsetup.rules. I
had found that this temporary fix worked quite well on all my machines,
but got burned when an automatic update of cryptsetup got installed
without me thoroughly considering the possible ramifications. The net
Thanks Jan, your patch completely fixes the problem for me with no
observed side effects (I didn't look too thorough, though). Oh, and I'm
a Gentoo user, so this fix should probably be propagated upstream.
--
mounting Luks encrypted USB-HDD does not work reliably
There is another problem with Gnome-mount.
As we know, LUKS encrypted partitions can be mounted with password
(passphrase) or with key file. When I connect LUKS formatted device,
Gnome-mount only asks me for a passphrase. There is no option for
mounting device with keyfile.
Usually majority of
The problem is originally caused by a race condition between cryptsetup
(actually libdevicemapper) and UDEV. In a UDEV system cryptsetup should
not add or remove the device node by itself but this is not so easy to
fix I think.
Anyway, it should be no problem if HAL correctly recognizes all
This is a race condition in hal, it grabs the temporary device before
the final name is decided.
** Changed in: devmapper (Ubuntu)
Status: New = Invalid
** Changed in: hal (Ubuntu)
Sourcepackagename: gnome-mount = hal
Importance: Undecided = High
Assignee: (unassigned) = Martin
Removing 65-dmsetup.rules does not help here. The LUKS volume is
correctly initialized and an entry in /dev/mapper is created but the
volume is not mounted.
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because
Attaching the 65-dmsetup.rules file for reference.
** Attachment added: 65-dmsetup.rules
http://launchpadlibrarian.net/11094539/65-dmsetup.rules
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are
Added devmapper to the affects list, since that's the package which
contains the problematic file.
** Also affects: devmapper (Ubuntu)
Importance: Undecided
Status: New
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this
Just wanted to confirm the exact same behavior. That is, it worked 100%
in Feisty then abruptly stopped in Gutsy. I just removed
/etc/udev/rules.d/65-dmsetup.rules, rebooted and encrypted removable
drives works again. Does anyone know if this is a factor of it being an
upgrade from Feisty to
... More coffee needed - I meant Feisty. Gutsy has the regression.
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Unfortunately I still occasionally get the temporary-cryptsetup mapping
left around (as shown by sudo dmsetup ls), though this is much less
frequent now. I'm afraid that race conditions are probably endemic due
to the design of udev; the way it forks processes into the background it
seems like
Just to confirm removing /etc/udev/rules.d/65-dmsetup.rules also solves
this problem on my system. No visible side effects yet.
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
I have fixed this problem by REMOVING
/etc/udev/rules.d/65-dmsetup.rules. Now there are no stale devices, the
password dialog appears every time I insert the stick, and the volume is
auto-mounted reliably.
Fedora (7) does not have any analogous file and does not have any
problems with
Horrid, Horrid! Handling of removable devices in Linux SUCKS!
It's all just too complicated, with a mess of kernel, udev, hal, gnome-
volume-manager, gnome-mount, cryptsetup... Lets have a single
monolithic kernel-based routine for the whole lot!
[Sorry, I just had to let off steam there, I
I suspect this is also related to bug #117011...
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
It is possible that the problem lies with cryptsetup. Even when
manually performing the steps
cryptsetup luksOpen /dev/sdb1 luks
cryptsetup luksClose luks
I still end up with some leaked devices. These can cause the already
setup error. For example I have
I can confirm this (won't work the first time etiher, for me) but I
think this is a hal rather than a gnome-mount issue?
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs,
I have to clarify this, I get asked for password and device mapper
device is setup correctly, but not mounted.
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
I strongly suspect this is a HAL issue, though I cannot confirm it.
This experience makes me suspect HAL:
I recompiled HAL with debugging enabled and optimization off. Then I
used gdb to step through lshal after the problem had been triggered.
Running lshal gave Dumping N devices from the
Stefan,
I think having two UUIDs is OK; as far as I know, the system should regard the
encrypted volume and the plaintext volume as separate objects (they correspond
to different devices, linked by the device mapper).
My experience with Feisty was better than yours - this stuff worked OK for me
I also have the same problem.
Mounting encryped external media don't work correctly for me since Feisty. In
Feisty it was horrible. Sometimes it worked correctly, bust most of the time it
didn't. See also this report:
https://bugs.launchpad.net/ubuntu/+source/hal/+bug/88213
Now I'm glad that
I have the same problems. First mount after reboot is OK. Subsequent
attempts either fail to popup the passphrase dialog or take the
passphrase but do not mount the drive.
In the case where the passphrase dialog did not appear, I attempted to
mount the volume by hand using
/usr/bin/gnome-mount
Instead of rebooting, you may try
sudo /etc/init.d/dbus restart
This restarts dbus and a load of daemons which are dependent on it,
including HAL. This had the same effect as a reboot for me.
humour
$ /usr/sbin/hald --version
HAL package version: 9000
I'm sorry Dave, I'm afraid I can't do
I have the same problems. The last time automount of luks encrypted
disks worked for me was with edgy.
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Attachment added: udev log of the first correcty working session (mounting
and unmounting the disk)
http://launchpadlibrarian.net/9669849/udev-working.log
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification
** Attachment added: udev log when the password dialog does not pop up
http://launchpadlibrarian.net/9669866/udev.log
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: gvm log when die password dialog pops up, but the disk
won't be mountet
http://launchpadlibrarian.net/9669868/gvm.log
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a
** Attachment added: udev log when die password dialog pops up, but the disk
won't be mountet
http://launchpadlibrarian.net/9669889/udev.log
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a
** Attachment added: gvm log of the first correcty working session (mounting
and unmounting the disk)
http://launchpadlibrarian.net/9669789/gvm-working.log
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification
** Attachment added: gvm log when the password dialog does not pop up
http://launchpadlibrarian.net/9669861/gvm.log
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: devices.txt
http://launchpadlibrarian.net/9669892/devices.txt
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
** Attachment added: dmesg.txt
http://launchpadlibrarian.net/9669897/dmesg.txt
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Attachment added: lshal.txt
http://launchpadlibrarian.net/9669903/lshal.txt
--
mounting Luks encrypted USB-HDD does not work reliably
https://bugs.launchpad.net/bugs/148003
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
70 matches
Mail list logo
