Package Details: hydrus 616-1

Git Clone URL: https://aur.archlinux.org/hydrus.git (read-only, click to copy)
Package Base: hydrus
Description: Danbooru-like image tagging and searching system for the desktop
Upstream URL: http://hydrusnetwork.github.io/hydrus/
Licenses: WTFPL
Conflicts: hydrus-docs-dummy
Submitter: Score_Under
Maintainer: Score_Under (turtletowerz)
Last Packager: turtletowerz
Votes: 42
Popularity: 1.04
First Submitted: 2015-02-28 18:11 (UTC)
Last Updated: 2025-04-03 01:03 (UTC)

Pinned Comments

turtletowerz commented on 2025-02-05 23:14 (UTC)

The AUR package for JpegXL support is outdated and does not build. If you need JpegXL support, follow the instructions in the comment I posted to update the PKGBUILD.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 13 Next › Last »

Score_Under commented on 2022-08-04 09:55 (UTC)

@WorldTeacher, it would be my recommendation to remove all packages installed in ~/.local/lib/python3.10, whether by moving it away or by invoking pip for each one. Then the packages you still need can be reinstalled via the AUR or pacman.

WorldTeacher commented on 2022-08-04 07:57 (UTC)

@Score_Under, so just to make sure I understand it correctly: I should uninstall opencv-python using pip (as well as the packages located in ~/.local/lib/python3.10) and install them using pamac / pacman? Or did you mean something else?

Score_Under commented on 2022-08-03 20:49 (UTC) (edited on 2022-08-03 20:56 (UTC) by Score_Under)

@WorldTeacher I note that you have opencv installed locally via pip. Just a heads-up, installing anything locally via pip can take priority over system packages and mess with otherwise-working python library installations on your system. I strongly recommend against using local pip installs, and instead anyone wanting to do so should confine those installs to a virtual environment (python -m venv --help).

If you move your ~/.local/lib/python3.10 directory away (e.g. rename it and add ".old" to the end), that will get rid of all locally installed python packages which should either allow you to determine if that really is the problem, or allow you to revert back to a hopefully working state.

For the record, I have python-opencv installed alongside hydrus on my system and it is not a problem.

WorldTeacher commented on 2022-08-03 17:05 (UTC) (edited on 2022-08-03 17:05 (UTC) by WorldTeacher)

In version v493-1, the client will not launch when opencv-python is installed on the system. As soon as opencv-python is uninstalled, it works fine. This is the error message it produces in the terminal:

v493, 2022/08/03 18:57:13: hydrus client started QObject::moveToThread: Current thread (0x5636edae12b0) is not the object's thread (0x5636ed9a12e0). Cannot move to target thread (0x5636edae12b0)

qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "/home/alexander/.local/lib/python3.10/site-packages/cv2/qt/plugins" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: xcb, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx.

[1] 7986 IOT instruction (core dumped) hydrus-client

misagh commented on 2022-01-04 05:01 (UTC)

@Score_Under Thanks the issue has been solved by switching back

Score_Under commented on 2022-01-02 15:52 (UTC)

@misagh, I've given this a look and it does indeed seem to be true that pyqt5 alone hits on some bugs, so I've put a hard dependency for pyside2 in again.

As much as part of me wants to run on pyqt5 just to find the bugs... :)

misagh commented on 2022-01-02 12:21 (UTC) (edited on 2022-01-02 12:22 (UTC) by misagh)

Hello @Score_Under,

Please take a look at this suggestion by the hydrus developer with regards to using PySide2 as opposed to PyQt5: https://github.com/hydrusnetwork/hydrus/issues/1033#issuecomment-1003620540

andiandi commented on 2021-12-29 21:15 (UTC)

Thanks for the hint @Score_Under! After rebuilding and then reinstalling python-mpv, everything works as expected now!

Score_Under commented on 2021-12-29 10:23 (UTC)

Reinstalling is likely a good enough solution, you don't even need the -git version.

Try pacman -Qo /usr/lib/python3.9 to see which AUR packages are still built for python 3.9 on your system. Those should all be reinstalled (with a clean build, if you get that option) so that they use python 3.10, the current Python version on Arch.

clue1ess commented on 2021-12-29 05:01 (UTC)

@And1G I Had the issue to. A bandaid would be installing python-mpv-git instead

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 13 Next › Last »