Am 28.04.24 um 18:20 schrieb Chris Hofstaedtler:
Source: udisks2
Version: 2.10.1-6
Severity: serious

Hi,

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.

It appears that this is a regression introduced in util-linux 2.40-7.
The udisks2 test suite passes with 2.40-6.

So I assume it's one of the upstream changes from
"""
* Import upstream stable/v2.40 up to a8aa0b5f154a44557f5bae5a4027bdbfe42b0323
    * lsns: fix netns use
    * libmount: fix comment typo for mnt_fs_get_comment()
    * libmount: Fix access check for utab in context
    * lsblk: simplify SOURCES code
    * findmnt: always zero-terminate SOURCES data
    * agetty: Don't override TERM passed by the user
    * libsmartcols: reset wrap after calculation
    * lslocks: remove a unused local variable
    * lslocks: don't abort gathering per-process information even if
      opening a /proc/[0-9]* fails
* lsns: tolerate lsns_ioctl(fd, NS_GET_{PARENT,USERNS}) failing with ENOSYS * lsns: report with warnx if a namespace related ioctl fails with ENOSYS
    * Fix misplaced else in mnt_update_already_done
    * findmnt: revise the code for -I and -D option (Closes: #1069634)
    * libblkid: topology/ioctl: simplify ioctl handling
    * libblkid: topology/ioctl: correctly handle kernel types
    * pam_lastlog2: link against liblastlog
* libblkid: Fix segfault when blkid.conf doesn't exist (Closes: #1069634)
"""
that broke udisks2.

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to