this sounds like a more general problem, though -- I bet you can also reproduce this with normal unencrypted USB sticks. Anyway, I think it's worth filing a new bug about it. I guess what happens is that nothing checks the state of USB devices after resuming, and thus there is never a "remove" event for the device. This requires some more thorough discussion what the right solution is.
komputes,
this sounds like a more general problem, though -- I bet you can also reproduce this with normal unencrypted USB sticks. Anyway, I think it's worth filing a new bug about it. I guess what happens is that nothing checks the state of USB devices after resuming, and thus there is never a "remove" event for the device. This requires some more thorough discussion what the right solution is.