[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nautilus (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. A new version of Nautilus is available on Maverick and we
are wondering if this bug is still an issue for you with that version?
Could you please test and comment back? Thanks in advance.
** Changed in: nautilus
** Package changed: ubuntu = cryptsetup (Ubuntu)
--
LUKS automount fails with jaunty
https://bugs.launchpad.net/bugs/363426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Package changed: cryptsetup (Ubuntu) = nautilus (Ubuntu)
--
LUKS automount fails with jaunty
https://bugs.launchpad.net/bugs/363426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: nautilus (Ubuntu)
Importance: Undecided = Low
--
LUKS automount fails with jaunty
https://bugs.launchpad.net/bugs/363426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I discovered a downside to 9R's workaround. On my Thinkpad R51, each
time I run the 9R workaround, NetworkManager believes an new wireless
interface has been added. I haven't figured out the root cause, but the
ultimate effect seems to be multiple wpa_supplicant's trying to
authenticate with the
I encounter this problem intermittently with an up-to-date jaunty. The sequence
I see is:
1. Log in.
2. Plug-in external USB hard disk with a single partition, encrypted with LUKS.
3. I get the password prompt and type in my password.
Then sometimes I get 4a, sometimes 4b.
4a. The LUKS
I'm not sure if we are having the same issue here, but you may want to
look into Bug #484429 which describes similar behavior as well as a
workaround.
==
Steps to reproduce 484429:
1) Go into palimsest (disk utility) and create an encrypted partition on an
external disk.
2) Quit Palimsest
3)
I can confirm this Bug with 3 different Ubuntu Jaunty Systems (2x x86, 1x
amd64) and 2 different USB devices (1x USB-HDD, 1x usb-flash-stick). Both USB
devices share a LUKS partition besides an unencrypted one, both times the LUKS
Partition is the second Partition.
The USB-HDD also has a
Same problem with an upgraded kubuntu jaunty.
1- I plug an USB with only one luks partition, nothing happens
2- I open dolphin, and see a Volume (crypto_luks)
3- I click on it and enter the password.
4- /dev/mapper/luks_crypto_[UUID] is created but nothing is mounted.
The workarround described
Same problem continues with the current Jaunty, as of today (July 24,
2009). The workaround described by 9R above works fine.
--
LUKS automount fails with jaunty
https://bugs.launchpad.net/bugs/363426
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm not sure if these aren't two unrelated issues. I can confirm Xoby's
original bug report and 9R's workaround.
--
LUKS automount fails with jaunty
https://bugs.launchpad.net/bugs/363426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This works very erratically for me.
Sometimes it prompts for the password when i plug in the usb-drive, after which
I still have to mount /dev/mapper/luks_crypto_#drive-id# manually.
Sometimes it does nothing when i plug in the drive, and I have to mount
/dev/sdc1 with cryptsetup luksOpen,
With a new install of Kubuntu 9.04, I have the same of problem as faithful:
- no problem with encrypted root swap
- KDE doesn't ask for password with removable (luks) encrypted volumes.
As soon as I do a sudo cryptsetup luksOpen, I get a notification to
open the corresponding decrypted fs.
--
It works again here. No problem with file:/// and whatsoever.
--
LUKS automount fails with jaunty
https://bugs.launchpad.net/bugs/363426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
For me the workaround does NOT work. The attached and decrypted drive is
still not being automounted!
@faithful: file:/// was removed from Nautilus a while back, if I recall
correctly.
@madhusudansingh: I think your problem is a different one and has
nothing to do with this bug report. You have
@ V for Vortex
file:/// was removed from Nautilus a while back, if I recall correctly.
I use KDE4 but the message is similar.
I haven't upgraded from Intrepid but installed a fresh new Jaunty (Kubuntu).
I haven't any problem with my luks encrypted root and swap partitions.
For me the problem is
Yes, it works again but I receive a warning about the position file:/// that
doesen't exist.
Can anyone confirm this issue?
--
LUKS automount fails with jaunty
https://bugs.launchpad.net/bugs/363426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
The situation is worse than this bug report would indicate.
Upgraded Ibex to Jaunty (Kubuntu) using the upgrade tool.
Now, I do not get a password prompt to enter my luks password to unlock the
encrypted LVM.
It drops me on to a BusyBox shell with an (initramfs) prompt. Error
message :
Check
Good news !
With the last updates, LUKS encrypted partitions automount works again.
Could others confirm ?
--
LUKS automount fails with jaunty
https://bugs.launchpad.net/bugs/363426
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I can confirm the bug and the workaround. I have two partitions on the
disk, first is FAT, second is LUKS. More information or tests available
on request.
-Peter
--
LUKS automount fails with jaunty
https://bugs.launchpad.net/bugs/363426
You received this bug notification because you are a
If there are more than one encrypted partitions on the usb drive some of
them are mounted after entering the correct passphrase, while others
are not.
Workaround:
Running
$ sudo udevadm trigger
in a shell after you have entered the passphrase(-s) will mount the
missing drives.
--
LUKS
Sorry, my previous description of the workaround was mot complete.
The Workaround goes like this:
After entering the passphrase in the dialog you have to restart hal
first:
$ sudo /etc/init.d/hal restart
Than trigger udev:
$ sudo udevadm trigger
now the drive should be mounted.
--
LUKS
23 matches
Mail list logo
