This looks to be the same bug I have been trying to analyze in Ubuntu bug #148003. It was reported there that the existence of this stale device node often prevents auto-mounting of encrypted USB memory sticks, etc.
There appears to be a race condition in the processes spawned by udev. The file /dev/mapper/temporary-cryptsetup-XXXX is created and then almost immediately destroyed. But it appears that the "remove" event gets processed before the "add" event is finished, with unfortunate results.
This looks to be the same bug I have been trying to analyze in Ubuntu bug #148003. It was reported there that the existence of this stale device node often prevents auto-mounting of encrypted USB memory sticks, etc.
There appears to be a race condition in the processes spawned by udev. The file /dev/mapper/ temporary- cryptsetup- XXXX is created and then almost immediately destroyed. But it appears that the "remove" event gets processed before the "add" event is finished, with unfortunate results.