Description of problem: How did this problem happen? 1) boot Fedora 39 nightly from usb-device 2) start the installer 3) see the error message How can it be reproduced? 1) try to install Fedora 39 nightly on a dell xps 9300 Comment: after the successful Test of the Fedora 39 Image, the systemd-prompt shows: "[Failed] Failed to start udisks2.service". This happens in every fedora-image with udisks2 versions 2 >= 2.10 on the dell xps 9300. I tried fedora Rawhide, fedora 39 beta and fedora 39 nightly. On my dell xps 9310 everything woks fine and udisks2 starts without any error. Version-Release number of selected component: anaconda-core-39.32.6-1.fc39.x86_64 The following was filed automatically by anaconda: anaconda 39.32.6 exception report Traceback (most recent call first): File "/usr/lib/python3.12/site-packages/dasbus/client/handler.py", line 509, in _handle_method_error raise exception from None File "/usr/lib/python3.12/site-packages/dasbus/client/handler.py", line 483, in _get_method_reply return self._handle_method_error(error) File "/usr/lib/python3.12/site-packages/dasbus/client/handler.py", line 450, in _call_method return self._get_method_reply( File "/usr/lib/python3.12/site-packages/dasbus/client/handler.py", line 382, in _get_property_value variant = self._call_method( File "/usr/lib/python3.12/site-packages/dasbus/client/property.py", line 54, in __get__ return self._getter() File "/usr/lib/python3.12/site-packages/dasbus/client/property.py", line 43, in get return self.__get__(None, None) # pylint: disable=unnecessary-dunder-call File "/usr/lib/python3.12/site-packages/dasbus/client/proxy.py", line 164, in __getattr__ return member.get() File "/usr/lib64/python3.12/site-packages/pyanaconda/modules/common/task/__init__.py", line 39, in sync_run_task while task_proxy.IsRunning: File "/usr/lib64/python3.12/site-packages/pyanaconda/ui/lib/storage.py", line 97, in reset_storage sync_run_task(task_proxy) File "/usr/lib64/python3.12/threading.py", line 989, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.12/site-packages/pyanaconda/core/threads.py", line 280, in run threading.Thread.run(self) dasbus.error.DBusError: Message recipient disconnected from message bus without replying Additional info: journalctl: Caused error: preexec_fn not supported at interpreter shutdown cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --graphical executable: /sbin/anaconda hashmarkername: anaconda product: Fedora package: anaconda-core-39.32.6-1.fc39.x86_64 reason: dasbus.error.DBusError: Message recipient disconnected from message bus without replying type: anaconda release: Fedora release 39 (Thirty Nine) cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-39-20231019-n-0 rd.live.image rd.live.check quiet addons: com_redhat_kdump nmcli_dev_list: Caused error: preexec_fn not supported at interpreter shutdown kernel: 6.5.6-300.fc39.x86_64 version: 39 other involved packages: python3-dasbus-1.7-4.fc39.noarch, python3-libs-3.12.0-1.fc39.x86_64 lsblk_output: Caused error: preexec_fn not supported at interpreter shutdown
Created attachment 1994851 [details] File: anaconda-tb
Created attachment 1994852 [details] File: backtrace
Created attachment 1994853 [details] File: os_info
Created attachment 1994854 [details] File: environ
Created attachment 1994855 [details] File: description
Created attachment 1994856 [details] File: storage.log
Created attachment 1994857 [details] File: packaging.log
Created attachment 1994858 [details] File: program.log
Created attachment 1994859 [details] File: anaconda.log
Created attachment 1994860 [details] File: dbus.log
Created attachment 1994861 [details] File: packaging.log
Oct 20 16:30:18 fedora systemd-coredump[1404]: Process 1295 (udisksd) of user 0 dumped core. Stack trace of thread 1295: #0 0x00007f27f5908834 __pthread_kill_implementation (libc.so.6 + 0x90834) #1 0x00007f27f58b68ee raise (libc.so.6 + 0x3e8ee) #2 0x00007f27f589e8ff abort (libc.so.6 + 0x268ff) #3 0x00007f27f589f7d0 __libc_message.cold (libc.so.6 + 0x277d0) #4 0x00007f27f599bcd9 __fortify_fail (libc.so.6 + 0x123cd9) #5 0x00007f27f599cf64 __stack_chk_fail (libc.so.6 + 0x124f64) #6 0x00007f27f5989178 ioctl (libc.so.6 + 0x111178) ... Can you please reproduce this crash again, then start ABRT, and hopefully, if udisks crash shows up there, use ABRT to report the udisks crash? And link it here. Thanks!
i managed to install Fedora-Workstation-Live-x86_64-39-20231020.n.0.iso, but the problem with udisks is still there. The error is reported: https://bugzilla.redhat.com/show_bug.cgi?id=2245707 Comment: I tried the live system of Ubuntu 23.10 as it ships with udisks v2.10 and I had no problems. in the live system of Fedora, no hard disk is detected until I type "udiskctl <tab for autocomplete>" in the terminal.
FEDORA-2023-0f7d8165cb has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-0f7d8165cb
This is caused by a NVMe device not conforming to the official NVM Express specification. Contact your hardware vendor for firmware update.
Let's close this in favor of the actual udisks crash in bug 2245707. *** This bug has been marked as a duplicate of bug 2245707 ***
FEDORA-2023-0f7d8165cb has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.