I got the following error message while I was using Chromium:
Do you want to restart Cinnamon?
Cinnamon just crashed. You are currently running in Fallback Mode.
I do not know how to properly fix this, if it should occur again.
I could not start the CLI via ALT+F2. I changed into other TTYs and tried several commands via internet search with no success. In the end, I managed to restart with CRTL+ALT+F2, login and then CRTL+ALT+DEL. Cinnamon works now but I assume, given that I didn't fix this properly, it could happen again. I would appreciate instructions how to address this properly instead of trial and error next time. Thank you.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason:Topic automatically closed 6 months after creation. New replies are no longer allowed.
Please generate an overview of your system like this:
- Launch a terminal window (this is how to launch a terminal window);
- make the terminal window full screen, to avoid chopped lines;
- copy/paste this command into the terminal:
You can disable hardware acceleration in Chromium (it's in the advanced settings). And you'd do wise to disable all visual effects in Cinnamon as well: Menu button - Preferences - Effects
Turn off everything there.
But with a modest video chipset like that, I'd also consider switching to the lightweight Xfce edition of Mint.
By the way: can you increase the amount of shared RAM for the video chipset, in the BIOS settings?
A cinnamon crash like that can be caused by a lot of things. You may have stumbled across some bug in Cinnamon's code or maybe a 3rd partly xlet you are using. If it happens again, before restarting, look in ~/.xsession-errors. Most of the time it will log what led to the crash so at least you know where the problem lies.
When I give opinions, they are my own. Not necessarily those of any other Linux Mint developer or the Linux Mint project as a whole.
I've just had the same "Fallback" problem a couple of times with Rafaela (which I was excited about because it's supposed to be more resource efficient.) Similar specs on a Dell laptop but 32-bit, and running Chromium to stream audio - nothing intensive. Irritating that it seems to say you can restart Cinnamon on the fly but nothing short of a full reboot seems to work. Nothing like it on any previous Cinnamon releases.
I have tweaked Chromium Flags a bit for performance and may go back to defaults to see if that fixes it. Would be interested in any confirmations of the cause and fix for it.
TRUST BUT VERIFY any advice from anybody, including me. Mint/Ubuntu user since 10.04 LTS. LM20 64 bit XFCE (Dell 1520). Dual boot LM20 XFCE / Win7 (Lenovo desktop and Acer netbook). Testing LM21.1 Cinnamon and XFCE Live for new Lenovo desktop.
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
/etc/mdm/Xsession: Beginning session setup...
localuser:drsv being added to access control list
** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
[cinnamon-settings-daemon-smartcard] Failed to start: no suitable smartcard driver could be found
[cinnamon-settings-daemon-smartcard] Failed to start: no suitable smartcard driver could be found
=== xinerama setup Configuration ===
Clone: false
Output: (null) attached to VGA-0
status: off
width: -1
height: -1
rate: -1
primary: true
position: -1 -1
Output: Laptop attached to LVDS
status: on
width: 1280
height: 800
rate: 60
primary: true
position: 0 0
Output: (null) attached to HDMI-0
status: off
width: -1
height: -1
rate: -1
primary: false
position: -1 -1
=== Applying Configuration Configuration ===
Clone: false
Output: (null) attached to VGA-0
status: off
width: -1
height: -1
rate: -1
primary: false
position: -1 -1
Output: Laptop attached to LVDS
status: on
width: 1280
height: 800
rate: 60
primary: true
position: 0 0
Output: (null) attached to HDMI-0
status: off
width: -1
height: -1
rate: -1
primary: false
position: -1 -1
(csd-power:2400): Gtk-WARNING **: Theme directory of theme oxygen has no size field
(nm-applet:2837): Gtk-WARNING **: Theme directory of theme oxygen has no size field
Cjs-Message: JS LOG: About to start Cinnamon
(nemo-desktop:2828): Gtk-WARNING **: Theme directory of theme oxygen has no size field
** Message: nemo-desktop: session is cinnamon, establishing proxy
St-Message: cogl npot texture sizes SUPPORTED
Cjs-Message: JS LOG: Cinnamon started at Thu Feb 01 2018 09:44:32 GMT-0600 (CST)
Cjs-Message: JS LOG: network applet: Cannot find connection for active (or connection cannot be read)
(cinnamon:2763): St-WARNING **: Ignoring length property that isn't a number at line 1703, col 13
Cinnamon warning: Log level 16: Theme directory of theme oxygen has no size field
openGL version 2.1 Mesa 17 detected (GL Cogl Driver)
MetaSyncRing disabled: couldn't find required GL extensions, or the minimum safe openGL version was not met
failed to create drawable
Cjs-Message: JS LOG: Invalid network device type, is 14
Cjs-Message: JS LOG: network applet: Found connection for active
(cinnamon-launcher:2762): Gtk-WARNING **: Theme directory of theme oxygen has no size field
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
(mate-panel:3138): Gtk-WARNING **: Theme directory of theme oxygen has no size field
Unable to open desktop file /usr/share/applications/caja-browser.desktop for panel launcher: No such file or directory
Unable to open desktop file /usr/share/applications/mate-terminal.desktop for panel launcher: No such file or directory
Window manager warning: Log level 16: Theme directory of theme oxygen has no size field
(nm-applet:2837): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed
mintUpdate: no process found
(mintUpdate.py:3276): Gtk-WARNING **: Theme directory of theme oxygen has no size field
cinnamon-session[2235]: WARNING: t+69.92496s: Could not launch application 'update-notifier.desktop': Unable to start application: Failed to execute child process "update-notifier" (No such file or directory)
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x5600008 ()
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: last_user_time (46908000) is greater than comparison timestamp (133391). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around...
Window manager warning: 0x3c00003 (Bottom Panel) appears to be one of the offending windows with a timestamp of 46908000. Working around...
Window manager warning: last_user_time (46908000) is greater than comparison timestamp (135418). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around...
Window manager warning: 0x3c00003 (Bottom Panel) appears to be one of the offending windows with a timestamp of 46908000. Working around...
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x5600008 ()
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: last_user_time (46908000) is greater than comparison timestamp (137304). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around...
Window manager warning: 0x3c00003 (Bottom Panel) appears to be one of the offending windows with a timestamp of 46908000. Working around...
(firefox:3599): Gtk-WARNING **: Theme directory of theme oxygen has no size field
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x5600008 ()
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: last_user_time (46908000) is greater than comparison timestamp (152503). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around...
Window manager warning: 0x3c00003 (Bottom Panel) appears to be one of the offending windows with a timestamp of 46908000. Working around...
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x6200085 (*.Xauthority (~))
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x5600008 ()
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: last_user_time (46908000) is greater than comparison timestamp (270505). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around...
Window manager warning: 0x3c00003 (Bottom Panel) appears to be one of the offending windows with a timestamp of 46908000. Working around...
(/usr/lib/firefox/firefox:3735): dconf-WARNING **: Unable to open /var/lib/flatpak/exports/share/dconf/profile/user: Permission denied
(/usr/lib/firefox/firefox:3787): dconf-WARNING **: Unable to open /var/lib/flatpak/exports/share/dconf/profile/user: Permission denied
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x5600008 ()
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: last_user_time (46908000) is greater than comparison timestamp (1714971). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around...
Window manager warning: 0x3c00003 (Bottom Panel) appears to be one of the offending windows with a timestamp of 46908000. Working around...
What does this all mean????? I don't want to have to re-install my LinuxMint as it works perfectly fine except when I login to my computer..