I’m on EOS Cinnamon, freshly updated. After the last reboot and login, I see a “Cinnamon is is in fallback mode”. Restarting Cinnamon leads to the same, only when I answer “No” to the restart, some desktop icons appear, and the Welcome app. No panel, no title bars on windows. I could get here by using some info button in the Welcom app only, which started Firefox, although its menus and tabs don’t work when clicking with the mouse.
I tried to get logs using the Welcome app. Since I can’t change windows, I’ll come back with the link, just a mo.
During the day, I did install & try a different theme via the Cinnamon theme setting, and removed it again. (Never mess with the default desktop & theming, aarrgh!). The system ran fine the whole day, but when I opened the lid again this evening, it was stuck, showing a time ~1 hour ago, and no login. Since Ctrl+F2 terminal didn’t let me log in, I had to hard poweroff. After that, problem on the next boot.
Cannot make a screenshot, but changing windows with mouse or Alt+Tab is impossible, and a small window fragment keeps jumping around on the screen.
was this themed installed to the system or for the user? I mean you could try to remove the cinnamon folders in .config and see if it lets you boot into it then.
cd ~/.config
mv cinnamon cinnamon.sav
mv cinnaom-session cinnamon-session.sav
reboot
No difference.
I installed that theme via the Cinnamon Theme app, by selecting from the available themes, downloading it, and activating it.
No good, so I changed back to standard theme, and deleted it again, also through the theme setting.
Currently can’t get there, since no panel, no Ctr+Alt+T terminal, and that doesn’t work from the Ctrl+F2 terminal of course.
I did an update this morning with Core stuff so I had to reboot. No problem.
There was some other stuff mid-day for the second update.
Just did an update now and it’s a bunch of core/glibc stuff.
Not that I knew of. I do have appimagelauncher but it is set to not automatically do anything. My ~/Applications folder is empty.
Nevertheless, I know that some AUR packages unpack from or use (?) AppImages, so here is my pacman -Qm. Note that all this worked before the update, for several weeks, without problems.
I am not sure how you configured your timeshift service. It doesn’t back up $HOME contents unless specifically enabled. If that’s the case, you can skip changes in your $HOME.
It appears that cinnamon crashed (core dumped, sig 6). Stick with the version that is working and wait for further update from pacman. If you really want, you could try to debug the core files. In systemd, they’are located in,
Problem is of course I’d like to continue updating and installing software on this machine. So it would be beneficial to find out what exactly caused the crash. I could then maybe uninstall the program causing it.
Otherwise, how would I know when it’s safe to update again?
Timeshift I’ve set to auto-snapshot once a day and before updates (using the Pacman hook), and never to save anything from the home folders. I use Back in Time for that.
coredumpctl shows:
$ coredumpctl list --since "3 days ago"
TIME PID UID GID SIG COREFILE EXE SIZE
Fri 2025-06-13 21:02:28 CEST 942 1000 1000 SIGTRAP present /tmp/.mount_espansA2ygLB/usr/bin/espanso 1M
Sat 2025-06-14 12:40:36 CEST 937 1000 1000 SIGTRAP present /tmp/.mount_espansU1o4ws/usr/bin/espanso 1M
Sat 2025-06-14 12:57:50 CEST 930 1000 1000 SIGTRAP present /tmp/.mount_espanspP1eEX/usr/bin/espanso 1M
Mon 2025-06-16 00:13:47 CEST 967 1000 1000 SIGTRAP present /tmp/.mount_espansCBzQfi/usr/bin/espanso 1M
So just some Espanso messages. It sometimes shows “updated keyboard configuration”, maybe that’s when it crashes. Usually happens at max. once a day so I didn’t care much, since it continued working.
$ ulimit -a
real-time non-blocking time (microseconds, -R) unlimited
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 63187
max locked memory (kbytes, -l) 8192
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 63187
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
EDIT: If you were looking for the crash dump, that might not be there anymore, since I had to restore to a Timeshift snapshot before the update and crash happened, to get this system working again. But I’ve saved the pacman.log (see above).
