Bugzilla – Bug 1055887
udisks gives wrong file system after updating systemd/udev to >= 228-25.9.1
Last modified: 2017-08-29 08:36:03 UTC
General ------- When putting http://download.opensuse.org/distribution/leap/42.3/iso/openSUSE-Leap-42.3-NET-x86_64.iso on a USB key and attaching it to a stock openSUSE Leap 42.2 system the information provided by udisks is wrong starting with systemd 228-25.9.1. It was working correctly with earlier versions of systemd/udev. When looking at the information given about the partition the first partition is wrongly identified as iso9660 where it should be vfat: Current (=wrong) behavior ------------------------- box:~ # udisksctl info --block-device /dev/sdb | grep -i idtype IdType: iso9660 box:~ # udisksctl info --block-device /dev/sdb1 | grep -i idtype IdType: iso9660 box:~ # udisksctl info --block-device /dev/sdb2 | grep -i idtype IdType: iso9660 Expected (=correct) behavior ---------------------------- box:~ # udisksctl info --block-device /dev/sdb | grep -i idtype IdType: iso9660 box:~ # udisksctl info --block-device /dev/sdb1 | grep -i idtype IdType: vfat box:~ # udisksctl info --block-device /dev/sdb2 | grep -i idtype IdType: iso9660 Last working version -------------------- box:~ # rpm -qa | egrep '^(libsystemd0|libudev1|systemd|systemd-sysvinit|udev)' | sort libsystemd0-228-25.6.1.x86_64 libudev1-228-25.6.1.x86_64 systemd-228-25.6.1.x86_64 systemd-presets-branding-openSUSE-0.3.0-28.1.noarch systemd-sysvinit-228-25.6.1.x86_64 udev-228-25.6.1.x86_64 First broken version -------------------- box:~ # rpm -qa | egrep '^(libsystemd0|libudev1|systemd|systemd-sysvinit|udev)' | sort libsystemd0-228-25.9.1.x86_64 libudev1-228-25.9.1.x86_64 systemd-228-25.9.1.x86_64 systemd-presets-branding-openSUSE-0.3.0-28.1.noarch systemd-sysvinit-228-25.9.1.x86_64 udev-228-25.9.1.x86_64 I also tested all later versions of systemd and friends (currently only 228-25.12.1). The behavior still is not correct. The above RPMs were the only ones I changed. The remaining system tested with was fully patched.
This is a duplicate of bug 1046268. For a workaround, please see bug 1046268 comment#29. *** This bug has been marked as a duplicate of bug 1046268 ***