You are not logged in.
I just upgraded to cinnamon-6.6.0-2. After doing to, I see severe rendering glitches. For example, in `XFCE Terminal` windows (upon focussing), in the windows' upper left, there is a rectangle displaying contents from bottom of same screen (in my case showing cinnamon's menu-panel), hence hiding the window's menu. It is possible to open said menu by clicking on it w/o first switching focus, though.
I tried downgrading to previous cinnamon (6.4-*). However (probably because of other package-versions I would have had to also downgrade), cinnamon came up completely broken (Desktop would render, but it would not react upon any inputs from keyboard or mouse).
Other applications (such as chrome) seem to be displayed w/o glitches. However, XFCE-Terminal is what I use almost exclusively so this glitch is very inconvenient :-(
Last edited by dr1fter (2025-12-20 09:45:29)
Offline
I see the same issue here. For me downgrading cinnamon-*, muffin and nemo fixed the issue:
cd /var/cache/pacman/pkg/
pacman -U cinnamon-6.4.13-1-x86_64.pkg.tar.zst cinnamon-control-center-6.4.2-1-x86_64.pkg.tar.zst cinnamon-desktop-6.4.2-1-x86_64.pkg.tar.zst cinnamon-menus-6.4.0-1-x86_64.pkg.tar.zst cinnamon-screensaver-6.4.1-1-x86_64.pkg.tar.zst cinnamon-session-6.4.2-1-x86_64.pkg.tar.zst cinnamon-settings-daemon-6.4.3-1-x86_64.pkg.tar.zst cinnamon-translations-6.4.2-1-any.pkg.tar.zst nemo-6.4.5-1-x86_64.pkg.tar.zst muffin-6.4.1-1-x86_64.pkg.tar.zstPS: It seems there is already an open issue on github: https://github.com/linuxmint/cinnamon/issues/13267
Last edited by olebowle (2025-12-15 18:25:55)
Offline
thanks - will try downgrading then + linked issue looks exactly like what I / we see
Offline
downgrading did not work for me (as in: cinnamon crashed after I tried and rebooted) :-(
As next-best alternative, I now switched to xfce4. let's see how long upstream will take to fix :-)
Last edited by dr1fter (2025-12-15 19:37:43)
Offline
Is this still happen if you remove the "caribou" package? Caribou is no longer used by Cinnamon, it's a leftover dependency that should be removed now, so it should be safe to run the following command:
# pacman -Rdd caribouOffline
I added a conflict with caribou in cinnamon 6.6.0-3, so users will have to remove it on system upgrade. Also, I dropped the caribou package into AUR, because it's deprecated and not used anymore.
Offline
I noticed the package-conflict (and dropped caribou). Will try later today whether this fixes issues w/ cinnamon, and post an update.
Offline
I've tried cinnamon with caribou removed - it breaks cinnamon-screensaver (including screen lock function), so I had to downgrade and re-introduce caribou on my setup.
I'm afraid, removing caribou may solve graphical artifacts, but introduces another (bigger?) problem for everyone.
See https://gitlab.archlinux.org/archlinux/ … /issues/11.
Offline
Offline
I've done the update and I'm still getting a graphical glitch. I've got a VM with the same version/setup and it works fine.
Is there something I need to force refresh or update to fix the start menu?
Last edited by Aconite33 (2025-12-17 14:20:46)
Offline
@City-busz, the solution of completely removing Caribou solved the rectangular glitches, thanks.
However, it seems that Caribou is required (tough not of its components). Caribou absence now throws an error in some Applets, e.g.,: Lock keys indicator with notifications
This is the error I get in Cinnamon looking glass:
error t=2025-12-17T10:36:59Z
[betterlock]: Requiring Caribou, version none: Typelib file for namespace 'Caribou' (any version) not found
[betterlock]: Error importing applet.js from betterlockThe problematic component of Caribou (Antler) is now blocked in Cinnamon, as per this commit:
https://github.com/linuxmint/cinnamon/c … 2380849b6e
It should be fine to remove the conflict between Cinnamon and Caribou right?
EDIT: Caribu dependency for this Cinnamon Applet was removed.
https://github.com/linuxmint/cinnamon-s … 6a43b62a86
Last edited by rcassani (2025-12-20 03:02:08)
Offline
I can confirm the original issue I reported is gone now (tested in my own machine, only) + I also see some minor glitch in "start menu" (for me, this state is again "good enough"). So I suppose it will be adequate to label this thread with "resolved", right? Thanks for your swift help!
Offline