Description of problem: LUKS2 connected device Version-Release number of selected component: blivet-gui-runtime-2.2.1-2.fc33 Additional info: reporter: libreport-2.14.0 cgroup: 0::/user.slice/user-1000.slice/user/app-gnome-blivet\x2dgui-209116.scope cmdline: /usr/bin/python3 /usr/bin/blivet-gui crash_function: _add_parent_devices exception_type: blivet.errors.DeviceTreeError executable: /usr/bin/blivet-gui interpreter: python3-3.9.1-1.fc33.x86_64 kernel: 5.9.15-200.fc33.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: #1 [/usr/lib/python3.9/site-packages/blivet/populator/populator.py:116] _add_parent_devices #2 [/usr/lib/python3.9/site-packages/blivet/threads.py:53] run_with_lock #3 [/usr/lib/python3.9/site-packages/blivet/populator/helpers/luks.py:46] run #4 [/usr/lib/python3.9/site-packages/blivet/populator/populator.py:267] handle_device #5 [/usr/lib/python3.9/site-packages/blivet/threads.py:53] run_with_lock #6 [/usr/lib/python3.9/site-packages/blivet/populator/populator.py:461] _populate #7 [/usr/lib/python3.9/site-packages/blivet/threads.py:53] run_with_lock #8 [/usr/lib/python3.9/site-packages/blivet/populator/populator.py:416] populate #9 [/usr/lib/python3.9/site-packages/blivet/threads.py:53] run_with_lock #10 [/usr/lib/python3.9/site-packages/blivet/blivet.py:142] reset
Created attachment 1742020 [details] File: backtrace
Created attachment 1742021 [details] File: blivet-gui-utils.log
Created attachment 1742022 [details] File: blivet.log
Created attachment 1742023 [details] File: cpuinfo
Created attachment 1742024 [details] File: environ
Created attachment 1742025 [details] File: mountinfo
Created attachment 1742026 [details] File: namespaces
Created attachment 1742027 [details] File: open_fds
Created attachment 1742028 [details] File: program.log
Some attachments may be missing due to the fact that blivet deletes the crash report dir… (see https://github.com/storaged-project/blivet/issues/920) But here is an upstream bug report I have created: https://github.com/storaged-project/blivet/issues/919
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.