Thanks for your report. This looks like a "should not happen (TM)" situation. Can you reproduce this by running
sudo /lib/udev/devkit-disks-part-id /dev/block/8:21
? Does that crash, or give you some output? (Please just copy&paste the entire output here if you are unsure). Can you please also do
devkit-disks --dump > /tmp/dkd.txt udevadm info --export-db > /tmp/udev.txt
and attach /tmp/dkd.txt and /tmp/udev.txt here?
Thanks!
Note to self: This happens because udev_device_get_devnode (device) == NULL, with device being a valid udev_device from a valid drive sysfs path.
Thanks for your report. This looks like a "should not happen (TM)" situation. Can you reproduce this by running
sudo /lib/udev/ devkit- disks-part- id /dev/block/8:21
? Does that crash, or give you some output? (Please just copy&paste the entire output here if you are unsure). Can you please also do
devkit-disks --dump > /tmp/dkd.txt
udevadm info --export-db > /tmp/udev.txt
and attach /tmp/dkd.txt and /tmp/udev.txt here?
Thanks!
Note to self: This happens because udev_device_ get_devnode (device) == NULL, with device being a valid udev_device from a valid drive sysfs path.