Description of problem: I had a virt-manager VM running, and I redirected a flashdrive to the virtual machine. Disks wouldn't open after un-redirecting the flashdrive. Version-Release number of selected component: udisks2-2.9.1-2.fc33 Additional info: reporter: libreport-2.14.0 backtrace_rating: 4 cgroup: 0::/system.slice/udisks2.service cmdline: /usr/libexec/udisks2/udisksd crash_function: device_open executable: /usr/libexec/udisks2/udisksd journald_cursor: s=060ed13377974d77b9539b16e664e224;i=b7a11;b=cd3487d4ec4a49f386396e20fbbe8808;m=a87804190;t=5bc2829b3180a;x=39d164b042171725 kernel: 5.10.16-200.fc33.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (9 frames) #0 device_open at lib/utils_device.c:303 #1 BITLK_read_sb at lib/bitlk/bitlk.c:470 #2 _crypt_load_bitlk.constprop.0 at lib/setup.c:988 #3 _init_by_name_crypt at lib/setup.c:1296 #4 crypt_init_by_name_and_header at lib/setup.c:1486 #5 _crypto_close at crypto.c:1132 #6 run_task_job at udisksthreadedjob.c:214 #7 g_task_thread_pool_thread at ../gio/gtask.c:1417 #9 g_thread_proxy at ../glib/gthread.c:820
Created attachment 1759310 [details] File: backtrace
Created attachment 1759311 [details] File: core_backtrace
Created attachment 1759312 [details] File: cpuinfo
Created attachment 1759313 [details] File: dso_list
Created attachment 1759314 [details] File: environ
Created attachment 1759315 [details] File: exploitable
Created attachment 1759316 [details] File: limits
Created attachment 1759317 [details] File: maps
Created attachment 1759318 [details] File: mountinfo
Created attachment 1759319 [details] File: open_fds
Created attachment 1759320 [details] File: proc_pid_status
Created attachment 1759321 [details] File: var_log_messages
*** Bug 1933231 has been marked as a duplicate of this bug. ***
Reassigning to cryptsetup. The invocation of crypt_init_by_name_and_header() from libblockdev side looks sane on a first sight.
Yes, this uncovered a bug in libcryptsetup when it is called on an active Bitlocker mapping but the underlying device already disappeared. Fix will be included in the next stable release.
Fixed by https://gitlab.com/cryptsetup/cryptsetup/-/commit/fea4074e8fc6542f43b2bd5b7507d0c08b2d7b8b
FEDORA-2021-17c262e08d has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-17c262e08d
FEDORA-2021-28e528d2b6 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-28e528d2b6
FEDORA-2021-3a694e18c9 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-3a694e18c9
FEDORA-2021-17c262e08d has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-17c262e08d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-17c262e08d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-3a694e18c9 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-2021-3a694e18c9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-3a694e18c9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-28e528d2b6 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-2021-28e528d2b6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-28e528d2b6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-17c262e08d has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-3a694e18c9 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-28e528d2b6 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.