Assertion failure running pwsafe (or how do you contact packager?)

I just installed flatpak to install the latest version of darktable (from flathub) on Debian GNU/Linux 12 (bookworm) and that went easily.

I then installed pwsafe for the same reason. But then I got this:

$ flatpak run org.pwsafe.pwsafe
/usr/include/c++/13.2.0/bits/stl_vector.h:1125: std::vector<_Tp,
_Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type)
[with _Tp = std::__cxx11::basic_string<wchar_t>; _Alloc =
std::allocator<std::__cxx11::basic_string<wchar_t> >; reference =
std::__cxx11::basic_string<wchar_t>&; size_type = long unsigned
int]: Assertion '__n < this->size()' failed.

Is there anything I can do to resolve this?

Or, is this a pwsafe bug that I should report at [1] or is this a flatpak packaging issue that I should report at [2]? How would you recommend that I proceed to resolve this issue?

  1. Issues · pwsafe/pwsafe · GitHub
  2. Issues · flathub/org.pwsafe.pwsafe · GitHub

Also, flatpak info org.pwsafe.pwsafe shows v1.18.2, although I was expecting 1.19.1 since it appeared in my flatpak installation at work this week (Red Hat 8).

In case of a verified app like this you should use the upstream issue tracker (unless a project states otherwise).

In case of an unverified app it depends on the issue. If some feature is not working as expected due to sandboxing (e.g. missing file access), you would report it in the Flathub project.

An issue like this I’d probably still report in the upstream project if Flathub distributes the latest upstream release.

You can also try to search for existing flatpak issues in the upstream project to see how these are handled.

Make sure you update your system & test the issue with the newest release of the app & runtime before reporting it.

Search for existing issues to avoid duplicates.

It looks like your issue was already reported & fixed: pwsafe stop with error message (/usr/include/c++/.....) · Issue #1327 · pwsafe/pwsafe · GitHub

Thanks very much for clarifying where issues should go.

I’m a little disappointed that my own searching didn’t turn up that issue in the pwsafe issue tracker, so thanks for pointing it out.

Rony says that this issue should be fixed in 1.19.1. The Version field says v1.18.2, but the commit says 1.19.1, which doesn’t make any sense to me. Since I still have the error, I would presume I actually have 1.18.2, or perhaps even 1.19.0.

$ flatpak info org.pwsafe.pwsafe
Password Safe - Password management utility

      ID: org.pwsafe.pwsafe
     Ref: app/org.pwsafe.pwsafe/x86_64/stable
    Arch: x86_64
  Branch: stable
 Version: v1.18.2
 License: Artistic-2.0
  Origin: flathub
  Collection: org.flathub.Stable
Installation: user
   Installed: 45.3 MB
 Runtime: org.freedesktop.Platform/x86_64/23.08
     Sdk: org.freedesktop.Sdk/x86_64/23.08

  Commit: 871486fabf4e6f7c8ae62b3625fe4bd3ccd9272a767599e731a1af0950d966c6
  Parent: 17893d5acce968a86b739d30910f7f4f9099393c9ac109c2caaf9037569c0841
 Subject: Update flatpak to 1.19.1 (9ebe6b5e)
    Date: 2024-07-05 11:27:35 +0000

$ flatpak info --show-commit  org.pwsafe.pwsafe

$ flatpak info --show-ref  org.pwsafe.pwsafe

$ ls ~/.local/share/flatpak/app/org.pwsafe.pwsafe/x86_64/stable
871486fabf4e6f7c8ae62b3625fe4bd3ccd9272a767599e731a1af0950d966c6/  active@

The version field is just metadata & not tied to the actual application version. If it’s not updated then Flatpak will display the wrong one (that would be another bug to report upstream).

The commit & its message are the actual indicator for the version. Since the source in the Flathub repo does indeed point to 1.19.1, it seems the bug is not fixed yet or you encountered another very similar issue.

Either way, you should report this upstream.

Thanks, Martin! Will do.