That's a shame, I think I solved it tonight on my box. (see the other thread)

Partial solution:

on my Asus EEE PC 900A:
- Recompile cryptsetup (upgrading to 1.1.2)
- Upgrade to Robby Workman's Xfce pack for 13.1
- Go with first suggestion on commenting out dm rules file
(the SD card crypto device mounted fine before, but my USB hard drive with sdb2 and sdb3 being separate LUKS partitions would not mount properly)

On my Sony laptop, right now it works fine (knock on wood) just by upgrading cryptsetup and Xfce.

While this may not be a security issue, I am highly disappointed that Pat has not put out fixes for this, and that it was not identified during testing. I'll have to search my email but I could swear I brought this up before release.

It still doesn't work reliably even with the new cryptsetup, new lvm2, xfce-4.6.2, the bogus udev rule in 10-dm.rules gone, and so on. It works fine on an MMC card here, but not on a usb thumb drive. I'm glad it works fine on your hardware, but the fact remains that it is NOT fixed.

Yes, you did mail about it before the release, and I had no time to reproduce it at that point. Even so, I doubt that it would have been a release blocker anyway - worst case scenario, you can still mount the partition from the command line.

A true fix for this is almost surely going to require digging into how exo or thunar or thunar-volman or some other part of xfce handle this (and perhaps the same for kde - I don't know if it works reliably there or not), and that will require more knowledge of C than I have.

A while ago in another thread I reported about my success after upgrading to cryptsetup 1.1.2. Before the upgrade, even the command line did not work. The hardware I'm talking about is an external USB hard drive.

First of all: Congratulations and all the best, Robby!

Not sure, if the following is related to the topic discussed here, but possibly it is.

I am on Slackware64 13.1 stable. When I boot my machine, while an external USB disk with a LUKS encrypted partition on it, a dialog asking for the LUKS passphrase pops up in KDE. I enter the passphrase, and the dialog is closed. Nothing else seems to happen, and there's no Dolphin window showing the file system.
Now, on the left side in Dolphin there's an icon for the LUKS device. Clicking with the left mouse button on it has no effect. But if I click onto it with the right mouse button, I can select an option to disconnect the device. Doing so and then clicking on the icon with the left mouse button brings up the passphrase dialog, again. This time the passphrase is accepted and a Dolphin window opens showing the file system on the encrypted partition on the USB device. Sometimes this fails, but in most cases it works, while the first attempt right after starting KDE almost always fails.

However, this seems all have to do with a timing problem. If I wait a couple of minutes after starting KDE, before I enter the LUKS passphrase in the dialog window, it usually works as expected. It fails, if I do it immediately when the passphrase dialogs pops up.

Plus: I don't have the problem, if I boot with no USB disk connected. If I connect the device after starting KDE, everything is working just fine in nine out of ten cases (not in ten out of ten, I have to say).

HTH.

gargamel