-
Notifications
You must be signed in to change notification settings - Fork 291
Cryptsetup segfaults #53
Comments
Have you tried plain encryption? |
@Grimler91 Lacking of some encryption algorithms in kernel shouldn't cause crash. Downgrading of libdevmapper fixes the problem. |
libdevmapper which works correctly: |
@xeffyr which devices/android versions did you test? There is a newer libdevmapper version available, I'll see if that fixes it, or if rebuilding cryptsetup is enough |
2.02.177 works but neither 2.03.02 or 2.02.183 works. I'll downgrade the package for now and add this to my list of stuff to look into |
Should work again after a pkg upgrade. Let me know otherwise |
Alright it no longer segfaults, so I guess from that perspecive this issue can be closed. I still am unable to open my encrypted disks.
So I am still trying to figure out why that is |
Ah, a false lead. My other device (where everything has been working displays the same result. |
Hi, just got a new phone so I have all kinds of new problems
Problem description
Cryptsetup is segfaulting when trying to open or create a LUKS encrypted device
Steps to reproduce
To create a new encrypted device
or to open a previously encrypted one
both result in a segfault.
Here's the logcat output about this
Expected behavior
It did work for many month like this on my previous phone, which was Android 7.1 arm64.
Additional information
The text was updated successfully, but these errors were encountered: