This package has been removed from Ubuntu. Closing all related bugs.
** Changed in: gnome-mount (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/296750
This bug still exists in lucid. When it occurs, you can manually fix it
once using hal-set-property, but on the next occasion it reoccurs of
course.
Could one of those familiar with the mount-process in hal please shed
some light on the issue? Especially it would help if you could give any
hint
I have this problem as well, and what's more confusing is it just
started. The volume used to work by clicking the item in nautilus, now
it always fails by asking for the password over and over. However, the
mapper entry is being created it's jsut being mounted. I can go into a
command line and
I switched back to using gnome on lucid, and the problem doesn't occur
any more.
--
special device /dev/dm-0 does not exist when mounting an encrypted drive
https://bugs.launchpad.net/bugs/296750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm having the same problem with ubuntu lucid. I'm using xfce, though,
which I installed before updating from karmic. Strangely, I didn't have
the problem before updating, but as it seems to show up irregularly I
was just lucky, I guess...
--
special device /dev/dm-0 does not exist when mounting
I'm seeing this on karmic kubuntu (my laptop) on a disk that has been
working fine up until now. It works fine on my desktop machine (also
running karmic, but with the newer KDE from backports).
--
special device /dev/dm-0 does not exist when mounting an encrypted drive
I have this problem using karmic koala and thunar-volman, so it looks
like this is still an issue. Was there a fix ever provided?
--
special device /dev/dm-0 does not exist when mounting an encrypted drive
https://bugs.launchpad.net/bugs/296750
You received this bug notification because you are
I further investigated this issue and found out the following:
Whenever it works, the hal entry for the unlocked device, which should get
mounted, contains the following line:
block.device = '/dev/mapper/luks_crypto_fb656bfe-460b-4437-97d6-93bb6e9e66c4'
(string)
Whenever it doesn't work,
I wonder why this has an importance=low as it breaks encrypted disks,
but well.
If I do lshal I get the following (among others):
block.device = '/dev/dm-3' (string)
linux.sysfs_path = '/sys/devices/virtual/block/dm-3' (string)
This sysfs_path does indeed exist. So it's probably udev
Or HAL not agreeing with udev about the device's location, FWIW.
--
special device /dev/dm-0 does not exist when mounting an encrypted drive
https://bugs.launchpad.net/bugs/296750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: gnome-mount (Ubuntu)
Importance: Undecided = Low
--
special device /dev/dm-0 does not exist when mounting an encrypted drive
https://bugs.launchpad.net/bugs/296750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Same problem for me but not with all devices.
My old encrypted USB stick is mounted without problems. But the one I
created recently can only be mounted the manual way most of the time.
Strange...
--
special device /dev/dm-0 does not exist when mounting an encrypted drive
With ubuntu 7.10 I had no problem mounting the encrypted partition on my
usb drive. However with 8.10 mounting the partition does not work most
of the time. Manually I can mount with commands like sudo mount
/dev/mapper/luks_crypto_ac639614-9758-4555-9c97-90d4796d9c8b /mnt as
mentioned before.
--
Same problem here. The mapper is created and manually mounting
/dev/mapper/* does work. It fails via Places.
--
special device /dev/dm-0 does not exist when mounting an encrypted drive
https://bugs.launchpad.net/bugs/296750
You received this bug notification because you are a member of Ubuntu
** Changed in: gnome-mount (Ubuntu)
Status: New = Confirmed
--
special device /dev/dm-0 does not exist when mounting an encrypted drive
https://bugs.launchpad.net/bugs/296750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I see this same problem.
The question is, what is looking for /dev/dm-0 and why? That will never
exist, will it?
--
special device /dev/dm-0 does not exist when mounting an encrypted drive
https://bugs.launchpad.net/bugs/296750
You received this bug notification because you are a member of
I'm not sure about that.
/dev/dm* are temporary device mappers if I am not mistaken. They used to be
associated with LVM which would make perfectly sense, as I have a logical
volumes in the encrypted drive. However I read somewhere that some volatile
devices like flash cards also use /dev/dm*
When mounting manually, the standard way is to map the encrypted drive
or partition using cryptsetup luksOpen, which automatically creates a
mapper device in /dev/mapper/chosen alias. gnome-mount (or is HAL
responsible for this?) seems to be doing it the same way, choosing an
alias
I totally agree.
For me the mapper is always correctly created. The problems occure somewhere in
the mounting process afterwards. Has anybody an idea how we could trace what's
actually going on and to which package the bug has to attributed to?
--
special device /dev/dm-0 does not exist when
I can confirm this on a freshly installed intrepid ibex.
To reproduce: Plug in a fully encrypted disk, the password dialogue pops up.
Enter password, the device mapper gets created, gnome mount rejects to mount
the drive. Quote:
Cannot mount volume.
Unable to mount the volume '[label]'.
I can confirm this problem, I have two machines, each connected to four
encrypted drives (cryptsetup,luks, different
usb 2.0, different drives from different vendors).
It is a common problem so I very often cannot mount all the drives via the menu
(Places-Removable Media-...),
but one of them
Sounds similar to bug #217749.
--
special device /dev/dm-0 does not exist when mounting an encrypted drive
https://bugs.launchpad.net/bugs/296750
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thanks for finally answering, but why do you say so? I don't see the
same error message anywhere in that thread, and the other bug is quite
old. My problem started in Intrepid.
Here are some additional details I can think of.
The most interesting thing is probably that this does not happen
** Description changed:
Intrepid, fully updated. This bug does not happen always, it happens
approximately 50% times.
Steps to reproduce:
1. Connect an USB hard drive with an encrypted partition with password stored
in GNOME keyring.
2. Enter the GNOME keyring password.
What
24 matches
Mail list logo
