Fallback mode linux mint

Linux Mint Forums

Welcome to the Linux Mint forums!

How to fix Cinnamon in Fallback Mode?

How to fix Cinnamon in Fallback Mode?

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

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.

Re: How to fix Cinnamon in Fallback Mode?

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

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

Copy/paste the output in your next message.

Re: How to fix Cinnamon in Fallback Mode?

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

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?

Re: How to fix Cinnamon in Fallback Mode?

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

/.xsession-errors. Most of the time it will log what led to the crash so at least you know where the problem lies.

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.

Re: How to fix Cinnamon in Fallback Mode?

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

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: 1280×800@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:
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..

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

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

Cinnamon just crashed. You are currently running in fallback mode.

Cinnamon just crashed. You are currently running in fallback mode.

Post by dave8647 » Mon May 20, 2019 4:46 pm

After installing Linux Mint on my old Dell Inspiron 5160, I am getting the message «Cinnamon just crashed. You are currently running in fallback mode.» This happens after I log in. If I say Yes to restarting Mint, I get the same message. So I have learned to just say No. If I say No, then everything seems to work just fine. I can play CDs and DVDs, launch LibreOffice, browse the internet with Firefox, even play youtube videos. All the menus seem okay, nothing is missing, everything appears in order.

Sometimes when the desktop first appears, the icons — Computer, Home, Trash, etc are all missing. I can go to Control Center — Preferences — Desktop and turn these items off, then back on. After a reboot, these icons come back usually. Also during the loading process before login, I see erratic flickers of light, some colored lines and other stuff. That made me wonder about display issues as I have seen posts here with similar problems (with the crash message) and display drivers are often mentioned as a possible problem. But like I said, once I get past the crash message, say No, and presumably stay in so-called fallback mode, then everything seems to be okay. The display looks fine and has the proper resolution.

Is there anything in this OS comparable to Microsoft Windows Event Viewer that might help identify why the crash message is appearing? I know almost nothing about Linux, so consider me a newbie.

After looking through other posts, I ran the inxi report and the results are below. Let me know if you have any ideas about what is going on. Thanks.

System: Host: Inspiron-5160 Kernel: 4.15.0-20-generic i686 bits: 32 compiler: gcc v: 7.3.0 Desktop: Cinnamon 4.0.8
Distro: Linux Mint 19.1 Tessa base: Ubuntu 18.04 bionic
Machine: Type: Portable System: Dell product: Inspiron 5160 v: N/A serial:
Mobo: Dell model: N/A serial: BIOS: Dell v: A08 date: 03/21/2005
Battery: ID-1: BAT0 charge: 97.7 Wh condition: 60.7/97.7 Wh (62%) model: Panasonic DELL D0093 status: Full
CPU: Topology: Single Core model: Mobile Intel Pentium 4 bits: 32 type: MT arch: Netburst Smithfield rev: 1
L2 cache: 1024 KiB
flags: pae sse sse2 sse3 bogomips: 12758
Speed: 1867 MHz min/max: 1867/3200 MHz Core speeds (MHz): 1: 1867 2: 1867
Graphics: Device-1: NVIDIA NV34M [GeForce FX Go5200 64M] vendor: Dell Inspiron 5160 driver: nouveau v: kernel bus ID: 01:00.0
Display: x11 server: X.Org 1.19.6 driver: nouveau unloaded: fbdev,modesetting,vesa resolution: 1400×1050

60Hz
OpenGL: renderer: NV34 v: 1.5 Mesa 18.0.5 direct render: Yes
Audio: Device-1: Intel 82801DB/DBL/DBM AC97 Audio vendor: Dell Inspiron 5160 driver: snd_intel8x0 v: kernel
bus ID: 00:1f.5
Sound Server: ALSA v: k4.15.0-20-generic
Network: Device-1: Broadcom Limited BCM4401-B0 100Base-TX vendor: Dell Inspiron 5160 driver: b44 v: 2.0 port: b080
bus ID: 02:01.0
Device-2: Intel PRO/Wireless 2200BG [Calexico2] Network driver: ipw2200 v: 1.2.2kmprq port: b080 bus ID: 02:02.0
IF: wlp2s2 state: up mac:
IF-ID-1: eth0 state: down mac:
Drives: Local Storage: total: 37.26 GiB used: 5.72 GiB (15.4%)
ID-1: /dev/sda vendor: Fujitsu model: MHV2040AH size: 37.26 GiB
Partition: ID-1: / size: 34.45 GiB used: 5.72 GiB (16.6%) fs: ext4 dev: /dev/dm-0
ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-1
Sensors: System Temperatures: cpu: 53.0 C mobo: N/A
Fan Speeds (RPM): cpu: 2548
Info: Processes: 159 Uptime: 6m Memory: 1.97 GiB used: 338.4 MiB (16.8%) Init: systemd runlevel: 5 Compilers: gcc: 7.3.0
Shell: bash v: 4.4.19 inxi: 3.0.27

Re: Cinnamon just crashed. You are currently running in fallback mode.

Post by jglen490 » Mon May 20, 2019 5:19 pm

Re: Cinnamon just crashed. You are currently running in fallback mode.

Post by jontrv » Mon May 20, 2019 5:28 pm

/.xsession-errors
and post the results, I do not know if that will help.

Re: Cinnamon just crashed. You are currently running in fallback mode.

Post by dave8647 » Mon May 20, 2019 6:11 pm

Here is the session-errors log.

/.xsession-errors
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1001/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/dave8647/.Xauthority
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting LANG=en_US.UTF-8
dbus-update-activation-environment: setting GDM_LANG=en_US
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting MANDATORY_PATH=/usr/share/gconf/cinnamon.mandatory.path
dbus-update-activation-environment: setting XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/dave8647
dbus-update-activation-environment: setting USER=dave8647
dbus-update-activation-environment: setting DESKTOP_SESSION=cinnamon
dbus-update-activation-environment: setting DEFAULTS_PATH=/usr/share/gconf/cinnamon.default.path
dbus-update-activation-environment: setting PWD=/home/dave8647
dbus-update-activation-environment: setting HOME=/home/dave8647
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/cinnamon:/usr/share/gnome:/home/dave8647/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share
dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=cinnamon
dbus-update-activation-environment: setting GTK_MODULES=gail:atk-bridge
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
dbus-update-activation-environment: setting IM_CONFIG_PHASE=1
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1001/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting SHLVL=1
dbus-update-activation-environment: setting LANGUAGE=en_US
dbus-update-activation-environment: setting GDMSESSION=cinnamon
dbus-update-activation-environment: setting LOGNAME=dave8647
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1001/bus
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1001
dbus-update-activation-environment: setting XAUTHORITY=/home/dave8647/.Xauthority
dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
dbus-update-activation-environment: setting XDG_CONFIG_DIRS=/etc/xdg/xdg-cinnamon:/etc/xdg
dbus-update-activation-environment: setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment
[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

(nm-applet:1350): Gtk-WARNING **: 16:56:53.088: Can’t set a parent on widget which has a parent
Cjs-Message: 16:56:53.250: JS LOG: About to start Cinnamon
Cjs-Message: 16:56:53.888: JS LOG: [LookingGlass/info] Cinnamon.AppSystem.get_default() started in 628 ms
Cjs-Message: 16:56:54.018: JS LOG: [LookingGlass/info] loading user theme: /usr/share/themes/Linux Mint/cinnamon/cinnamon.css
Cjs-Message: 16:56:54.192: JS LOG: [LookingGlass/info] added icon directory: /usr/share/themes/Linux Mint/cinnamon
** Message: 16:56:54.471: nemo-desktop: session is cinnamon, establishing proxy
Cjs-Message: 16:56:54.974: JS LOG: [LookingGlass/info] PlacesManager: Updating devices
St-Message: 16:56:54.994: cogl npot texture sizes NOT supported
Cjs-Message: 16:56:55.027: JS LOG: [LookingGlass/info] loaded at Mon May 20 2019 16:56:55 GMT-0500 (CDT)
Cjs-Message: 16:56:55.027: JS LOG: Cinnamon started at Mon May 20 2019 16:56:55 GMT-0500 (CDT)
Cjs-Message: 16:56:55.300: JS LOG: [LookingGlass/info] ExtensionSystem started in 2 ms
Cjs-Message: 16:56:55.302: JS LOG: [LookingGlass/info] DeskletManager started in 2 ms
Cjs-Message: 16:56:55.302: JS LOG: [LookingGlass/info] SearchProviderManager started in 4 ms
openGL version 1.5 Mesa 18 detected (GL Cogl Driver)
MetaSyncRing disabled: couldn’t find required GL extensions, or the minimum safe openGL version was not met
Cjs-Message: 16:56:56.051: JS LOG: [LookingGlass/info] Loaded applet show-desktop@cinnamon.org in 424 ms
Cjs-Message: 16:56:56.138: JS LOG: [LookingGlass/info] Loaded applet removable-drives@cinnamon.org in 88 ms
Cjs-Message: 16:56:56.767: JS LOG: [LookingGlass/info] Loaded applet calendar@cinnamon.org in 628 ms
Cjs-Message: 16:56:56.871: JS LOG: [LookingGlass/info] Loaded applet keyboard@cinnamon.org in 104 ms
Cjs-Message: 16:56:56.934: JS LOG: [LookingGlass/info] Role locked: notifications
Cjs-Message: 16:56:57.045: JS LOG: [LookingGlass/info] Loaded applet notifications@cinnamon.org in 174 ms
Cjs-Message: 16:56:57.080: JS LOG: [LookingGlass/info] Role locked: tray
Cjs-Message: 16:56:57.097: JS LOG: [LookingGlass/info] Loaded applet systray@cinnamon.org in 46 ms
Cjs-Message: 16:56:57.235: JS LOG: [LookingGlass/info] Loaded applet power@cinnamon.org in 138 ms
Cjs-Message: 16:56:57.599: JS LOG: [LookingGlass/info] Loaded applet user@cinnamon.org in 362 ms

(csd-power:1167): power-plugin-CRITICAL **: 16:56:57.822: abs_to_percentage: assertion ‘max > min’ failed
Cjs-Message: 16:56:57.935: JS LOG: [LookingGlass/info] Role locked: panellauncher
Cjs-Message: 16:56:57.957: JS LOG: [LookingGlass/info] Loaded applet panel-launchers@cinnamon.org in 358 ms
Cjs-Message: 16:56:58.647: JS LOG: [LookingGlass/info] Loaded applet sound@cinnamon.org in 690 ms
Cjs-Message: 16:56:58.877: JS LOG: [LookingGlass/info] Loaded applet window-list@cinnamon.org in 228 ms
Cjs-Message: 16:56:58.937: JS LOG: [LookingGlass/info] Loaded applet network@cinnamon.org in 58 ms
failed to create drawable
Cjs-Message: 16:57:00.762: JS LOG: Unknown network device type, is 14
Cjs-Message: 16:57:02.735: JS LOG: [LookingGlass/info] Loaded applet menu@cinnamon.org in 3798 ms
Cjs-Message: 16:57:02.737: JS LOG: [LookingGlass/info] AppletManager started in 7708 ms
Cjs-Message: 16:57:02.750: JS LOG: [LookingGlass/info] Cinnamon took 9498 ms to start

(cinnamon:1312): Cogl-CRITICAL **: 16:57:03.517: cogl_bitmap_new_for_data: assertion ‘cogl_is_context (context)’ failed
Gtk-Message: 16:57:04.784: GtkDialog mapped without a transient parent. This is discouraged.
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

(nm-applet:1350): Gdk-CRITICAL **: 16:57:06.573: gdk_window_thaw_toplevel_updates: assertion ‘window->update_and_descendants_freeze_count > 0’ failed

(metacity:1447): metacity-WARNING **: 16:57:24.116: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4e00054 (mintMenu.py)

(metacity:1447): metacity-WARNING **: 16:57:24.116: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.

(metacity:1447): metacity-WARNING **: 16:58:26.749: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4e00054 (mintMenu.py)

(metacity:1447): metacity-WARNING **: 16:58:26.749: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
dave8647@Inspiron-5160:

Источник