Bug#954950: dislocker reports memory access error / segfault after call

2020-03-27 Thread Michael Wurm
... the dumps gave the answer: dislocker 0.7.1-5~bpo10+1 depends on libdislocker0.7.1-5~bpo10+1. On the used systems the dependency was not resolved. Instead libdislocker0.7.1-4+b1 was installed, which triggered the crash. Solved, Michael

Bug#954950: dislocker reports memory access error / segfault after call

2020-03-27 Thread Michael Wurm
Dear Bernhard, Journalctrl reveals no more information here. I generated with cordump a trace: syslog report: systemd-coredump[8550]: Process 8548 (dislocker) of user 0 dumped core.#012#012Stack trace of thread 8548:#012#0  0x0bb6 n/a (n/a) systemd[1]: systemd-coredump@1-8549-0.ser

Bug#954950: dislocker reports memory access error / segfault after call

2020-03-25 Thread Michael Wurm
Package: dislocker Version: 0.7.1-5~bpo10+1 Severity: important Dear Maintainer, i found an issue with dislocker on my current debian 10 install. - I created different bilocker encrypted partitions in Win10 (NTFS, Win10 Version 1909). - During creation I selected different encryption methods (Ne