How to fix Cinnamon in Fallback Mode?

Please post suggestions for improvement of Cinnamon here
https://github.com/linuxmint/Cinnamon
Post Reply
Frederick Turner
Level 1
Level 1
Posts: 20
Joined: Wed Sep 02, 2015 2:57 pm

How to fix Cinnamon in Fallback Mode?

Post by Frederick Turner » Sun Sep 27, 2015 11:51 am

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.
Linux Mint 17.2 64-bit Cinnamon

User avatar
Pjotr
Level 19
Level 19
Posts: 9665
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland)
Contact:

Re: How to fix Cinnamon in Fallback Mode?

Post by Pjotr » Sun Sep 27, 2015 11:56 am

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:

Code: Select all

inxi -Fxz
(if you type: the letter F is a capital letter)

Press Enter.

Copy/paste the output in your next message.
Tip: 10 things to do after installing Linux Mint 18.3 Sylvia
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.

Frederick Turner
Level 1
Level 1
Posts: 20
Joined: Wed Sep 02, 2015 2:57 pm

Re: How to fix Cinnamon in Fallback Mode?

Post by Frederick Turner » Sun Sep 27, 2015 12:03 pm

Here it is:

Code: Select all

System:    Host: mint-ThinkPad-T61 Kernel: 3.16.0-38-generic x86_64 (64 bit, gcc: 4.8.2) 
           Desktop: Cinnamon 2.6.13  Distro: Linux Mint 17.2 Rafaela
Machine:   System: LENOVO product: 8896WFX version: ThinkPad T61
           Mobo: LENOVO model: 8896WFX Bios: LENOVO version: 7LETC9WW (2.29 ) date: 03/18/2011
CPU:       Dual core Intel Core2 Duo CPU T8100 (-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 8378.84 
           Clock Speeds: 1: 800.00 MHz 2: 1200.00 MHz
Graphics:  Card: Intel Mobile GM965/GL960 Integrated Graphics Controller (primary) bus-ID: 00:02.0 
           X.Org: 1.15.1 drivers: intel (unloaded: fbdev,vesa) Resolution: 1920x1200@60.0hz 
           GLX Renderer: Mesa DRI Intel 965GM GLX Version: 2.1 Mesa 10.1.3 Direct Rendering: Yes
Audio:     Card: Intel 82801H (ICH8 Family) HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 
           Sound: Advanced Linux Sound Architecture ver: k3.16.0-38-generic
Network:   Card-1: Intel PRO/Wireless 4965 AG or AGN [Kedron] Network Connection 
           driver: iwl4965 ver: in-tree: bus-ID: 03:00.0
           IF: wlan0 state: down mac: <filter>
           Card-2: Intel 82566MM Gigabit Network Connection driver: e1000e ver: 2.3.2-k port: 1840 bus-ID: 00:19.0
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 1878.4GB (17.1% used) 1: id: /dev/sda model: ST1750LM000_HN size: 1750.4GB 
           2: id: /dev/sdb model: SAMSUNG_MZ7PC128 size: 128.0GB 
Partition: ID: / size: 9.1G used: 6.0G (70%) fs: ext4 ID: /home size: 17G used: 1.3G (9%) fs: ext4 
           ID: swap-1 size: 6.04GB used: 0.00GB (0%) fs: swap 
RAID:      No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Sensors:   System Temperatures: cpu: 50.0C mobo: 48.0C 
           Fan Speeds (in rpm): cpu: 2983 
Info:      Processes: 166 Uptime: 33 min Memory: 1720.5/3879.8MB Runlevel: 2 Gcc sys: 4.8.4 
           Client: Shell (bash 4.3.11) inxi: 1.9.17 
I hope this provides any clues. Do you think its hardware related?
Linux Mint 17.2 64-bit Cinnamon

User avatar
Pjotr
Level 19
Level 19
Posts: 9665
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland)
Contact:

Re: How to fix Cinnamon in Fallback Mode?

Post by Pjotr » Sun Sep 27, 2015 12:20 pm

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?
Tip: 10 things to do after installing Linux Mint 18.3 Sylvia
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.

JosephM
Level 5
Level 5
Posts: 834
Joined: Sun May 26, 2013 6:25 pm

Re: How to fix Cinnamon in Fallback Mode?

Post by JosephM » Mon Sep 28, 2015 3:12 am

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.

I2k4
Level 4
Level 4
Posts: 439
Joined: Thu Feb 02, 2012 8:33 pm

Re: How to fix Cinnamon in Fallback Mode?

Post by I2k4 » Mon Oct 12, 2015 1:15 pm

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. Ubuntu / Mint user since 10.04 LTS. M17.3 Cinnamon (Dell 1520). Dual booting M17.3 XFCE / W7 (Acer netbook) and M18.2 Cinnamon / W7 (Lenovo desktop). Testing M18.3 64bit on persistent live USB.

DoctorVell
Level 1
Level 1
Posts: 5
Joined: Thu Feb 01, 2018 11:50 am
Location: San Antonio, Texas
Contact:

Re: How to fix Cinnamon in Fallback Mode?

Post by DoctorVell » Thu Feb 01, 2018 12:15 pm

Hi there,

I know this is an old topic...but I am new to LinuxMint and I am now coming up with this error...

Here is my result of "inxi -Fxz"

System: Host: DRSV Kernel: 4.13.0-32-generic x86_64 (64 bit gcc: 5.4.0)
Desktop: Cinnamon 3.6.7 (Gtk 3.18.9-1ubuntu3.3)
Distro: Linux Mint 18.3 Sylvia
Machine: System: Gateway product: M-1625 v: 3409925R
Mobo: Gateway model: N/A v: 9D.04
Bios: Phoenix v: 9D.04 date: 04/07/2008
CPU: Dual core AMD Turion 64 X2 Mobile TL-60 (-MCP-) cache: 1024 KB
flags: (lm nx sse sse2 sse3 svm) bmips: 3192
clock speeds: max: 2000 MHz 1: 800 MHz 2: 800 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] RS690M [Radeon Xpress 1200/1250/1270]
bus-ID: 01:05.0
Display Server: X.Org 1.18.4 drivers: ati,radeon (unloaded: fbdev,vesa)
Resolution: 1280x800@60.00hz
GLX Renderer: ATI RS690
GLX Version: 2.1 Mesa 17.2.4 Direct Rendering: Yes
Audio: Card-1 Advanced Micro Devices [AMD/ATI] RS690 HDMI Audio [Radeon Xpress 1200 Series]
driver: snd_hda_intel bus-ID: 01:05.2
Card-2 Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA)
driver: snd_hda_intel bus-ID: 00:14.2
Sound: Advanced Linux Sound Architecture v: k4.13.0-32-generic
Network: Card-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
driver: r8169 v: 2.3LK-NAPI port: a000 bus-ID: 07:00.0
IF: enp7s0 state: down mac: <filter>
Card-2: Realtek RTL8187B Wireless 802.11g 54Mbps Network Adapter
usb-ID: 001-005
IF: null-if-id state: N/A mac: N/A
Drives: HDD Total Size: 1750.4GB (91.2% used)
ID-1: /dev/sda model: WDC_WD2500BEVS size: 250.1GB
ID-2: USB /dev/sdb model: External_USB_3.0 size: 1500.3GB
Partition: ID-1: / size: 228G used: 133G (62%) fs: ext4 dev: /dev/sda1
ID-2: swap-1 size: 2.01GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 71.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 182 Uptime: 28 min Memory: 1008.9/1866.6MB
Init: systemd runlevel: 5 Gcc sys: 5.4.0
Client: Shell (bash 4.3.481) inxi: 2.2.35 \
--------------------------------------------------------------
Then I saw the response to see what it says in .xsession-errors and here is what I got

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..

Thank you.
Doctor Vell ----- http://www.doctorvell.com

Level: Amateur (for now)
Kernel: 4.4.0-53-generic x86_64
Desktop: Cinnamon 3.2.7
Distro: Linux Mint 18.1 Serena

User avatar
Pjotr
Level 19
Level 19
Posts: 9665
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland)
Contact:

Re: How to fix Cinnamon in Fallback Mode?

Post by Pjotr » Thu Feb 01, 2018 12:54 pm

@DoctorVell:

Try these things:

1. Disable all visual effects in Cinnamon:
https://sites.google.com/site/easylinux ... n-Cinnamon
(item 7.1, right column)

2. While you're at it, apply some other safe speed tweaks on that web page as well.

3. Roll back to the latest kernel of the 4.4 series (currently: 4.4.0-112):
Update Manager - panel: View - Linux kernels

Reboot after installing it, and make sure you boot from it (it's under the header Advanced in the Grub bootloader menu).

No bootloader menu? Make it visible by repeatedly hitting the Esc key.
Tip: 10 things to do after installing Linux Mint 18.3 Sylvia
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.

Post Reply

Return to “Cinnamon”