Package Details: zoiper 5.2.28-1

Git Clone URL: (read-only)
Package Base: zoiper
Description: a SIP and IAX2 VoIP softphone
Upstream URL:
Licenses: custom
Submitter: ava1ar
Maintainer: severach
Last Packager: severach
Votes: 54
Popularity: 0.190634
First Submitted: 2009-10-15 10:31
Last Updated: 2019-04-04 01:44

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

barbuk commented on 2018-06-30 07:04

5.2.19 is out.


Asgaroth commented on 2018-05-03 10:11

One nice fix in 5.2.16 is this:

Fixed issue with missing tray icon on Linux distros.

Which is currently wrecking my head where if I minimize to tray, I cannot re-open zoiper.

severach commented on 2018-04-27 00:11

pacaur does not halt on error or show messages in prepare(). I put it back into build.

Asgaroth commented on 2018-04-26 19:21

Thanks, the "!strip" sorted the issue out.

Just another quick question, i deleted the zoiper cache for pacaur, but when I ran "pacaur -S zoiper" for the installation, the warning message that tells you to manually download the tarball does not come up in the beginning anymore. It does however error out on the following line:

"bsdtar: Error opening archive: Failed to open '/home/username/.cache/pacaur/zoiper/zoiper5_5.2.14_x86_64.tar.xz'"

Is it possible to have that initial warning to download the release tarball prior to the build attempt?

severach commented on 2018-04-26 17:38

I'll add !strip even if it's not the problem. I usually avoid stripping commercial software. It wastes time and accomplishes nothing. strip is a strange beast, modifying executables even when there is nothing to strip.

Asgaroth commented on 2018-04-26 13:03

There is still an issue with this package. If using the application as a free package then it works fine, however, if you are a registered user then when trying to activate the license you are presented with the following error message:

"Executable checksum mismatch (5)"

Looking at the checksums of the 2 binaries, the one installed from this package:

337de3286511023a37d151b57325ada4 /usr/lib/zoiper/zoiper

And the binary that is in the tar file used to build the package:

afe0b1286c5e2ed01409be1d6f68c964 ~/Downloads/Zoiper5/zoiper

If I run the packaged binary then I get the checksum error, if I run the binary from the source tarball then I am able to activate my license.

Could it be down to the stripping of the symbols from the binary that is causing this?

==> Tidying install... -> Removing libtool files... -> Purging unwanted files... -> Removing static library files... -> Stripping unneeded symbols from binaries and libraries... -> Compressing man and info pages...

Any thoughts on this?

Asgaroth commented on 2018-04-25 09:50

This package now fails as the version has been updated to 5.2.14 whereas package expects 5.2.12.

If I edit PKGBUILD and modify pkgver to be 5.2.14 then the build proceeds but fails to install as the version in PKGBUILD and .SRCINFO differ (PKGBUILD has 5.2.14 and .SRCINFO has 5.2.12)

Please would someone update the package. Much appreciated.

Xavion commented on 2017-12-28 23:44

Yes, that sounds like a good idea. I've modified the PKGBUILD accordingly.

I was going by Zoiper's own dependency list. As you can see (at the bottom of the following webpage), those two aren't mentioned.

ricardofunke commented on 2017-12-28 22:46

I think there are missing dependencies

I tried to start zoiper and had:

zoiper: error while loading shared libraries: cannot open shared object file: No such file or directory

Installed gtk2 package and then:

zoiper: error while loading shared libraries: cannot open shared object file: No such file or directory

installed gconf package and finally I could start it

I think you should add both gtk2 and gconf as dependencies, right?

Xavion commented on 2017-11-25 20:59

I'm away from my Linux box for the next week or so. The update to Zoiper v5 will have to wait until I return.