note there is now an AppImage provided as well for XnViewMP
Search Criteria
Package Details: xnviewmp 1.8.0-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/xnviewmp.git (read-only, click to copy) |
---|---|
Package Base: | xnviewmp |
Description: | An efficient multimedia viewer, browser and converter. |
Upstream URL: | https://www.xnview.com/en/xnviewmp/ |
Keywords: | graphics |
Licenses: | custom |
Submitter: | oliwer |
Maintainer: | Corax |
Last Packager: | Corax |
Votes: | 307 |
Popularity: | 2.46 |
First Submitted: | 2008-07-25 19:01 (UTC) |
Last Updated: | 2024-09-03 14:45 (UTC) |
Dependencies (2)
- qt5-multimedia
- glib2 (glib2-gitAUR, glib2-selinuxAUR, glib2-patched-thumbnailerAUR) (optional) – support for moving files to trash
Required by (0)
Sources (2)
Latest Comments
« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 27 Next › Last »
Kewl commented on 2018-03-08 22:30 (UTC)
OldNuc commented on 2017-11-10 04:36 (UTC)
0.88-1 has fixed the font issue.
Corax commented on 2017-11-04 12:09 (UTC) (edited on 2017-11-04 12:10 (UTC) by Corax)
0.88 is upon us :D This should solve the font issues, apparently fuan_k has already confirmed that :-) Don't forget to remove /opt/xnviewmp/lib/libfontconfig.so.1 if you used the hack I mentioned below.
Corax commented on 2017-10-08 17:03 (UTC)
@fuan_k: great news, and well done reporting these bugs! Looks like 0.88 is going to be a great release :-)
fuan_k commented on 2017-10-02 03:25 (UTC) (edited on 2017-10-02 14:24 (UTC) by fuan_k)
@Corax: he's doing this in private. Wait and see.
edit: here is the bug tracker ticker: https://www.xnview.com/mantisbt/view.php?id=1315
I've also managed to get him to fix the broken config path I mentioned before (below). The problem was using the "Program (XnView)" setting during initial set up, instead of "User (System)". It was a bug anyway, now fixed too. https://www.xnview.com/mantisbt/view.php?id=1317
Corax commented on 2017-10-01 17:54 (UTC)
@fuan_k: awesome! Did he comment about that on the forum? Can't see anything in General Support.
fuan_k commented on 2017-09-29 23:01 (UTC)
Good news, the xnviewmp author has looked into it and has it fixed in an upcoming version! No more fontconfig errors (just tried it myself). :D
Corax commented on 2017-09-27 18:42 (UTC)
@fuan_k: not much I can do about the font glitch I'm afraid, there's probably something wrong about how XnView uses fontconfig :/ Regarding the fontconfig breakage, I'll give it some more time before I hack the PKGBUILD. An Archer has reported the issue on the forum, we'll see how it goes: https://newsgroup.xnview.com/viewtopic.php?f=82&t=36326
fuan_k commented on 2017-09-27 01:52 (UTC) (edited on 2017-09-27 02:17 (UTC) by fuan_k)
It's funny because the fontconfig error always mentions a totally different line for each xnviewmp instance.
@Corax: thanks again for maintaining this package. It might be wise to add the workaround to the PKGBUILD (and perhaps document it in comments).
For me I found the old package in /var/cache/pacman, and I did not have 1.10.0 as I skipped an update :P.
Would it be a good idea to ask the author of XnviewMP to include his own fontconfig in the package?
I'm still trying to fix this stupid font glitch from forever ago.
Edit: I got it to work after downgrading to libfontconfig.so.1.9.4 and using this shell script:
export LD_LIBRARY_PATH="/usr/lib:$dirname/Plugins"
export QT_PLUGIN_PATH="/usr/lib:$dirname/lib:/usr/lib/qt/plugins"
export QT_QPA_PLATFORM_PLUGIN_PATH="$dirname/lib/platforms/"
QT_QPA_PLATFORMTHEME=qt5ct
exec "$dirname/XnView" "$@"
Still looking for a way to preload these libs without downgrading my entire system and not segfault xnview.
Edit: I give up. For now, the font glitch is here to stay until I try again. ugh.
Pinned Comments
Corax commented on 2017-01-21 15:34 (UTC) (edited on 2017-02-12 19:23 (UTC) by Corax)
Corax commented on 2017-01-20 21:49 (UTC) (edited on 2023-10-30 20:39 (UTC) by Corax)
If makepkg fails because the checksum is incorrect, please flag the package out-of-date and I will update the PKGBUILD.
The PKGBUILD now references the latest versioned archive, as a result of which it should keep working if a new version is released. However, upstream sometimes updates released archives in place, in which case the checksum will fail and a manual intervention is required.