Philippe Vaucher

Alright :smirk: thanks!

@jwiegley: not sure you answered @Mallchad 's question tho

Yeah time-based releases would be ok. Maybe a quarterly scheme would be appropriate, compute what's best based on the number of commits.

@goolhanrry: a release manager tag versions and usually keeps a changelog up to date.

I have the same problem and what is weird is that it appeared recently without touching anything else: builds from january were working fine, and now I have this NSS...

@probonopd: actually it was not! Using this works: ``` shell LD_LIBRARY_PATH="/usr/lib/x86_64-linux-gnu/nss" mybinary ``` So basically, it'd just be a matter of packaging that lib in the appimage. I'll play around...

Ok I just checked based on my latest successful build, and found out that 46a1e7f481317ecfab1804cfe7aa117bcb10e0e6 is able to build & run my Appimage. I also confirm that using `-exclude-libs="libnss3.so,libnssutil3.so"` with...

So after verifications, basically in previous versions it did not package `libnss*` but it was loaded from the system dir, because it was already installed by 3rd party packages (e.g...

Ok, another fix is doing `cp /usr/lib/x86_64-linux-gnu/nss/* lib` before building the appimage. Also it's opened by the app: ``` shell stvs@P080027f4c1bf:~/squashfs-root$ strace -f ./AppRun 2>&1 | grep libsoftokn3 [pid 4720]...

> Did you open a ticket there? No, I didn't know this was a Qt issue.