Newly installed manjaro-XFCE and fully updated. glycin (as glycin-image-rs or as glycin-svg) brings the CPU to 100% and often crashes my system. I have disabled preview of files in Thunar and Gnome (for Gnome using gsettings set org.gnome.desktop.thumbnailers disable-all true) but still glycin runs after reboot and login.
How to fix this? Get rid of glycin (I do not need thumbnails) (unfortunately gdk-pixbuf2 depends on this). My last resort is to remove the x bit from the executables but this is not proper solution. I can not work otherwise. The system is unstable because of this. I also have removed $USER/.cache/thumbnails
Assuming your system is using a fully up-to-date mirror and your system is fully up-to-date.
Looking at the packages
First the glycin package, then the gdk-pixbuf2 package seems to indicate your issue is symptom rather than the cause
$ pamac info glycin
Name : glycin
Version : 2.1.5-2
Description : Sandboxed and extendable image decoding
URL : https://gnome.pages.gitlab.gnome.org/glycin/
Licenses : MPL-2.0 OR LGPL-2.1-or-later
Repository : extra
Installed Size : 18,3 MB
Groups : --
Depends On : bubblewrap cairo fontconfig glib2 glibc lcms2 libgcc libjxl librsvg libseccomp
Optional Dependencies : libheif: Load .avif, .heic and .heif [Installed]
Required By : gdk-pixbuf2
Optional For : --
Provides : libglycin-2.so=0-64
Replaces : --
Conflicts With : --
Packager : Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Build Date : man 06 jul 2026 18:59:30 CEST
Install Date : tor 23 jul 2026 06:13:28 CEST
Install Reason : Installed as a dependency for another package
Validated By : Signature
Backup files : --
$ pamac info gdk-pixbuf2
Name : gdk-pixbuf2
Version : 2.44.7-1
Description : An image loading library
URL : https://gitlab.gnome.org/GNOME/gdk-pixbuf
Licenses : LGPL-2.0-or-later
Repository : extra
Installed Size : 3,1 MB
Groups : --
Depends On : glib2 glibc glycin shared-mime-info
Optional Dependencies : libheif: Load .avif, .heic and .heif [Installed]
libopenraw: Load .arw, .cr2, .crw, .dng, .erf, .mrw, .nef, .orf, .pef and .raf
libwmf: Load .apm and .wmf [Installed]
Required By : firefox flatpak gcr gegl ghostscript gimp gst-plugins-good gtk-update-icon-cache
gtk-vnc gtk3 gtk4 jan-bin libdbusmenu-gtk3 libgnomekbd libhandy libnotify librewolf
librsvg proton-vpn-gtk-app qemu-ui-gtk rofi spice-gtk system-config-printer
vlc-plugin-notify webkit2gtk-4.1 wxwidgets-gtk3 xapp xdg-desktop-portal
xdg-desktop-portal-gtk
Optional For : libwmf qt6-base
Provides : libgdk_pixbuf-2.0.so=0-64
Replaces : --
Conflicts With : --
Packager : Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Build Date : lør 27 jun 2026 19:35:01 CEST
Install Date : tor 23 jul 2026 06:13:28 CEST
Install Reason : Installed as a dependency for another package
Validated By : Signature
Backup files : --
The glycin is a hard dependency of gdk-pixbuf2 which in turn is required by the current GTK toolkit versions, which makes it impossible to avoid, and more importantly it points towards a local system issue.
If you have any foreign packages sync’ed to your system (AUR buildscripts), I suggest you start by removing them.
As it is not a widespread or commonly known issue - at least at this forum - finding what is causing it will be guesswork at best.
Perhaps providing system information - the output from inxi -Fxc0 - could provide better foundation for guessing…
Searching Gnome Gitlab for glycin gives these results:
First, I can not remove AUR because I need zoom. But before I installed yay, the system already had this symptom with glycin.
I run inxi -Fxc0 and the output is pasted below. I do not know if this helps in anyway.
What if I switch from XFCE to mate-desktop? Will that help?
Oh, did not think that this was the issue. You are correct. I always add swap in my installations. I do not know how come I forgot it this time. I will do it and see if this solves my issue.
Lack of swap may be contributing to the issue; a very likely contributor, in fact, however, it may not be the issue that’s causing you grief.
As has already been said:
I notice your / (root) is comparatively small… My suggestion is to create a swappartition rather than a swapfile.
A swap file lives in your / file system, which means that whatever size you configure, the available space on / will drop by that much as well (in approximate terms).
Creating a separate swap file on another partition seems the best way forward; that is, unless you can confidently micro-manage your own disc space usage.
With only 4 GiB of physical RAM, I might suggest a swap partition of 12 GiB to 16 GiB (but, definitely not less than 8 GiB).
Answering that question would seem rather difficult when the actual issue isn’t yet known, don’t you think?
If you were thinking in terms of memory usage, 4 GiB of RAM and no swap wouldn’t be helping, no matter which of the official DE’s are used.
See (below) to learn how to install Zoom on Manjaro:
Yes, this is from the official Zoom site; easy instructions.
In any case, the suggestion by @linux-aarhus was merely a temporary measure to allow better diagnosis of the problem. As it stands there is not a lot to work with; we can only guess where the problem might stem from.
Thanks for all the answers. It turns out that the issue was indeed the lack of swap. I added swap on a file to test and the system became absolutely stable. Now I will change the partitions to add a swap partition because as you say it is a better option.
This machine had Ubuntu before. This may explain how come I did not observe the lack of swap partition. Maybe Ubuntu’s default installation uses a file for swap.
I’ve taken the liberty of marking the solution post for you, as you seem to have forgotten.
Regards.
Assuming Manjaro was installed via Calamares, you may simply have missed/ignored swap setup. By default, swap is not configured – one needs to deliberately choose the preferred option or manually configure it when/if choosing the manual partitioning method of installation.
Yes, but I did not reformat the whole disk. I only formatted /
(/home is a different partition)
So if Ubuntu had a swap partition it ought to be there.
You could open up Gparted to visually check it. Otherwise, as you say, it might easily have been a swapfile, whether default or not.
I recall (however many years ago it was) when I installed Debian, I prepared partitioning and swap manually (a separate volume for /home is always good) but Ubuntu, I don’t know what the norm is (I’ve managed to avoid the distribution for many years).
to learn how to install Zoom on Manjaro: