Dear util-linux@, in Debian, udisks2 2.10.1-6 (autopkg-)tests fail with util-linux 2.40, but passed with 2.39. We are not yet sure if this is directly caused by util-linux, but it seems somewhat likely. I won't get to it this week (also re: stable v2.40.1), but maybe someone else has seen this failure already? > udisks2's autopkgtest fails when tried together with util-linux 2.40. An > example can be seen here: > https://ci.debian.net/packages/u/udisks2/testing/amd64/46012968/ > > 537s ====================================================================== > 537s FAIL: test_ext4 (__main__.FS.test_ext4) > 537s fs: ext4 > 537s ---------------------------------------------------------------------- > 537s Traceback (most recent call last): > 537s File "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line 1107, in _do_udisks_check > 537s cd_fs.call_mount_sync(ro_options, None) > 537s gi.repository.GLib.GError: udisks-error-quark: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sr1 at /media/root/41b1acb1-744c-422a-9071-2dba5368a683: fsconfig system call failed: /dev/sr1: Can't open blockdev (0) > 537s > 537s During handling of the above exception, another exception occurred: > 537s > 537s Traceback (most recent call last): > 537s File "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line 725, in test_ext4 > 537s self._do_fs_check('ext4') > 537s File "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line 894, in _do_fs_check > 537s self._do_udisks_check(fs_type) > 537s File "/tmp/autopkgtest.btnhgm/build.cz4/src/src/tests/integration-test", line 1112, in _do_udisks_check > 537s self.fail('Mounting read-only device with \'rw\' option failed' > 537s AssertionError: Mounting read-only device with 'rw' option failedwith an unexpected error. > 537s Got: udisks-error-quark: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error mounting /dev/sr1 at /media/root/41b1acb1-744c-422a-9071-2dba5368a683: fsconfig system call failed: /dev/sr1: Can't open blockdev (0) > 537s Expected: 'is write-protected but explicit read-write mode requested' or 'is write-protected but `rw' option given' > > I do not understand what this error means, or what the underlying problem is. > Please investigate. For context, Debian's util-linux 2.40-7 should have everything from 2.40 stable up to a8aa0b5f154a44557f5bae5a4027bdbfe42b0323. Chris
