[omano@omano-nvme ~]$ pamac-manager
(pamac-manager:23212): Gdk-CRITICAL **: 18:35:58.792: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed
Failed to query https://aur.archlinux.org/rpc/?v=5&type=suggest&arg=lib from AUR: Socket I/O timed out
Failed to query https://aur.archlinux.org/rpc/?v=5&type=suggest&arg=libr from AUR: Socket I/O timed out
Failed to query https://aur.archlinux.org/rpc/?v=5&type=suggest&arg=libre from AUR: Socket I/O timed out
Failed to query https://aur.archlinux.org/rpc/?v=5&type=suggest&arg=librew from AUR: Socket I/O timed out
Failed to query https://aur.archlinux.org/rpc/?v=5&type=suggest&arg=par from AUR: Socket I/O timed out
Failed to query https://aur.archlinux.org/rpc/?v=5&type=search&arg=paru from AUR: Socket I/O timed out
Failed to query https://aur.archlinux.org/rpc/?v=5&type=suggest&arg=paru from AUR: Socket I/O timed out
We get blocked because of the suggestion feature when we search. Pamac hangs because it fails to receive AUR response, because it floods the AUR.
I’m opening an issue on GitLab, hope this get looked at. New Pamac search suggestion floods AUR search (#1135) · Issues · Applications / pamac · GitLab
As I suggested here Responsible use of AUR
Maybe the default search should also be only in the repositories, instead of searching the AUR by default (clicking the AUR button would then trigger the search)?