Arch Linux User Repository

thanks! cofirming a working version...

Hi, @rpodgorny, @Dragonlord: I have adjusted PKGBUILD to apply mentioned patch.

Just replace lines source and sha256sums with following content except <> around URLs (I do not know, how to provide patch to PKGBUILD here, so I hope, that following way will be at least easy temporary solution, until 4.14.2 is released; I also do not know, how to format posts here in nice way). Patched package works for me.

source=(<https://secure.nic.cz/files/datove_schranky/>$pkgver/$pkgname-$pkgver.tar.xz 
    <https://gitlab.labs.nic.cz/datovka/datovka/uploads/38d47477a2bad75a6058e988cc50f08a/datovka.cpp.patch>)
sha256sums=('6676df789db928db3fb6246a196de9bcfdfb2e8ef2a6bf4912e7f02faaee364a'
        'e2cc0b97c4c2bb14e26af7893f54cd5a56b34d5e16f14dd46f188788f7b5ce3b')

prepare() {
  cd "$pkgname-$pkgver"
  patch --forward --strip=1 "src/gui/datovka.cpp" --input="${srcdir}/datovka.cpp.patch"
}

please note the current stable version is crashing constantly. the fix is here:

https://gitlab.labs.nic.cz/datovka/datovka/uploads/38d47477a2bad75a6058e988cc50f08a/datovka.cpp.patch

please add to pkgbuild until upstream releases new (fixed) version.

more info:

https://gitlab.labs.nic.cz/datovka/datovka/issues/444#note_138420

k3a: It works, thanks!

pixelfields: just rebuild "libisds". This is the common issue after every new release. Maybe this ebuild should be set to somehow force libisds rebuild.. probably by just requiring a specific version of libisds (not just any as it is now)!

Guys, after the last system update I can't start the app, getting following error:

datovka: error while loading shared libraries: libicui18n.so.63: cannot open shared object file: No such file or directory

Rebuilding the package doesn't seem to help. Is there something what I can do to solve it? Any advice?

Okay, did some further debugging and it seems to be related to openss library, becouse it seems to fail when calling its functions like:

X509_free() of BUF_MEM_free()

Anyway, installig older version of openssl (openssl-1.1.1.a-1) fixes the problem for me and now Datovka works without any crashes.

UPDATE: Datovka developer is already aware about this issue:

https://gitlab.labs.nic.cz/datovka/datovka/issues/410

It's openssl bug and should be fixed in new openssl version. So, for now just use older openssl.

Same here, I've rebuilt libisds and Datovka, but it also crashes when downloading message details. I've even removed old configuration and database files and created whole new profile to rule out database problem, but it's still the same:

terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc

But I have no idea what's wrong.

Updated Datovka and libisds as well, but it still crashes when downloading whole message content.

terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc

Any ideas?

@dragonlord: this always happens on Datovka updates and rebuilds, not on libraries updates.

Not-so-obviously, this is related to libisds, which must be rebuilt after Datovka is updated. Perhaps mention this in installation note?