igor2x

@jjberk, thanks for also confirming deb package. @ronys, can you please remove "flatpak" label, because it looks like from jjberk comment, this is not flatpak specific problem. ---- I can't...

@tinker2much, this is actually security feature and not a bug. I described details at bug report https://github.com/pwsafe/pwsafe/issues/1094 Work-around solutions: 1. Copy/move your database file .pswafe3 and/or .ibak files to $HOME/.var/app/org.pwsafe.pwsafe/config/pwsafe...

@ronys, I have already explained what are the benefits of flatpak in https://github.com/pwsafe/pwsafe/issues/562#issuecomment-1700899895, benefits like sandboxed app etc. Reasons to replace deb/rpm application with flatpak app: 1. Automatic update &...

@tinker2much, have you tried any of the solution I have provided in my first post of this bug report?

Flatpaks on Flathub are build for x86_64 and **aarch64**. Probably following the [flatpak route](https://github.com/pwsafe/pwsafe/issues/562) it may fix this problem as well.

Flatpaks on Flathub are build for x86_64 and aarch64. Probably following the [flatpack route](https://github.com/pwsafe/pwsafe/issues/562) it may fix this problem as well.

@MajorTomDE, I use Pinta 2.2-development from master branch as a user not as developer and I would also like to point: 1. Pinta 2.2 is not using standard menus anymore...

> Just to clarify one things, the explain output you showed for "ordinary UPDATE" shows an insert plan? Is this a mistake? Yes, it is mistake. I have now updated...

I have forgot to mentioned in original post, that attached SQLa are simplified examples. In attached UPSERT and UPDATE statements there are only 2 rows in VALUES, but in production...

We have now changed the logic from bulk-UPDATE to bulk-UPSERT for out application and it works great. Thanks for help. If this issue is of any future value, maybe leave...