Quote:
Originally Posted by ownedbycats
Yes, I've been able to replicate the dirty bit issue by leaving a kepub open during connect.
|
Quote:
Originally Posted by ownedbycats
I should also note that this also happens to me on 4.30. (It would explain the handful of scan&fix errors I was getting prior to my initial 4.31 upgrade.)
|
What I managed to get with a kepub open during connect was a read-only mount. Again, I couldn't reliably duplicate it.