[Bug]: password entry in state where editing or deleting freezes the application

[clayt0nk]

Bug description

Passy Flatpak v.1.10.1

On Passy Flatpak desktop, I got two password entries into a state where I could neither delete them nor edit them, as any attempt to do so resulted in Passy freezing, requiring me to manually kill the process and restart Passy. I was able to sync them to Android Passy, where I was able to delete one and edit the other. Syncing back to desktop, I can now edit the remaining, previously problematic, entry.

I so far have not been able to localize what exactly was triggering this behavior. Is there anywhere where Passy is storing logs that I can attempt to capture?

Expected outcome

No response

Steps to reproduce

No response

Error log

No response

App version

None

Submission checklist

• I have specified the problem in the issue title
• I have provided a verbose description of the problem

[GleammerRay]

Hello @clayt0nk !

While this bug most probably carries no risk to data integrity, it is concerning nonetheless.

Unfortunately, Passy does not generate any crash log files, I will look into implementing that. Even then, when fully frozen, there isn't a reasonable way to capture errors or produce logs, so that's unlikely to help the debugging, which is the main reason for my choice to have the error logs appear as in-app notifications instead.

Such issues are best resolved when there is a way to replicate them, do tell me if you find something that works at least semi-consistently. After all, this bug could just be a flatpak containerised filesystem interface quirk, as Passy is doing a lot of operations such as file write access locking/unlocking/moving in quick succession to ensure encrypted data integrity when saving at all times. Thank you!