Comment 11 for bug 139635

Hello all,

I'll just jump in, because I'm lucky to see this today, before I upgrade my feisty systems to gutsy.

This bug has not been active for two weeks. This is a horrible situation for anyone who depends on encrypted storage for whatever reason (company laptop with sensitive data or something), and this is because, as Jani said, this change is breaking, unconditionally, a feature that users are relying on, for no obvious reason. (Where "trust me, there is a reason" does not count as obvious).

I'm more than willing to help in an effort to fix the bug, but this will not be possible for any community member or any other person who does not know the nature of the problem. As it stands now, an upgrade to gutsy simply is not an option for me.

Although, for the record, I saw it work on a system with libgcrypt.so.11 and libgpg-error.so.0 manually copied to /lib (which made me cringe, but a non-working installation makes me cringe even more.)

Please, please, please do something about this situation. At least provide us some information. I don't think leaving everything as it is is acceptable. And, concerning the "workaround" that the grandparent has suggested: This is not something that I'd like to watch some friends of mine do.

Regards,
Sebastien