Hello Michael,
that is great news, just two points I want to mention:
If you want to forward information to certain people,
please send email to both, the bugs address and the person,
e.g. use "reply all" in your mail client.
And if you get e.g. "/lib/libdislocker.so.0.7" in your backtrace
... 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
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]:
Hello Michael,
I am not involved in packaging dislocker but might have some points.
This "error 14" should mean it cannot read from memory the next
instruction to execute. This makes sense as the "ip" or "RIP" has
a value of 0xbb6 which is unlikely to contain program code.
If it is possible to
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
5 matches
Mail list logo
