https://bugzilla.suse.com/show_bug.cgi?id=1174285 https://bugzilla.suse.com/show_bug.cgi?id=1174285#c9 Ignaz Forster <iforster@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@suse.com Flags| |needinfo?(aschnell@suse.com | |) --- Comment #9 from Ignaz Forster <iforster@suse.com> --- Confirming. On a regular (successful) run transactional-update will call * snapper create --print-number --userdata "transactional-update-in-progress=yes" * btrfs subvolume set-default ${BTRFS_ID} ${SNAPSHOT_DIR} * snapper modify -u "transactional-update-in-progress=" ${SNAPSHOT_ID} Setting the new default subvolume in the second step seems to cause the snapshot entry in /.snapshots/grub-snapshot.cfg to disappear on the next snapper call - but only on read-write systems. Arvin, is this intentional behaviour? -- You are receiving this mail because: You are on the CC list for the bug.