<kinghat:matrix.org> if i try to change the flatpaks blockchain location to the default appimage location: /home/kinghat/.bitmonero/lmdb/ i get this warning and the path comes out:

<kinghat:matrix.org> mrelay.p2pool.observer/m/matrix.org/VanhrtrTleCzauKENbfczuVd.png (image.png)

<kinghat:matrix.org> mrelay.p2pool.observer/m/matrix.org/GiQzSDbPdUjjSMoxnNAgMFzT.png (image.png)

see monero-project/monero-gui #3941

<kinghat:matrix.org> ok that makes sense. maybe the flatpak should just be granted access to .bitmonero by default 🤔

<kinghat:matrix.org> gave the flatpak access to ~/.bitmonero and now i get:

<kinghat:matrix.org> mrelay.p2pool.observer/m/matrix.org/nayzJDHpNsoNnoHuMDciDICA.png (image.png)

<kinghat:matrix.org> oh ok, you have to select the .bitmonero dir and not lmdb dir.

<kinghat:matrix.org> picking up the blocks not synced from closing the node from appimage yesterday:

<kinghat:matrix.org> mrelay.p2pool.observer/m/matrix.org/ZdsUvmOXlZsvSZYJdxEXrImn.png (image.png)

<kinghat:matrix.org> ands its starting the verifying all over again after syncing up:

<kinghat:matrix.org> mrelay.p2pool.observer/m/matrix.org/RtTQKPAjdRmnIvhzOrfupewy.png (image.png)

so is this with flatpak or not?

seems you used flatpak again?

<kinghat:matrix.org> ya i went back to flatpak after testing the appimage.

I don't know what the issue is, maybe a permission issue with the flatpak sandbox.

If the wallet cache can't be written, it will restart the next time.

<kinghat:matrix.org> once its(the flatpak) done verifying i can go open the appimage again and see if it verifies from the start as well.

<kinghat:matrix.org> selsta: this is most likely whats happening. odd nobody else has mentioned it though.

.merge+ 4600

Added