ok, this is what happens in journalctl when an ISO successfully is mounted:
``` Oct 29 18:02:06 boxxy kernel: loop1: p1 p2 Oct 29 18:02:06 boxxy kernel: ISO 9660 Extensions: Microsoft Joliet Level 3 Oct 29 18:02:06 boxxy kernel: ISO 9660 Extensions: RRIP_1991A Oct 29 18:02:06 boxxy udisksd[2567]: Mounted /dev/loop1p1 at /media/tessa/Ubuntu 20.04.1 LTS amd64 on behalf of uid 1000 Oct 29 18:02:06 boxxy udisksd[2567]: Set up loop device /dev/loop1 (backed by /home/tessa/Downloads/ISOs/ubuntu-20.04.1-desktop-amd64.iso) Oct 29 18:02:07 boxxy fwupd[6497]: 01:02:07:0315 FuEngine ccgx failed to change udev device /sys/devices/virtual/block/loop1: cannot ensure ID: FuUdevDevice: Oct 29 18:02:07 boxxy fwupd[6497]: Unknown Device Oct 29 18:02:07 boxxy fwupd[6497]: Flags: none Oct 29 18:02:07 boxxy fwupd[6497]: 01:02:07:0319 FuEngine ccgx failed to change udev device /sys/devices/virtual/block/loop1/loop1p2: cannot ensure ID: FuUdevDevice: Oct 29 18:02:07 boxxy fwupd[6497]: Unknown Device Oct 29 18:02:07 boxxy fwupd[6497]: Flags: none Oct 29 18:02:07 boxxy fwupd[6497]: 01:02:07:0320 FuEngine ccgx failed to change udev device /sys/devices/virtual/block/loop1/loop1p1: cannot ensure ID: FuUdevDevice: Oct 29 18:02:07 boxxy fwupd[6497]: Unknown Device Oct 29 18:02:07 boxxy fwupd[6497]: Flags: none ``` but when I try to mount that virtio iso, it just times out, displays that error dialogue, and literally nothing goes to `journalctl`. is there a way to run it with debug logging? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901286 Title: gnome-disk-image-mounter fails after upgrade to 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1901286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
