Ran the latest upgrades, including 7.2.0-1-default with dup and found out I couldn’t run flatpak update anymore.
There were no issues with the upgrade, the system booted fine.
The error it was giving was roughly (after guessing from half-localized error):
Warning: Error pulling from repo: syncfs(repo): Structure needs cleaning
After guessing around with an LLM, it was suggested to be a kernel related error instead directly linked to flatpak, and I did find a large amount of btrfs errors in the system logs:
[Mon Aug 31 13:53:11 2026] [ T31862] BTRFS error (device nvme1n1p2): root 1368 ino 231048 folio 94060544 is fixup with an empty fixup bitmap
[Mon Aug 31 13:53:16 2026] [ T38052] BTRFS error (device nvme1n1p2): root 1368 ino 231048 folio 94060544 is fixup with an empty fixup bitmap
[Mon Aug 31 13:53:21 2026] [ T41042] BTRFS error (device nvme1n1p2): root 1368 ino 231048 folio 94060544 is fixup with an empty fixup bitmap
[Mon Aug 31 13:53:26 2026] [ T40022] BTRFS error (device nvme1n1p2): root 1368 ino 231048 folio 94060544 is fixup with an empty fixup bitmap
[Mon Aug 31 13:53:31 2026] [ T38674] BTRFS error (device nvme1n1p2): root 1368 ino 231048 folio 94060544 is fixup with an empty fixup bitmap
[Mon Aug 31 13:53:36 2026] [ T34507] BTRFS error (device nvme1n1p2): root 1368 ino 231048 folio 94060544 is fixup with an empty fixup bitmap
[Mon Aug 31 13:53:42 2026] [ T38052] BTRFS error (device nvme1n1p2): root 1368 ino 231048 folio 94060544 is fixup with an empty fixup bitmap
[Mon Aug 31 13:53:47 2026] [ T39370] BTRFS error (device nvme1n1p2): root 1368 ino 231048 folio 94060544 is fixup with an empty fixup bitmap
[Mon Aug 31 13:53:52 2026] [ T38052] BTRFS error (device nvme1n1p2): root 1368 ino 231048 folio 94060544 is fixup with an empty fixup bitmap
Tried checking the filesystem, no errors. The only thing “broken” seemed to be a single file. /usr/lib/sysimage/rpm/Index.db
Since there didn’t seem to be anything wrong with the filesystem or drive, I removed the file and refresh zypper.
The error is now gone, but just thought I would bring this up, since this is a new occurrence and coincides with a new kernel version.