Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1876804 - Segmentation fault
Summary: Segmentation fault
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: dislocker
Version: 32
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Robert Scheck
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-08 08:25 UTC by jari.kosonen4
Modified: 2020-12-29 01:15 UTC (History)
2 users (show)

Fixed In Version: dislocker-0.7.3-1.fc32 dislocker-0.7.3-1.fc33 dislocker-0.7.3-1.el8 dislocker-0.7.3-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-22 01:16:48 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description jari.kosonen4 2020-09-08 08:25:00 UTC 
Description of problem:
Segmentation fault occurs when I try use the dislocker

Version-Release number of selected component (if applicable):
dislocker by Romain Coltel, v0.7.1 (compiled for Linux/x86_64)

How reproducible:
Command line usage of dislocker

Steps to Reproduce:
1. sudo dislocker /dev/nvme0n1p3 -p ...
2.
3.

Actual results:
Segmentation fault

Expected results:
encryption of the dislocker partition

Additional info:
Same failure occurs with ZorinOS15.3 as well.
Comment 1 Eshin Kunishima 2020-12-01 14:28:46 UTC 
I met the same issue but the latest one worked. Try to build yourself.
https://github.com/Aorimn/dislocker/releases/tag/v0.7.3

> Program received signal SIGSEGV, Segmentation fault.
> 0x0000000000000f0b in ?? ()
> (gdb) bt
> #0  0x0000000000000f0b in ?? ()
> #1  0x00007ffff7f2ef13 in print_one_datum (level=level@entry=L_DEBUG, datum=datum@entry=0x55555555ab14) at /usr/src/debug/dislocker-0.7.1-17.fc32.x86_64/src/metadata/datums.c:262
> #2  0x00007ffff7f2f273 in print_datum_vmk (level=L_DEBUG, vdatum=0x55555555a9f4) at /usr/src/debug/dislocker-0.7.1-17.fc32.x86_64/src/metadata/datums.c:444
> #3  0x00007ffff7f2ef13 in print_one_datum (level=level@entry=L_DEBUG, datum=datum@entry=0x55555555a9f4) at /usr/src/debug/dislocker-0.7.1-17.fc32.x86_64/src/metadata/datums.c:262
> #4  0x00007ffff7f32a23 in print_data (level=level@entry=L_DEBUG, dis_meta=dis_meta@entry=0x55555555a720) at /usr/src/debug/dislocker-0.7.1-17.fc32.x86_64/src/metadata/print_metadata.c:247
> #5  0x00007ffff7f30a14 in dis_metadata_initialize (dis_meta=0x55555555a720) at /usr/src/debug/dislocker-0.7.1-17.fc32.x86_64/src/metadata/metadata.c:251
> #6  0x00007ffff7f2c37b in dis_initialize (dis_ctx=0x5555555592a0) at /usr/src/debug/dislocker-0.7.1-17.fc32.x86_64/src/dislocker.c:186
> #7  0x00005555555556f7 in main (argc=6, argv=0x7fffffffe488) at /usr/src/debug/dislocker-0.7.1-17.fc32.x86_64/src/dislocker-fuse.c:229
Comment 2 Fedora Update System 2020-12-13 17:14:53 UTC 
FEDORA-2020-769d151294 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-769d151294
Comment 3 Fedora Update System 2020-12-13 17:14:55 UTC 
FEDORA-EPEL-2020-d4a923e4c4 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-d4a923e4c4
Comment 4 Fedora Update System 2020-12-13 17:14:55 UTC 
FEDORA-2020-92761f9e2a has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-92761f9e2a
Comment 5 Fedora Update System 2020-12-14 00:34:01 UTC 
FEDORA-2020-92761f9e2a has been pushed to the Fedora 32 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-92761f9e2a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-92761f9e2a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2020-12-14 01:15:41 UTC 
FEDORA-EPEL-2020-d4a923e4c4 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-d4a923e4c4

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2020-12-14 01:20:22 UTC 
FEDORA-2020-769d151294 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-769d151294`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-769d151294

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 8 Fedora Update System 2020-12-14 01:28:22 UTC 
FEDORA-EPEL-2020-412a78f451 has been pushed to the Fedora EPEL 7 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-412a78f451

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 9 Fedora Update System 2020-12-22 01:16:48 UTC 
FEDORA-2020-92761f9e2a has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 10 Fedora Update System 2020-12-22 01:28:53 UTC 
FEDORA-2020-769d151294 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 11 Fedora Update System 2020-12-29 00:28:58 UTC 
FEDORA-EPEL-2020-d4a923e4c4 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 12 Fedora Update System 2020-12-29 01:15:04 UTC 
FEDORA-EPEL-2020-412a78f451 has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.