Arch Linux User Repository

@guglovich v2.5 (this package) was released in early January. That commit will be part of v2.6 which will come within the next few days.

@luspi Don't they have built-in support now? That's why I wrote. I asked them to add support for the format and then there was a commit.

https://gitlab.com/luspi/photoqt/-/commit/b704cfbe2375ad3644decb30bbb83aef80d3bf0f

@guglovich v2.5 only supports HEIC through ImageMagick (you need to swap from GraphicsMagick to ImageMagick in the PKGBUILD to take advantage of that). Starting with v2.6 (likely to be released later this coming week) support for HEIC through kimageformats will be added.

Please update the application. HEIC support is now available.

@crismblog

PhotoQt fails to build because your build of the dependency python-pychromecast failed. I suggest commenting on the python-pychromecast AUR page) to see if someone has an idea (it builds fine on my local machine thogh). If you can't get it to work, you can edit the PKGBUILD of PhotoQt to remove that dependency by removing its mention in the depends() array (line 11) and adding -DCHROMECAST=OFF to the cmake call (line 26).

@DianaNites I had the same issue. Got past it by deleting ~/.config/PhotoQt and ~/.cache/PhotoQt

@DianaNites

Did you try it with imagemagick? If you could file a bug report upstream, that'd also be great: https://gitlab.com/luspi/photoqt/-/issues

@luspi

Yes, my system is fully up to date. Probably a photoqt bug I guess.

For now i've just been using the previous version

@DianaNites Is your system up to date, in particular GraphicsMagick? There are some reports floating around the internet for various packages using various version of GraphicsMagick encountering this issue. If Your system is up to date, you can try switching over to ImageMagick:

In line 26 of the PKGBUILD, change -DIMAGEMAGICK=OFF -DGRAPHICSMAGICK=ON to -DIMAGEMAGICK=ON -DGRAPHICSMAGICK=OFF and in line 11 change graphicsmagick to imagemagick.

..I can't view images since updating. Every time I try it just opens a window saying photoqt has updated and to close this window to continue.

"photoqt: magick/semaphore.c:601: LockSemaphoreInfo: Assertion `semaphore_info != (SemaphoreInfo *) NULL' failed."

@Agafron, Thanks, I forgot to add python-pychromecast as dependency. Should be fixed now.

CMake Error at CMakeLists.txt:325 (message): ** Unable to locate Python3 module pychromecast. Please first install it or disable Chromecast support.

-- Configuring incomplete, errors occurred! See also "/tmp/trizen-ypp/photoqt/src/photoqt-2.5/CMakeFiles/CMakeOutput.log". ==> ОШИБКА: Произошел сбой в prepare().

@mutley, that's the same version I have and it builds just fine for me. That's just strange.

Anyways, I updated the PKGBUILD with some changes, one of them being that it now builds by default with GraphicsMagick.

Thanks @lebaux that switching from imageMagick to GraphicsMagick also worked for me. Could this be a imagemagick versioning problem the version i have (that does not work with photoqt) is 7.0.10.61-1.

Hm, it shouldn't make much difference wheter it's being built with GraphicsMagick and ImageMagick, but somehow it doesn't want to cooperate on your system. Unfortunately I can't seem to reproduce that, the current PKGBUILD works just fine on my machine.

Did you try removing the old build directory (for yay that should be ~/.cache/yay/photoqt/)?

Confirmed, switching over to GraphicsMagick works. Maybe this should be default build?

In the meantime, if you are using yay and want to edit PKGBUILD quickly, use:

yay --editmenu -S photoqt
a
n
a

And follow the instructions on line 13 and 25.

works with changing from building with ImageMagick to GraphicsMagick

Hm, it's compiling just fine here.

Some things that come to mind:

• Make sure to clean the build directory from any possible previous build. There has been a change of defaults from GraphicsMagick to ImageMagick.

• Make sure your system is up to date.

• If it still doesn't build, try changing from building with ImageMagick to GraphicsMagick (lines 13 and 25 in the PKGBUILD tell you how).

Let me know if the error persists.

+1 same issue

BUILD fails

[ 82%] Building CXX object CMakeFiles/photoqt.dir/photoqt_autogen/T24IUX3VL4/qrc_img.cpp.o
[ 84%] Building CXX object CMakeFiles/photoqt.dir/photoqt_autogen/ZWKA2O7I7G/qrc_misc.cpp.o
[ 86%] Linking CXX executable photoqt
/usr/bin/ld: CMakeFiles/photoqt.dir/cplusplus/scripts/handlingmanipulation.cpp.o: in function `PQLoadImageMagick::load(QString, QSize, QSize*, bool)':
handlingmanipulation.cpp:(.text._ZN17PQLoadImageMagick4loadE7QString5QSizePS1_b[_ZN17PQLoadImageMagick4loadE7QString5QSizePS1_b]+0x73c): undefined reference to `Magick::Image::rows() const'
/usr/bin/ld: handlingmanipulation.cpp:(.text._ZN17PQLoadImageMagick4loadE7QString5QSizePS1_b[_ZN17PQLoadImageMagick4loadE7QString5QSizePS1_b]+0x74a): undefined reference to `Magick::Image::columns() const'
/usr/bin/ld: handlingmanipulation.cpp:(.text._ZN17PQLoadImageMagick4loadE7QString5QSizePS1_b[_ZN17PQLoadImageMagick4loadE7QString5QSizePS1_b]+0x7f8): undefined reference to `Magick::Geometry::Geometry(unsigned long, unsigned long, long, long)'
/usr/bin/ld: handlingmanipulation.cpp:(.text._ZN17PQLoadImageMagick4loadE7QString5QSizePS1_b[_ZN17PQLoadImageMagick4loadE7QString5QSizePS1_b]+0x105f): undefined reference to `Magick::Geometry::Geometry(unsigned long, unsigned long, long, long)'
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/photoqt.dir/build.make:793: photoqt] Error 1
make[1]: *** [CMakeFiles/Makefile2:126: CMakeFiles/photoqt.dir/all] Error 2
make: *** [Makefile:149: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
error making: photoqt

FYI, I don't use photoqt for PDFs anyway so I've disabled poppler with this cmake option: -DPOPPLER=OFF

poppler, again. :(

Poppler updated again, so this requires a bump so it'll rebuild again.

@pallegro Thanks for the updated PKGBUILD!

@Tomek80Bytom I just updated the PKGBUILD, it should build again now. PhotoQt links against various libraries and if one of them updates then the library files sometimes change names (e.g., the new version number gets added). Unfortunately there is nothing I can do, PhotoQt (like other apps) needs to be rebuilt (actually, re-linked would be enough) to find these libraries again...

https://gitlab.com/luspi/photoqt/commit/c6fd41478e818f3a651d40f96cab3d790e1c09a4.diff is the fix for building with exiv-0.27 PKGBUILD: https://pastebin.com/9T80vR9R

@Tomek80Bytom try qimgv — pretty similar nice alternative

The application is very good itself, but unfortunately I have regularly problems, that after updates of some system packages it stop working and I have to reinstall it. Yesterday has occurred the same... application doesn't work on my machine now. More over, currently it is impossible to reinstall it because there are some issues with build.

@luspi My guess problem was in KDE session management, it's always saves unwanted states of some important programs, so it brings a lot of bugs, and I always forget about it =)

So yeah, now all works just fine! Thanks for the help mate ;)

@ruestique A simple rebuild of photoqt will suffice (make sure to start with a clean setup - do you use an aur helper?). Essentially all that needs to happen is for the executable to be linked against the new poppler libs.

@luspi I also checked poppler and poppler-qt5, but cannot --overwrite it, since I don't know the <path>

@ruestique reinstall is not enough, poppler update necessitates recompile. I bumped pkgrel to trigger recompiles.

having an error photoqt: error while loading shared libraries: libpoppler.so.86: cannot open shared object file: No such file or directory

google and reinstall can't help =(

@3enke They are created to allow the option of 'fake transparency'. The screenshots need to be done before the app window is shown, they are thus taken and stored in the tmp directory at startup of PhotoQt.

Any idea why PhotoQT is making desktop screenshots in /tmp folder? I am using version 1.5.1.

Yes, that solved the issue. Thank you!

@pbnoxious It seems that Qt 5.11 finally removed the qt5_use_modules() cmake function (it was deprecated for a while already). I added a patch here that replaces that line by a call to target_link_libraries(), so it should work again now!

When I try to install it I get an error from CMake with regard to qt5:

CMake Error at CMakeLists.txt:141 (qt5_use_modules):
    Unknown CMake command "qt5_use_modules".

The log does not show anything suspicous to me, does somebody know what the reason for the failure might be?

Thanks, added it to the makedepends array!

@ruestique thanks, I just had that problem. Sounds like it should probably be added as a makedeps dependency.

if someone gets:

Could not find a package configuration file provided by "ECM" with any of the following names: blah-blah-blah...

just make sure you have installed:

cmake extra-cmake-modules

Thanks, rtfreedman, applied those changes!

The proper arch is: arch=('x86_64') An install file is not needed - pacman takes care of desktop/icon updates