Cinnamon Sticks on Boot (Mint 18.1, 64bit)

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
blumf
Level 1
Level 1
Posts: 10
Joined: Thu Aug 08, 2013 7:38 pm

Cinnamon Sticks on Boot (Mint 18.1, 64bit)

Post by blumf »

Recently upgraded to 18.1 and am finding that (approx) 1 in 4 boots ends up with Cinnamon getting stuck, hammering the CPU and HD.

I can <ctrl>+<alt>+<F1> to a console and log in, but not knowing any details to check, the only thing I do is reboot.

I have the system setup to automatically log in, if that has any bearing on the issue.

Intel 3400 Series chipset.
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.
blumf
Level 1
Level 1
Posts: 10
Joined: Thu Aug 08, 2013 7:38 pm

Re: Cinnamon Sticks on Boot (Mint 18.1, 64bit)

Post by blumf »

This is still happening, although slightly less often (about 1 in 20 now)

It gets as far as starting the X server (can see and move mouse pointer) but nothing loads, just a black screen

Issuing from the console:

Code: Select all

sudo systemctl restart mdm.service
...restarts the session and it auto-logs in as normal at that point.

If anybody can suggest a log file to look in or any other diagnostic info/ideas I'd appreciate it, as it's rather annoying.
killer de bug

Re: Cinnamon Sticks on Boot (Mint 18.1, 64bit)

Post by killer de bug »

in /var/log you can check the syslog and kern.log files.
You can past the last 20 lines here next time you observe this behavior.
ColdBoot

Re: Cinnamon Sticks on Boot (Mint 18.1, 64bit)

Post by ColdBoot »

blumf wrote:Recently upgraded to 18.1 and am finding that (approx) 1 in 4 boots ends up with Cinnamon getting stuck, hammering the CPU and HD.
You're not alone. Before I've set nomodeset it happened at every other boot so you can try that to alleviate the problem.
ColdBoot

Re: Cinnamon Sticks on Boot (Mint 18.1, 64bit)

Post by ColdBoot »

It happend... here's how things look in syslog:

A

Code: Select all

pr 30 08:50:01 nighthawk systemd[1]: Starting Stop ureadahead data collection...
Apr 30 08:50:01 nighthawk systemd[1]: Stopped Read required files in advance.
Apr 30 08:50:01 nighthawk systemd[1]: Started Stop ureadahead data collection.
Apr 30 08:50:08 nighthawk kernel: [   56.664409] traps: cinnamon-settin[1341] trap int3 ip:7fa57b0d7a5b sp:7ffdfbec1c70 error:0
Apr 30 08:50:08 nighthawk cinnamon-session[1234]: WARNING: t+50,80800s: Application 'cinnamon-settings-daemon.desktop' killed by signal 5
Apr 30 08:51:25 nighthawk console-kit-daemon[1160]: (process:1999): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Apr 30 08:51:25 nighthawk acpid: client 1108[0:0] has disconnected
Apr 30 08:51:36 nighthawk systemd[1]: Started Session 1 of user sasa.
Apr 30 08:51:36 nighthawk console-kit-daemon[1160]: (process:2025): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Edit: from kern.log:

Code: Select all

Apr 30 08:49:19 nighthawk NetworkManager[932]: <info>  [1493534959.2044] manager: NetworkManager state is now CONNECTED_LOCAL
Apr 30 08:49:19 nighthawk NetworkManager[932]: <info>  [1493534959.2056] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 30 08:49:19 nighthawk NetworkManager[932]: <info>  [1493534959.2057] policy: set 'Wired connection 1' (enp3s0) as default for IPv4 routing and DNS
Apr 30 08:49:19 nighthawk NetworkManager[932]: <info>  [1493534959.2058] dns-plugin[0x27a14e0]: starting dnsmasq...
Apr 30 08:49:19 nighthawk NetworkManager[932]: <info>  [1493534959.2087] dns-mgr: Writing DNS information to /sbin/resolvconf
Apr 30 08:49:19 nighthawk NetworkManager[932]: <info>  [1493534959.3168] device (enp3s0): Activation: successful, device activated.
Apr 30 08:49:19 nighthawk NetworkManager[932]: <info>  [1493534959.3212] dnsmasq[0x27a14e0]: dnsmasq appeared as :1.34
Apr 30 08:49:24 nighthawk NetworkManager[932]: <info>  [1493534964.7766] manager: startup complete
Apr 30 08:49:26 nighthawk NetworkManager[932]: <info>  [1493534966.7778] manager: WiFi hardware radio set enabled
Apr 30 08:49:26 nighthawk NetworkManager[932]: <info>  [1493534966.7778] manager: WWAN hardware radio set enabled
Apr 30 08:50:08 nighthawk kernel: [   56.664409] traps: cinnamon-settin[1341] trap int3 ip:7fa57b0d7a5b sp:7ffdfbec1c70 error:0
Apr 30 0
blumf
Level 1
Level 1
Posts: 10
Joined: Thu Aug 08, 2013 7:38 pm

Re: Cinnamon Sticks on Boot (Mint 18.1, 64bit)

Post by blumf »

Finally happened again for me. X appears to start, mouse pointer shows and is moveable, otherwise blank screen. HD light is continuously flickering, until I <ctrl>+<alt>+F1 to the console (<c>+<a>+F8 back to the session, HD starts flickering again)

I'm guessing, some kind of race condition?

That 'GLib-CRITICAL' in syslog relevant?

Here's the logs:

tail -n 25 /var/log/syslog

Code: Select all

May  3 21:37:00 pawpaw nm-dispatcher: req:2 'up' [wlp5s0b1]: start running ordered scripts...
May  3 21:37:00 pawpaw NetworkManager[718]: <info>  [1493843820.9156] dnsmasq[0x13690e0]: dnsmasq appeared as :1.28
May  3 21:37:00 pawpaw dnsmasq[1317]: setting upstream servers from DBus
May  3 21:37:00 pawpaw dnsmasq[1317]: using nameserver 192.168.1.1#53(via wlp5s0b1)
May  3 21:37:00 pawpaw ModemManager[685]: <info>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:1c.1/0000:05:00.0': not supported by any plugin
May  3 21:37:00 pawpaw ModemManager[685]: <info>  Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:1c.2/0000:06:00.0': not supported by any plugin
May  3 21:37:01 pawpaw dbus[669]: [system] Activating via systemd: service name='org.freedesktop.UDisks2' unit='udisks2.service'
May  3 21:37:01 pawpaw systemd[1]: Starting Disk Manager...
May  3 21:37:01 pawpaw udisksd[1394]: udisks daemon version 2.1.7 starting
May  3 21:37:01 pawpaw dbus[669]: [system] Successfully activated service 'org.freedesktop.UDisks2'
May  3 21:37:01 pawpaw systemd[1]: Started Disk Manager.
May  3 21:37:01 pawpaw udisksd[1394]: Acquired the name org.freedesktop.UDisks2 on the system message bus
May  3 21:37:01 pawpaw org.gtk.vfs.AfcVolumeMonitor[1211]: Volume monitor alive
May  3 21:37:01 pawpaw dbus[669]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
May  3 21:37:01 pawpaw systemd[1]: Starting Manage, Install and Generate Color Profiles...
May  3 21:37:01 pawpaw dbus[669]: [system] Successfully activated service 'org.freedesktop.ColorManager'
May  3 21:37:01 pawpaw systemd[1]: Started Manage, Install and Generate Color Profiles.
May  3 21:37:01 pawpaw colord-sane: [bjnp] create_broadcast_socket: ERROR - bind socket to local address failed - Cannot assign requested address
May  3 21:37:02 pawpaw ntpd[1030]: Soliciting pool server 194.82.168.17
May  3 21:37:02 pawpaw systemd[1]: Stopping LSB: Start NTP daemon...
May  3 21:37:02 pawpaw ntp[1490]:  * Stopping NTP server ntpd
May  3 21:37:02 pawpaw ntpd[1030]: ntpd exiting on signal 15 (Terminated)
May  3 21:37:02 pawpaw ntp[1490]:    ...done.
May  3 21:37:02 pawpaw systemd[1]: Stopped LSB: Start NTP daemon.
May  3 21:37:02 pawpaw systemd[1]: Stopped LSB: Start NTP daemon.
May  3 21:37:02 pawpaw systemd[1]: Starting LSB: Start NTP daemon...
May  3 21:37:02 pawpaw ntp[1604]:  * Starting NTP server ntpd
May  3 21:37:02 pawpaw ntpd[1614]: ntpd 4.2.8p4@1.3265-o Wed Apr  5 13:28:07 UTC 2017 (1): Starting
May  3 21:37:02 pawpaw ntpd[1614]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 108:114
May  3 21:37:02 pawpaw ntpd[1616]: proto: precision = 0.088 usec (-23)
May  3 21:37:02 pawpaw ntpd[1616]: unable to bind to wildcard address :: - another process may be running - EXITING
May  3 21:37:02 pawpaw ntp[1604]:    ...done.
May  3 21:37:02 pawpaw systemd[1]: Started LSB: Start NTP daemon.
May  3 21:37:02 pawpaw avahi-daemon[694]: Joining mDNS multicast group on interface wlp5s0b1.IPv6 with address fe80::de56:56bb:72e7:1d4.
May  3 21:37:02 pawpaw avahi-daemon[694]: New relevant interface wlp5s0b1.IPv6 for mDNS.
May  3 21:37:02 pawpaw avahi-daemon[694]: Registering new address record for fe80::de56:56bb:72e7:1d4 on wlp5s0b1.*.
May  3 21:37:03 pawpaw /cinnamon-killer-daemon: Bound Cinnamon restart to <Control><Alt>Escape.
May  3 21:37:03 pawpaw /cinnamon-killer-daemon: Bound Cinnamon restart to <Control><Alt>Escape.
May  3 21:37:03 pawpaw NetworkManager[718]: <info>  [1493843823.9601] manager: startup complete
May  3 21:37:08 pawpaw NetworkManager[718]: <info>  [1493843828.9800] manager: WiFi hardware radio set enabled
May  3 21:37:08 pawpaw NetworkManager[718]: <info>  [1493843828.9801] manager: WWAN hardware radio set enabled
May  3 21:37:11 pawpaw ntpdate[1529]: adjust time server 85.199.214.99 offset -0.052018 sec
May  3 21:37:12 pawpaw systemd[1]: Started LSB: Start NTP daemon.
May  3 21:37:25 pawpaw pulseaudio[1258]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
May  3 21:37:39 pawpaw console-kit-daemon[1063]: (process:1768): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
May  3 21:37:44 pawpaw systemd[1]: Starting Stop ureadahead data collection...
May  3 21:37:44 pawpaw systemd[1]: Stopped Read required files in advance.
May  3 21:37:44 pawpaw systemd[1]: Started Stop ureadahead data collection.
May  3 21:37:44 pawpaw systemd[1]: Started Session 1 of user scott.
May  3 21:37:44 pawpaw console-kit-daemon[1063]: (process:1787): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
tail -n 25 /var/log/Xorg.0.log

Code: Select all

[     6.724] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event4"
[     6.724] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[     6.724] (--) evdev: AT Translated Set 2 keyboard: Found keys
[     6.724] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[     6.724] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input4/event4"
[     6.724] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 15)
[     6.724] (**) Option "xkb_rules" "evdev"
[     6.724] (**) Option "xkb_model" "pc105"
[     6.724] (**) Option "xkb_layout" "gb"
[     6.724] (**) Option "xkb_variant" "extd"
[     6.726] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/event10)
[     6.726] (**) ETPS/2 Elantech Touchpad: Applying InputClass "evdev touchpad catchall"
[     6.726] (**) ETPS/2 Elantech Touchpad: Applying InputClass "evdev touchscreen catchall"
[     6.726] (**) ETPS/2 Elantech Touchpad: Applying InputClass "touchpad catchall"
[     6.726] (**) ETPS/2 Elantech Touchpad: Applying InputClass "Default clickpad buttons"
[     6.726] (II) LoadModule: "synaptics"
[     6.726] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[     6.726] (II) Module synaptics: vendor="X.Org Foundation"
[     6.726] 	compiled for 1.18.1, module version = 1.8.2
[     6.726] 	Module class: X.Org XInput Driver
[     6.726] 	ABI class: X.Org XInput driver, version 22.1
[     6.726] (II) Using input driver 'synaptics' for 'ETPS/2 Elantech Touchpad'
[     6.726] (**) ETPS/2 Elantech Touchpad: always reports core events
[     6.726] (**) Option "Device" "/dev/input/event10"
[     6.796] (II) synaptics: ETPS/2 Elantech Touchpad: ignoring touch events for semi-multitouch device
[     6.796] (--) synaptics: ETPS/2 Elantech Touchpad: x-axis range 0 - 1408 (res 31)
[     6.796] (--) synaptics: ETPS/2 Elantech Touchpad: y-axis range 0 - 640 (res 31)
[     6.796] (--) synaptics: ETPS/2 Elantech Touchpad: pressure range 0 - 255
[     6.796] (--) synaptics: ETPS/2 Elantech Touchpad: finger width range 0 - 15
[     6.796] (--) synaptics: ETPS/2 Elantech Touchpad: buttons: left right double triple
[     6.796] (--) synaptics: ETPS/2 Elantech Touchpad: Vendor 0x2 Product 0xe
[     6.796] (--) synaptics: ETPS/2 Elantech Touchpad: touchpad found
[     6.796] (**) ETPS/2 Elantech Touchpad: always reports core events
[     6.828] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input6/event10"
[     6.828] (II) XINPUT: Adding extended input device "ETPS/2 Elantech Touchpad" (type: TOUCHPAD, id 16)
[     6.828] (**) synaptics: ETPS/2 Elantech Touchpad: (accel) MinSpeed is now constant deceleration 2.5
[     6.828] (**) synaptics: ETPS/2 Elantech Touchpad: (accel) MaxSpeed is now 1.75
[     6.828] (**) synaptics: ETPS/2 Elantech Touchpad: (accel) AccelFactor is now 0.129
[     6.828] (**) ETPS/2 Elantech Touchpad: (accel) keeping acceleration scheme 1
[     6.828] (**) ETPS/2 Elantech Touchpad: (accel) acceleration profile 1
[     6.828] (**) ETPS/2 Elantech Touchpad: (accel) acceleration factor: 2.000
[     6.828] (**) ETPS/2 Elantech Touchpad: (accel) acceleration threshold: 4
[     6.828] (--) synaptics: ETPS/2 Elantech Touchpad: touchpad found
[     6.829] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/mouse1)
[     6.829] (**) ETPS/2 Elantech Touchpad: Ignoring device from InputClass "touchpad ignore duplicates"
[     7.563] (II) intel(0): EDID vendor "BOE", prod id 1410
[     7.563] (II) intel(0): Printing DDC gathered Modelines:
[     7.563] (II) intel(0): Modeline "1366x768"x0.0   72.33  1366 1414 1446 1526  768 771 777 790 -hsync -vsync (47.4 kHz eP)
[    46.792] (II) AIGLX: Suspending AIGLX clients for VT switch
[    46.894] (--) synaptics: ETPS/2 Elantech Touchpad: touchpad found
dmesg | tail -n 25

Code: Select all

[    5.841839] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[    5.842261] ieee80211 phy0: registered radio enabled led device: brcmsmac-phy0:radio gpio: 499
[    5.849815] brcmsmac bcma0:1 wlp5s0b1: renamed from wlan0
[    6.007066] cgroup: new mount options do not match the existing superblock, will be ignored
[    6.239314] random: crng init done
[    6.413591] IPv6: ADDRCONF(NETDEV_UP): wlp5s0b1: link is not ready
[    6.493400] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: false (implement)
[    6.493410] brcmsmac bcma0:1: brcms_ops_config: change power-save mode: false (implement)
[    6.493683] IPv6: ADDRCONF(NETDEV_UP): wlp5s0b1: link is not ready
[    6.503094] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
[    6.517725] r8169 0000:06:00.0 enp6s0: link down
[    6.517870] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
[    6.599735] IPv6: ADDRCONF(NETDEV_UP): wlp5s0b1: link is not ready
[    8.051049] wlp5s0b1: authenticate with 00:30:4f:75:9c:98
[    8.055446] wlp5s0b1: send auth to 00:30:4f:75:9c:98 (try 1/3)
[    8.057722] wlp5s0b1: authenticated
[    8.057907] brcmsmac bcma0:1 wlp5s0b1: disabling HT as WMM/QoS is not supported by the AP
[    8.057909] brcmsmac bcma0:1 wlp5s0b1: disabling VHT as WMM/QoS is not supported by the AP
[    8.062539] wlp5s0b1: associate with 00:30:4f:75:9c:98 (try 1/3)
[    8.064507] wlp5s0b1: RX AssocResp from 00:30:4f:75:9c:98 (capab=0x401 status=0 aid=49)
[    8.065334] brcmsmac bcma0:1: brcmsmac: brcms_ops_bss_info_changed: associated
[    8.065339] brcmsmac bcma0:1: brcms_ops_bss_info_changed: qos enabled: true (implement)
[    8.065351] wlp5s0b1: associated
[    8.065401] IPv6: ADDRCONF(NETDEV_CHANGE): wlp5s0b1: link becomes ready
[    8.143296] brcmsmac bcma0:1: brcms_ops_bss_info_changed: arp filtering: 1 addresses (implement)
killer de bug

Re: Cinnamon Sticks on Boot (Mint 18.1, 64bit)

Post by killer de bug »

I'm lost. I can't help you.
But it seems that the content of syslog is different for both crash. :?
deepakdeshp
Level 20
Level 20
Posts: 12341
Joined: Sun Aug 09, 2015 10:00 am

Re: Cinnamon Sticks on Boot (Mint 18.1, 64bit)

Post by deepakdeshp »

Not a perfect solution, but can you backup user files and re-install Mint once again?
If I have helped you solve a problem, please add [SOLVED] to your first post title, it helps other users looking for help.
Regards,
Deepak

Mint 21.1 Cinnamon 64 bit with AMD A6 / 8GB
Mint 21.1 Cinnamon AMD Ryzen3500U/8gb
ColdBoot

Re: Cinnamon Sticks on Boot (Mint 18.1, 64bit)

Post by ColdBoot »

deepakdeshp wrote:Not a perfect solution, but can you backup user files and re-install Mint once again?
What makes you think it'll change anything? This is not Windows, where reinstall is a cure for most problems. :mrgreen:

Restarting the mdm service is a simple workaround. The inconvenience is that I cannot expect my desktop will boot every time when I try to power it remotely and I need GUI up.
deepakdeshp
Level 20
Level 20
Posts: 12341
Joined: Sun Aug 09, 2015 10:00 am

Re: Cinnamon Sticks on Boot (Mint 18.1, 64bit)

Post by deepakdeshp »

ColdBoot wrote:
deepakdeshp wrote:Not a perfect solution, but can you backup user files and re-install Mint once again?
What makes you think it'll change anything? This is not Windows, where reinstall is a cure for most problems. :mrgreen:

Restarting the mdm service is a simple workaround. The inconvenience is that I cannot expect my desktop will boot every time when I try to power it remotely and I need GUI up.
I am not a newb with Linux. Rather I have more experienc on Linux or Unix right from AT &T Unix sys 5 through Solaris through Red hat Ubuntu and Mint.
Any way what makes me think what reformating will work is, there are some user actions like editing some important files or play around with the system so that the system may act funny.
Just to test, booting from Live DVD or USB can be done too.
If I have helped you solve a problem, please add [SOLVED] to your first post title, it helps other users looking for help.
Regards,
Deepak

Mint 21.1 Cinnamon 64 bit with AMD A6 / 8GB
Mint 21.1 Cinnamon AMD Ryzen3500U/8gb
ColdBoot

Re: Cinnamon Sticks on Boot (Mint 18.1, 64bit)

Post by ColdBoot »

deepakdeshp wrote: I am not a newb with Linux. Rather I have more experienc on Linux or Unix right from AT &T Unix sys 5 through Solaris through Red hat Ubuntu and Mint.
Any way what makes me think what reformating will work is, there are some user actions like editing some important files or play around with the system so that the system may act funny.
Just to test, booting from Live DVD or USB can be done too.
Thank you deepakdeshp, :)

Since I currently don't have a spare OS or a computer, I'm not keen at all on tinkering with the default setup, the sole exceptions being installing Nvidia driver (as my desktop totally freezes with Nuveau driver) and adding nomodeset in the attempt to resolve this issue. However, since Saturday I've switched to 4.10.0-20 kernel and after more than dozen restarts, done on purpose, no sign of killed cinnamon-settings-daemon on my machine though it is too early... if it persists till next Saturday, I'll consider that kernel upgrade fixed it.
kleinbottle
Level 1
Level 1
Posts: 23
Joined: Thu Aug 25, 2011 4:26 pm

Re: Cinnamon Sticks on Boot (Mint 18.1, 64bit)

Post by kleinbottle »

I can confirm the same problem.Cinnamon is basically borked.Re-installing it isn't going to make a jot of a difference.This issue seems to have crept up post 17.1.However MATE 18.1 64-bit works just fine.A bug report (but no solution) has been filed here: https://bugs.launchpad.net/linuxmint/+bug/1653160
Mobo:Asus P8 H77-I Intel GPU;i3 CPU,4GB RAM
blumf
Level 1
Level 1
Posts: 10
Joined: Thu Aug 08, 2013 7:38 pm

Re: Cinnamon Sticks on Boot (Mint 18.1, 64bit)

Post by blumf »

Well, it's been a while since I've had a problem, it may be because I've upgraded the kernel. Currently on 4.10.0-21 which had a bunch of fixes for the drm/i915 module (although that's just a guess at the issue)

Now I've mentioned that, expect the next boot to fail :roll:
Locked

Return to “Installation & Boot”