Package Details: zandronum 3.0.1-3

Git Clone URL: (read-only, click to copy)
Package Base: zandronum
Description: OpenGL ZDoom port with Client/Server multiplayer
Upstream URL:
Licenses: custom
Conflicts: zandronum2
Submitter: sanerb
Maintainer: sanerb
Last Packager: sanerb
Votes: 22
Popularity: 0.046390
First Submitted: 2017-12-14 15:03
Last Updated: 2020-04-03 18:03

Pinned Comments

sanerb commented on 2018-01-21 07:55

Bug reports can be filed at
News updates for packages can be followed at

(If you want an RSS-feed only pertaining to my AUR packages, you can subscribe to in your favourite RSS reader.)

Note that you should still use the AUR web interface for flagging packages as out-of-date if a new version is released; the aforementioned bug tracker is to aid in issues with building/packaging/the PKGBUILD formats/etc. specifically.

GPG signature "errors" are explained here:

Please read; it's not a bug.


Latest Comments

1 2 Next › Last »

sanerb commented on 2020-07-17 02:52


WHOOPS, that's right; they switched to mercurial. Embarrassingly, I also maintain zandronum-hg. (It's still stuck in my head as zandronum-git.)

Will work on changing name to zandronum-bin and having this build from source. Can you please confirm against zandronum-hg to see if you're getting the same behaviour? (EDIT: and comment there if you are so others will know and I can potentially investigate)

lyghters commented on 2020-07-17 00:17


Sorry, it probably was 'zandronum-hg' or something (I'm afraid I don't remember anymore). I deleted my previous comment to avoid further confusion.

Renaming to 'zandronum-bin' is a good idea, though.

sanerb commented on 2020-07-16 16:00


Are you sure you have the right package and aren't trying to build zandronum-git? This PKGBUILD doesn't do any compiling. (I should really rename it to zandronum-bin at some point and do a separate package that builds, but...)

Please confirm.

5anya commented on 2020-04-25 10:51

no, don't implement those in the launcher: it works fine after you switch the sound system in the settings from OSS/ALSA to SDL. I think the issue's gonna be fixed in the fmodex library (at least I think it's the library's issue). did anyone file a bug report to fmodex's developers on this? and yeah, it still happens with the latest version.

sanerb commented on 2020-04-25 01:11

do you guys want me to implement those in the launcher? i hesitate to do so since it would always start with -nosound then.

i DID update the package to use the appropriate FMOD version. is it still happening in 3.0.1-3 version of this package?

5anya commented on 2020-04-24 19:55

These errors are also fixed with @laserlennart's workaround: double free or corruption (!prev) OR malloc_consolidate(): invalid chunk size

sanerb commented on 2020-03-29 01:44


thanks for finding that workaround! did you file a bug report upstream yet or find a relevant one? if not, i'll open one.

laserlennart commented on 2020-03-28 18:45

FMOD support seems broken with newer kernels. For those who got this error on startup:

corrupted size vs. prev_size in fastbins

use this workaround i got from discord:

  • start zandronum with -nosound option
  • set output system to SDL in options
  • quit game
  • restart normally

works for me.

csnxs commented on 2019-10-24 00:44

Please update to v3.0.1 -

Pol_M commented on 2019-04-18 15:14

Could you remove the "," in the conflicts section? It causes an error.