But why would
some Leap 15.1 systems mount a dirty FAT32 FS in RW mode
then in the first place? This is highly inconsistent ...
Three physical machines here, each with a Leap 15.1 install, each with
KDE. One cares about the dirty state, two do not.
I would look at the logs. Yes, it is curious.
Just looked at ´journalctl -a | grep -i sdb` (i.e. my sticks) on all
systems. Two are showing no errors. The system in question however does:
Multiple entries of `invalid cluster chain` per mount, coming from
`fat_get_cluster`, triggering an RO mount. The strange thing though is
that the mounts from the command line do not exhibit those errors.
Last time I used "fsck -f -y /dev/whatever".
But usually "fsck -a ..."
Just did `fsck.vfat /dev/sdb1` and went through all messages manually.