The only reliable way I found to fix the font issue is to use qt5ct and add this to the environment variables (or just add the following to xnview.sh maybe?)
QT_QPA_PLATFORMTHEME=qt5ct
This will force the Qt application to use whatever you set up. You can also use the "--platformtheme qt5ct" command line option.
You'll notice this in terminal output when running xnviewmp: qt5ct: using qt5ct plugin
Unfortunately, there is still a weird problem: if you use a different desktop environment (i3wm for example) and if you load another picture (from a file manager), the theme will get swapped to the Fusion Theme. More details there: https://wiki.archlinux.org/index.php/qt#Qt5
Fonts will stay fine though, but some widget buttons will get shuffled around and such. Very strange. Anyway, that should go to the XnViewMP developer. ;)
Search Criteria
Package Details: xnviewmp 1.7.2-1
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: | 302 |
| Popularity: | 2.44 |
| First Submitted: | 2008-07-25 19:01 (UTC) |
| Last Updated: | 2024-06-07 17:35 (UTC) |
Dependencies (2)
- qt5-multimedia (qt5-multimedia-gitAUR)
- glib2 (glib2-gitAUR, glib2-patched-thumbnailerAUR, glib2-selinuxAUR) (optional) – support for moving files to trash
Required by (0)
Sources (2)
fuan_k commented on 2017-01-20 23:05 (UTC) (edited on 2017-01-21 01:58 (UTC) by fuan_k)
fuan_k commented on 2017-01-20 22:46 (UTC) (edited on 2017-01-20 22:55 (UTC) by fuan_k)
Had an error with this line, as it couldn't find the file (I never had it): rm "${pkgdir}/opt/${pkgname}/lib/"libicu*.54*
You might want to change for the following (I could be wrong, but I tested it and it worked I think):
if [[ -e "${pkgdir}/opt/${pkgname}/lib/"libicu*.54* ]]; then
rm "${pkgdir}/opt/${pkgname}/lib/"libicu*.54*
fi
Anyway, I still get issues with this package:
-remove qt.conf as usual (otherwise I get: This application failed to start because it could not find or load the Qt platform plugin "xcb"
in "".)
-the font is indeed still the wrong one. Still investigating... Have you guys tried using strace on this program? It's crazy the amount of libraries it's looking for in places that don't even exist... ugh.
blitz commented on 2017-01-20 22:28 (UTC)
xnviewmp 0.84-1 build works
with system Qt5 libs
without bundled /opt/xnviewmp/lib/"lib*
Total Installed Size: 36.54 MiB
The only missing dependency is extra/qt5-location
>Upstream released a new version today (?), which fixes the libicu issue
XnViewMP
Version 0.84 x64 (Jan 17 2017)
Libformat version 6.95
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.
Corax commented on 2017-01-20 21:43 (UTC)
@KVF Upstream released a new version today (?), which fixes the libicu issue.
@DungeonMaster Thanks for the feedback, it's very hard to know how things work out on other people's setup so I need this kind of feedback. Given that the libicu issue is now fixed, I reverted to using the bundled libs in 0.84-2, it should work just like before.
@fuan_k @whoseos Since XnView seems to be somewhat working with the system Qt libs, at least for some people, I could create a another xnviewmp package where the bundled libs are removed. Hopefully that would make everyone happy. What do you think?
KVF commented on 2017-01-20 04:35 (UTC)
The PKGBUILD incorrect - md5sums_x86_64=('bbb8bfac5a212103830c9b1dca51c2ae')
should be - a1202367f23f32e14a6a0d860564e1da
DungeonMaster commented on 2017-01-20 03:46 (UTC)
@Corax
removing the bundled libraries for this update made the fonts a strange type and a size too small to read very well at all. I use this program all the time, so I downloaded the DEB from xnview, ran debtap and installed it. It installed as 0.84-1 and everything appears to be working fine -so far-
I tell you this with the hope that maybe if you look at the DEB or you debtap it and take a look at the tar.xz file, maybe it can help you somehow, I don't know.
I look forward to a fixed 0.84-2 whenever it happens.
Corax commented on 2017-01-17 22:18 (UTC) (edited on 2017-01-18 19:33 (UTC) by Corax)
So basically upstream 0.84 is broken but I worked around it, more details in the commit I just pushed. Some Qt 5 libraries depend on icu 56, which should be shipped with the rest but is not.
It seems that it works fine with the system Qt 5 libraries for me, so I just removed the bundled libs. I noticed that XnView doesn't use my system Qt theme (QT_QPA_PLATFORMTHEME) because of that, but it can be worked around (XnView provides alternate themes). Please let me know if other things are not working and I'll try to fix them, but I would very much prefer to use the system libs if it's it at all possible.
gabripo commented on 2017-01-17 11:13 (UTC) (edited on 2017-01-17 12:27 (UTC) by gabripo)
Problem on installing the 0.83-1 version!
To allow installing please correct the md5sum in the PKGBUILD with bbb8bfac5a212103830c9b1dca51c2ae (the newest package from the official site, x86_64 version).
Sources linked is wrong at now!
EDIT: The actal icu package version 58.2-1 is not compatible. Please downgrade to the 56.1-2 version to make XnViewMp working - EXCRUCIATING IDEA! IT WILL CORRUPT EVERY OTHER PROGRAM!
Corax commented on 2016-12-16 22:54 (UTC)
@fuan_k Well that's quite troubling indeed... I get this error too, I don't have any font problem but if XnView does indeed what you describe then I may just be lucky. The issue seems to come from the XnView itself, as I see the error message even when forcing it to use the system libfontconfig. Using the normal launch script, symlinking libfontconfig.so.1 into lib/ doesn't change anything for me.
Actually, if I launch XnView directly, like this:
$ LD_LIBRARY_PATH=/lib:./Plugins/ QT_PLUGIN_PATH=./lib ./XnView
keeping qt.conf as is (otherwise XnView crashes as I mentioned in a previous comment), then the font is wrong! So for me it's the reverse situation...
There's definitely something wrong with XnView, but I'm not sure what to do about it right now, since there's no real problem for me out the box... Anyone else affected by this?
fuan_k and whoseos, feel free to start an email thread or something like that on this topic, to avoid flooding the comments too much.
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.