Package Details: xnviewmp 0.85-1

Git Clone URL: (read-only)
Package Base: xnviewmp
Description: An efficient multimedia viewer, browser and converter.
Upstream URL:
Keywords: graphics
Licenses: custom
Submitter: oliwer
Maintainer: Corax
Last Packager: Corax
Votes: 239
Popularity: 3.824569
First Submitted: 2008-07-25 19:01
Last Updated: 2017-04-04 18:42

Pinned Comments

Corax commented on 2017-01-21 15:34

I have created a new package: xnviewmp-system-libs. This is exactly the same build, except that the bundled Qt/icu libs are removed. Please try it if you want to use XnView without the bundled libs, and discuss any issue related to this configuration here: Do keep in mind that this is an experimental package though, and things may break when I try to fix other things...

Corax commented on 2017-01-20 21:49

If makepkg fails because the checksum is incorrect, please flag the package out-of-date and I will update the PKGBUILD.

Upstream does not version the released archives and does not announce new releases either, so the checksum is bound to become wrong every time there is a new release, and there's nothing I can do about that.

Latest Comments

Corax commented on 2017-04-04 18:44

@fritz2 Thanks for the notification, I have bumped the PKGBUILD. No need to comment though, flagging out-of-date is enough to send me a notification.

fritz2 commented on 2017-04-04 15:51

A new version is out:
Results in a 404 error:
curl: (22) The requested URL returned error: 404 Not Found
==> ERROR: Failure while downloading

Corax commented on 2017-02-12 19:22

@fuan_k First, I wish more people didn't "know much about computers" like you do, the world would be a better place :D To be honest the packaging of XnView MP is awful and I don't feel like the maintainer really understands what he does.

Anyway, I found out that I still had a font issue using system libs. I think I found a way to fix it, which is actually quite logical. Please try the latest pkgrel of and let me know if it works for you (look at the commit message for more info on what I did). Note that this package relies on the gtk2 platform themes, but I believe it should work with qt5ct too (just tweak

fuan_k commented on 2017-02-09 18:55

Now segfaulting since the last update, when using system libs (ie. the previous workarounds to fix the fonts don't seem to work anymore because I can only use bundled libs). What on Earth are they doing upstream? xD

Changing the following line in causes the segfault:
``export QT_PLUGIN_PATH="$dirname/lib"`` to ``export QT_PLUGIN_PATH="/usr/lib"``

Must be because updated Qt libs are now 5.8 and xnview is still shipping 5.6 libs?

Edit: Found a new workaround which works!! Edit as follows:

export LD_LIBRARY_PATH="/usr/lib:$dirname/Plugins"
export QT_PLUGIN_PATH="/usr/lib"
export QT_QPA_PLATFORM_PLUGIN_PATH="$dirname/lib/platforms"

and change qt.conf like this:
Plugins = Plugins
lib = lib

Then symlink qt5ct into the Plugins directory:
sudo ln -s /usr/lib/qt/plugins/platformthemes/ /opt/xnviewmp/Plugins/

And to avoid the "missing style proxy" error (not critical, only optional):
sudo mkdir /opt/xnviewmp/Plugins/styles
sudo ln -s /usr/lib/qt/plugins/styles/ /opt/xnviewmp/Plugins/styles/

Then qt5ct plugin loads fine again -- although the icons get reverted to default gnome icons for some reason -- but the font is tweaked accordingly to qt5ct again. Can't find a way to have qt5gtk2 working though.
Sorry I don't know much about computers but... What a MESS!

Corax commented on 2017-02-01 21:18

@goldpaw Yes with your suggestion it's now less problematic (I've updated the pinned comment accordingly), we just have to notice that upstream has made a new release. When I find time I'll set up something to check that periodically, e.g. every day.

And you're very much welcome, I only maintain this package since a few months ago but I'm glad it proves useful to so many people :)

goldpaw commented on 2017-02-01 14:37

@Corax happy to help! :D

And I totally agree that the way the xnview team does their versioning is a problem. We're bound to get checksum errors and bugs from time to time since they don't really label or announce anything. But it's easy enough for us to check the md5 of the source and manually modify the PKGBUILD when needed. We'll figure it out!

Thanks for your continued work, wouldn't know what to do without this package! :)

Corax commented on 2017-01-24 22:10

@goldpaw I implemented your suggestion in the latest commit (I didn't bump the pkgrel as there is no point in making everyone rebuild exactly the same package). Thanks again!

Corax commented on 2017-01-23 21:27

@goldpaw I actually thought about doing that (very briefly though). I was concerned that it could be deceiving as the source archive would be renamed to the wrong version if the PKGBUILD it out-of-date, but that only happens if you've never run makepkg before, which probably means that you don't keep the PKGBUILD repo after building, in which case it doesn't matter how the sources are named. Also doing so would allow me (and others) to keep the various versions around. So yes definitely a good idea, but... Yeah I remember now, there's actually a problem with that. As we've seen last week, upstream doesn't necessarily bump the version number when publishing a new release. I think I'll work around that by appending a rel (release) number. Anyway thanks for mentioning this, I hadn't considered it seriously enough :-)

DungeonMaster commented on 2017-01-22 22:03


Beautiful. Works great.

Just a hint for those who might be experiencing problems with QT_QPA_PLATFORMTHEME=qt5ct I downloaded a package in the AUR called qt5gtk2 and I use QT_QPA_PLATFORMTHEME=qt5gtk

qt5gtk is explained well in this article:

goldpaw commented on 2017-01-22 15:21

@Corax the problem with the wrong md5sum is that the download is stored with the same name each time. This leads to PKGBUILD assuming that the file is already downloaded, and thus it attempts to use the existing one instead. Which leads to a md5sum mismatch, of course.

The solution is to modify the PKGBUILD slightly, so that it includes the pkgver$ variable in the downloaded filename. All that needs changing are the two sources. Not that it's important to use " instead of ' here, otherwise it won't change the $pkgver variable into the actual file version.

I changed the thwo source lines to this, and was able to build it without manually having to delete the old download first:


Yay! :D

All comments