Cinnamon freezes, only mouse pointer can move around. Linux Mint 17.1

[mxa]

I have sporadic freezes with Linux Mint 17 Cinnamon 64, only the mouse pointer can move. I can switch to another terminal. Programs keep running, music keeps playing (until the next song), just interaction with the desktop is impossible and screen gets not updated (except the mouse pointer). This happens when pressing alt+tab or alt+shift+tab, but is not reliably reproducable.

[clfarron4]

Have you looked in the system logs (in the /var/log/ folder), which might say what is going on?

[mxa]

I can't find anything suspicious in the logs.

[pacharanero]

I had the same problem but updating the linux kernel from the stock (3.13) to latest (currently 3.15.7) seems to have fixed it. (I hope)

[mxa]

It's hard to believe that a different Kernel would fix this kind of problem that seems to be so top level, window manager related. But I have updated to the current Kernel to give it a try. Unfortunately the sporadic crashes on alt-tab persist.

[mxa]

The problem occurs on alt-tab, seemingly particulary when pressing this command during the startup of an application. It just happened earlier and i switched to another tty with Ctl+Alt+F1, logged in and typed: egrep -i 'error|fail' ~/.xsession-errors here is a picture of the output:

[mxa]

Another occurance:

[shirish87]

I'm facing this issue while switching workspaces with Ctrl+Alt+Left/Right.

(cinnamon-settings-daemon:4755): media-keys-plugin-WARNING **: Grab failed for some keys, another application may already have access the them.
(dropbox:4849): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion 'private->update_and_descendants_freeze_count > 0' failed
Window manager warning: Log level 16: Error converting selection

[mxa]

@shirish87 I'll start using Ctl+Alt+Left/Right to see if I get freezes. Would you mind trying to use Ctl+Alt+(shift)+Tab? This way we can figure out if it is the same issue. Give it a few hours/days before drawing a conclusion.

[shirish87]

Agreed :)
Is there any other log file we need to keep track of, apart from .xsession-errors?

[mxa]

Very good qustion. I'm afraid I am not qualified to answer that. @clfarron4 says something about the system logs. I couldn not find anything there what seems relevant though.

[shirish87]

Just experienced the freeze again, and this time it was when I clicked a minimized window. @mxa, I think this happens whenever we switch away from the current window, either while switching workspaces or tabs or restoring a minimized window.

.xsession-errors this time contains about 50 entries of No such key 'picture-options'.

In my experience, I think I've always had a browser window (Maxthon) in the foreground and switched away from it.

Update: The most recent freeze on my machine correlates to a segfault caused by Maxthon.

shirish@SIRIUS-3 ~ $ cat /var/log/kern.log | grep segfault
Aug 11 23:29:45 SIRIUS-3 kernel: [21172.052150] events[24314]: segfault at 40 ip 00007f43c42c3b3f sp 00007f43c0edcbd0 error 4 in libusb-1.0.so.0.1.0[7f43c42bc000+15000]
Aug 12 20:41:30 SIRIUS-3 kernel: [ 5064.377192] cinnamon-settin[8432]: segfault at 8 ip 00007fafe9cbc51e sp 00007fff5ae2beb0 error 4 in libnetwork.so[7fafe9cac000+1f000]
Aug 12 20:41:37 SIRIUS-3 kernel: [ 5071.528480] cinnamon-settin[8441]: segfault at 8 ip 00007ff96b9d451e sp 00007fff80076270 error 4 in libnetwork.so[7ff96b9c4000+1f000]
Aug 13 04:09:21 SIRIUS-3 kernel: [31952.298496] plugin-containe[30828]: segfault at 4068 ip 00007fd1e8a9f414 sp 00007fffedd1b2f0 error 4 in libpthread-2.19.so[7fd1e8a95000+19000]
Aug 13 04:09:37 SIRIUS-3 kernel: [31968.321200] plugin-containe[31551]: segfault at 4068 ip 00007f760be4b414 sp 00007fffe2c76b50 error 4 in libpthread-2.19.so[7f760be41000+19000]
Aug 13 04:10:17 SIRIUS-3 kernel: [32008.421912] plugin-containe[31580]: segfault at 4068 ip 00007f2e10619414 sp 00007ffffa083100 error 4 in libpthread-2.19.so[7f2e1060f000+19000]
Aug 13 04:13:28 SIRIUS-3 kernel: [32199.408023] plugin-containe[32046]: segfault at 4068 ip 00007f2d76137414 sp 00007fffab3445e0 error 4 in libpthread-2.19.so[7f2d7612d000+19000]
Aug 13 04:26:39 SIRIUS-3 kernel: [32990.969440] plugin-containe[32150]: segfault at 4068 ip 00007fdd5f466414 sp 00007fff6b4adc30 error 4 in libpthread-2.19.so[7fdd5f45c000+19000]
Aug 13 18:11:05 SIRIUS-3 kernel: [ 3805.775249] Watchdog[3292]: segfault at 0 ip 00007fa23924ab1e sp 00007fa2291d92d0 error 6 in maxthon[7fa23504a000+6917000]
Aug 13 19:02:05 SIRIUS-3 kernel: [ 6867.241369] Watchdog[9679]: segfault at 0 ip 00007fc51d454b1e sp 00007fc50d3e32d0 error 6 in maxthon[7fc519254000+6917000]
Aug 13 19:02:15 SIRIUS-3 kernel: [ 6877.423742] Watchdog[13727]: segfault at 0 ip 00007f556530fb1e sp 00007f555529e2d0 error 6 in maxthon[7f556110f000+6917000]

@mxa The next time you experience a freeze, please check the above logs on your system.

Update 2: Ignore all of the above. Finally tracked my issue to be caused by Variety (wallpaper changer). Thanks.

[mxa]

I've restrained myself not to use Ctl.+Alt+(Shift)+Tab any more. I use Ctl.+Alt+Left/Right to switch between workspaces rather than changing the Z order of apps now. This is running stable for me. No crashes. Also I never had problems minimizing applications by clicking on the taskbar. I start to think we have two different issues.

[mxa]

@shirish87 nothing suspicious in my logs after the freeze. I was able to restart cinnamon with Ctl.+Alt+Backspace however this time.

[mtwebster]

The issue with the window alt-tabber still exists in current Cinnamon master (workaround for now is use a different alt-tab style), but I'm hoping the freeze issue is fixed now - are there any brave souls here that could try the nightly ppa?

[mxa]

what's the different alt-tab style? Is the nightly PPA this one: ppa:gwendal-lebihan-dev/cinnamon-nightly ?

[mtwebster]

If you go into Settings->Windows-> Alt-Tab Switcher Style - use preview, coverflow, or timeline for now.

Yes, that's the nightly. If you're on Mint though, you can't just add it, update, and upgrade. Instead, do this after adding the ppa and apt-get updating:

sudo apt-get install -ttrusty cinnamon muffin cinnamon-settings-daemon libcinnamon-desktop0 libcjs0e cjs

If you use nemo-preview, you'll want to uninstall that first.

[mxa]

@mtwebster thank you so much for the workaround - I had no more freezes since. I'm not brave enough to try the nightly as I'm in the middle of production.

[mxa]

After some weeks I can say that this workaround does reduce the likelyhood of a freeze drastically, but it still happens some times. I have now "Window preview (No icons)" selected in the Window properties.

[ghost]

I can confirm the problem is still here. It append when I switch windows from the taskbar.
It almost always reproductible (to make it crash) when I switch between windows quickly for 30s to 1mn.

It's like this one #2946

[ghost]

I just tried with a live USB on an other PC, a laptop with intel integrated graphics (I have a desktop with Nvidia GPU) and I had a freeze in 2mn simply by quickly switching windows and moving windows order from the taskbar.

So I guess everyone install of Linux Mint 17.1 has the bug but it occur ramdomly when you switch/move windows with the tasktar or with alt+tab.

[pollend]

I've been experiencing a similar issue. Everything on the desktop freezes, but the mouse cursor.

[ghost]

Same, I've been getting these random Cinnamon glitches on all my Mint 17 setups. I can restart cinnamon by opening another tty (e.g. CTRL + ALT + F2) and, after logging in as root, killall -9 cinnamon
Any ideas?

[jonorthwash]

For me, the glitches are momentary. I'm not sure what triggers them, but video playback seems to make it last longer. Normally it's only a few hundred milliseconds every 5 or 6 seconds under a normal load. Everything freezes except the mouse cursor for that period. For instance, I can rapidly drag a window in a continuous circle, and when the freeze happens, my cursor continues in the circle while everything else on the screen is frozen. Alternatively, I can hold a key on the keyboard, and get a steady rate of input of that character, but when the glitch occurs, everything on the screen freezes. After a short pause, everything "catches up" to where it should be—i.e., the window "reattaches" to where the mouse cursor's new location, and the keystrokes that were not displayed appear all at once.

My guess would be that it has something to do with threading in the composite manager, or something similar...

[HerrDIerk]

Same issue here. When Cinnamon freezes, the only icon I can click on is the menu. The menubar and others are frozen. I have to open a new program (mostly Firefox) and my desktop wakes up. I never had such a "problem" in my previous versions. But this makes it interesting, isn't it :-)
I never have this with pushing Alt-Tab or any other button.

[mxa]

@mtwebster I am now using the nightly and my cinnamon is version 2.4.6-20150210040008-trusty. The freeze is still occurring sometimes, albeit not as often as before. When it is occurring I can still quit Cinnamon with Ctl+Alt+Backspace (loosing all open applications). That's a little bit more convenient then having to do a hardware reset.

[shirish87]

@mxa You can avoid losing all open applications by:

• Ctrl + Alt + F2
• Log in with your credentials
• Terminate all cinnamon processes killall -HUP cinnamon
• Come back to your desktop with Ctrl + Alt + F8

[mxa]

That is definitely not working. On coming back to F8 everything is still freezed, mouse still moves.

[wrouesnel]

I am experiencing this as well with current cinnamon nightlies (I update every morning). In my case it happened while I was switching desktops - the the windows got stuck mid-way in the slide animation.

Notably, the keyboard locked up for me to - the mouse still moved, but Ctrl+Alt+F1 F2 etc. would not switch TTYs.

[mtwebster]

@wrouesnel (or anyone else feeling adventurous) Do you have a second PC (or smartphone) you can ssh into the problem machine? If you can, you might be able to get a trace of where it freezes - see https://github.com/linuxmint/Cinnamon/wiki/How-to-use-GDB-to-gather-debug-information-on-a-program where it says "Debugging Cinnamon" - you'd basically let it run until you get a freeze, then ctrl-c on the ssh client and get a trace at that point.

Thanks

[cpitclaudel]

I have this problem too, or at least one that looks similar. The freezes seem to happen mostly when I open certain applications (Evince, qpdfview, and the archive manager mostly). In my case the freeze is only temporary, and most of the time using Alt-tab to change applications makes it stop. I'll try the nightly and report.

[jonorthwash]

For me the "freezes" are temporary as well (and fairly momentary most of the time). From all indications, it's only a display issue of some kind—everything keeps on running while it's frozen (and the cursor moves, but doesn't appear to interact with anything, though when the freeze ends it's clear that it did). The freezes get longer the more time I've had the X Session running for, and are longest with programs like evince and gvim (especially when there's a lot of text in the buffer).

[mvdberge]

@mtwebster I tried to debug cinnamon on a Debian Jessie (running cinnamon 2.2.16-5) via gdb. Unfortunately, this cause cinnamon to freeze again. The log file had no interesting information in it, here are the last lines:

Reading symbols from /lib/x86_64-linux-gnu/libnss_dns.so.2...Reading symbols from /usr/lib/debug//lib/x86_64-linux-gnu/libnss_dns-2.19.so...done.
done.
Loaded symbols for /lib/x86_64-linux-gnu/libnss_dns.so.2
Reading symbols from /usr/lib/x86_64-linux-gnu/gconv/ISO8859-1.so...Reading symbols from /usr/lib/debug//usr/lib/x86_64-linux-gnu/gconv/ISO8859-1.so...done.
done.
Loaded symbols for /usr/lib/x86_64-linux-gnu/gconv/ISO8859-1.so
0x00007fd13b7d350d in poll () at ../sysdeps/unix/syscall-template.S:81
81 ../sysdeps/unix/syscall-template.S: Datei oder Verzeichnis nicht gefunden.
A debugging session is active.

   Inferior 1 [process 16234] will be detached.

Quit anyway? (y or n) Detaching from program: /usr/bin/cinnamon, process 16234

[mtwebster]

@mvdb-christmann I should have mentioned - once gdb attaches to the process, cinnamon will freeze, and you have to "c" or "continue", and it should proceed normally (then you can try to reproduce the real issue, etc..)

[mvdberge]

@mtwebster Was able to reproduce the bug with active gdb debugging but the output says nothing interesting. Just some debug symbols loading and normally starting and exiting threads. So obviously, the cinnamon process is not the root of all evil...
Any other ideas what could be the cause?

[mtwebster]

Well, not necessarily, cinnamon might just think it's doing anything wrong - when it freezes, do a ctr-c on the debugging terminal to break the process, then do a thread apply all bt - that'll spit out what all threads are doing (i'm guessing one of them is stuck waiting on something else) - after you've gotten the trace, you can 'c' to let cinnamon continue running. I'm curious what the traces show.

Thanks for helping out!

[mvdberge]

Just pasted the main output to pastebin: http://pastebin.com/rAkeRqNv

[mtwebster]

@mvdb-christmann You're still on Cinnamon 2.2 it looks like - this particular freeze has been fixed in 2.4.

[mtwebster]

Ah I see you did mention you were on 2.2 - sorry. Unfortunately, the fixes are not things we can backport (we completely updated cjs to a newer upstream, and refactored Cinnamon as well)

[mvdberge]

Huäääh... okay, let's see what debian maintainers will do... Thanks for helping me out!

[mtwebster]

@ EVERYONE....

There were huge changes between Cinnamon 2.2 and 2.4 with interaction between multiple packages - if you're experiencing freezing issues in 2.2, there's really nothing we can do - please upgrade to 2.4 (if possible) and see if your issue is resolved. These changes were done precisely because of a lot of these problems.

Of course with change comes new bugs - see #2946 (comment) for an easy-to-apply fix to try, or please try the Cinnamon Nightly PPA or build from source if that doesn't fix it (though drag-and-drop issue exists for everyone on Mint 17.1, it just depends on your use habits whether you encounter it or not).

I'll try to post up-to-date instructions on the wiki here later, on how to build from source (in debian systems) and in what order, etc..

Thanks

[jonorthwash]

I'm running straight from git (admittedly, it's been several weeks since I last pulled), and neither of those freezes describe what's happening for me. Should I open a new issue?

[mtwebster]

@jonorthwash I'd first try rebasing and re-building - just so our playing field is even. You can describe it here if you want.

The drag-and-drop bug could happen even if you're not intentionally dragging and dropping (It would happen to me 'accidentally' when clicking on window list items, and moving my mouse away too quickly, so it wasn't at first apparent what was causing it)

[Fantu]

Will 2.4.7 have the fixes included, right?
About debian for now 2.4 packages are only in debian experimental (with cinnamon 2.4.6).
2.4 can't be uploaded to jessie now in freeze, cjs 2.4 and also needed changes in cinnamon for cjs and this problems are too big.
I'll try to put 2.4 in jessie-backports when possible.

[matthijsmelissen]

I can confirm the freeze on alt-tab issue in Cinnamon 2.4.6.

Is there anything information I can provide to help resolving this issue?

[leigh123linux]

@mtwebster

My UI froze yesterday for about 30 seconds, this warning was in the logs could it be related to the freeze?

(nemo:1789): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed
Cjs-Message: JS LOG: Invalid or null source id used when attempting to run Mainloop.source_remove()
== Stack trace for context 0x24bbcc0 ==
overrideMainloop/Mainloop.source_remove@/usr/share/cinnamon/js/ui/overrides.js:114
MessageTray.prototype._updateNotificationTimeout@/usr/share/cinnamon/js/ui/messageTray.js:1732
MessageTray.prototype._onNotificationDestroy@/usr/share/cinnamon/js/ui/messageTray.js:1521
_emit@resource:///org/gnome/gjs/modules/signals.js:124
Notification.prototype._onDestroy@/usr/share/cinnamon/js/ui/messageTray.js:1022
Notification.prototype.destroy@/usr/share/cinnamon/js/ui/messageTray.js:1027
Source.prototype.destroyNonResidentNotifications@/usr/share/cinnamon/js/ui/messageTray.js:1199
NotificationDaemon.prototype._onFocusAppChanged@/usr/share/cinnamon/js/ui/notificationDaemon.js:532

Window manager warning: Log level 16: STACK_OP_ADD: window 0x2a05e85 already in stack
Window manager warning: Log level 16: STACK_OP_ADD: window 0x2a05e85 already in stack
Window manager warning: Log level 16: STACK_OP_ADD: window 0x2a05e82 already in stack
Window manager warning: Log level 16: STACK_OP_ADD: window 0x2a05e82 already in stack
Window manager warning: Log level 16: STACK_OP_ADD: window 0x2a05f37 already in stack
Window manager warning: Log level 16: STACK_OP_ADD: window 0x2a05f37 already in stack
Window manager warning: Log level 16: STACK_OP_ADD: window 0x2a05f34 already in stack
Window manager warning: Log level 16: STACK_OP_ADD: window 0x2a05f34 already in stack
Cjs-Message: JS LOG: Invalid or null source id used when attempting to run Mainloop.source_remove()
== Stack trace for context 0x24bbcc0 ==
overrideMainloop/Mainloop.source_remove@/usr/share/cinnamon/js/ui/overrides.js:114
MessageTray.prototype._updateNotificationTimeout@/usr/share/cinnamon/js/ui/messageTray.js:1732
MessageTray.prototype._onNotificationDestroy@/usr/share/cinnamon/js/ui/messageTray.js:1521
_emit@resource:///org/gnome/gjs/modules/signals.js:124
Notification.prototype._onDestroy@/usr/share/cinnamon/js/ui/messageTray.js:1022
Notification.prototype.destroy@/usr/share/cinnamon/js/ui/messageTray.js:1027
Source.prototype.destroyNonResidentNotifications@/usr/share/cinnamon/js/ui/messageTray.js:1199
NotificationDaemon.prototype._onFocusAppChanged@/usr/share/cinnamon/js/ui/notificationDaemon.js:532

[ProfKnowby]

Hello, I've been experiencing the same problem everyone else appears to be having. Does any of the following raise a red flag?

~ $ inxi -Fxz
System: Host: colossus Kernel: 3.13.0-24-generic i686 (32 bit, gcc: 4.8.2) Desktop: Gnome Distro: Linux Mint 17.1 Rebecca
Machine: System: Dell product: Vostro 1000
Mobo: Dell model: 0WY383 Bios: Dell version: 2.6.2 date: 10/17/2006
CPU: Single core Mobile AMD Sempron 3600+ (-UP-) cache: 256 KB flags: (lm nx sse sse2 sse3) bmips: 1600.07 clocked at 800.00 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] RS482M [Mobility Radeon Xpress 200] bus-ID: 01:05.0
X.Org: 1.15.1 drivers: ati,radeon (unloaded: fbdev,vesa) Resolution: 1280x800@59.9hz
GLX Renderer: Gallium 0.4 on ATI RS480 GLX Version: 2.1 Mesa 10.1.0 Direct Rendering: Yes
Audio: Card: Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA) driver: snd_hda_intel bus-ID: 00:14.2
Sound: Advanced Linux Sound Architecture ver: k3.13.0-24-generic
Network: Card-1: Broadcom BCM4401-B0 100Base-TX driver: b44 ver: 2.0 bus-ID: 08:00.0
IF: eth0 state: up speed: 100 Mbps duplex: full mac:
Card-2: Broadcom BCM4311 802.11b/g WLAN driver: b43-pci-bridge bus-ID: 05:00.0
IF: wlan0 state: down mac:
Drives: HDD Total Size: 120.0GB (23.6% used) 1: id: /dev/sda model: FUJITSU_MHY2120B size: 120.0GB
Partition: ID: / size: 109G used: 27G (26%) fs: ext4 ID: /boot size: 236M used: 44M (20%) fs: ext2
RAID: No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Sensors: System Temperatures: cpu: 57.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 146 Uptime: 34 min Memory: 474.1/873.7MB Runlevel: 2 Gcc sys: 4.8.2 Client: Shell inxi: 1.8.4

ClamTk, v5.15
Wed Mar 18 18:53:28 2015
ClamAV Signatures: 3772303

Found 5 possible threats (100490 files scanned).

/usr/lib/mono/4.5/mscorlib.dll PUA.Win32.Packer.PrivateExeProte-7
/usr/lib/mono/4.0/mscorlib.dll PUA.Win32.Packer.PrivateExeProte-7
/usr/lib/linuxmint/mintWifi/drivers/i386/Broadcom4318_Dell1390/bcmwl5.sys PUA.Win32.Packer.PrivateExeProte-7
/usr/lib/linuxmint/mintWifi/drivers/i386/WUSB54Gv4/rt2500usb.sys PUA.Win32.Packer.NspackDotnetNor-1
/usr/lib/linuxmint/mintWifi/drivers/i386/Dell_bcmwl5/bcmwl5.sys PUA.Win32.Packer.PrivateExeProte-7

Thanks in advance for any help that can be provided.

[cpitclaudel]

Running for about three weeks using nightly builds; the situation is much better; the freezes still happen after at least one suspend-resume cycle, and often when using a PDF reader (could it be something poppler does? This sounds weird)

[mxa]

Reliable freezes with Cinnamon 2.4.6-20150405040008-trusty nightly PPA and using scribus opening eps documents and copying & pasting them into other documents while playing back music with clementine. (heavy disk i/o). Moved to MATE, no freezes of the OS there while doing the same work.

[mtwebster]

@mxa Is it a permanent freeze? or momentary? I'm attempting to reproduce what you're describing.

Heavy text eps files? images? Is clementine playing local files?

Thanks

[mxa]

Longer then my patience, which is about a minute. EPS have text and images but are not very complex. Clementine plays local files.

Am 6. April 2015 03:03:45 GMT+09:00, schrieb Michael Webster notifications@github.com:

@mxa Is it a permanent freeze? or momentary? I'm attempting to
reproduce what you're describing.

Heavy text eps files? images? Is clementine playing local files?

Thanks

---

Reply to this email directly or view it on GitHub:
#3275 (comment)

[mtwebster]

Can you try temporarily disabling any non-system applets and extensions and reproducing? Not able to reproduce here yet.

[mxa]

I have no extensions installed.
Which ones are non-system applets?

[mxa]

With all respect, I think it is a design problem if a third party extension to the desktop is able to freeze the desktop. It may exit or quit, even become unresponsive (only the plugin) but should not be able to take the whole desktop with it.

[savuori]

I'm not sure if me using Cinnamon on Ubuntu (gwendal-lebihan-dev-ubuntu-cinnamon-nightly PPA) invalidates this but I can pretty reliably reproduce the freeze. It happens almost always if I'm switching windows and during the switch Telegram IM-app receives a message producing a notification pop-up. Everything stops except the mouse cursor, music continues playing etc. I can switch to a virtual console and kill Cinnamon which restarts but for some reason I lose sound. Haven't been able to restore it (restarting pulseaudio unloading/reloading modules).

[marben]

Interesting. I can confirm loosing sound after the freeze as well..

[matthijsmelissen]

I can also confirm losing sound after a freeze followed by killall mdm and sudo mdm.

[craigs100]

In fairness, my mouse isn't exactly standard. It's a wireless Evoluent Vertical mouse. Only cleared by them for Windows and Mac users of course, they say it defaults to normal protocols if their drivers aren't there. But I sometimes have my doubts.

[E3V3A]

I doubt this is a mouse problem, as my mouse still works for this bug. The other problems people have here, with freezes etc. must be of a different origin. This is a Cinnamon or windows manager problem! (And it doesn't look to be fixed anytime soon, since it just keep on propagating to newer releases.)

[Zerophase]

This only seems to happen to me if I open the options window for Libreoffice. Does still not reproduce the freeze?

[gerrnot]

For me this solved it: using nvidia-375 driver now, that is available in 18.1 via driver manager. The nouveau driver, that was previously recommended, seems having been the culprit.

[WendellF]

Still working for you, gerrnot? I'm having the issue on an older HP Pavilion p6230y with an H-RS880-uATX motherboard. I'm using Fedora 25. Has happened for a long time.

[maxkoryukov]

@gerrnot , nvidia-375 is heating up my PC, don't know why.. Linux Mint 18.1 Serena, Desktop: Cinnamon 3.2.7. So currently, I am on integrated Intel controller.
Btw: FAILED: nouveau

[maxkoryukov]

@WendellF Fedora 25?? As I know, it is RPM based, so there are not so much common packages (Mint is ubuntu based)

[craigs100]

@maxkoryukov I recently found my Dell M3800 running Mint 18.1 overheating. Indicated by the presence of a set of processes beginning with "k" (sorry, they're not there now and can't remember the name but was something like "kine", one for each processor). They were off loading the CPUs to protect them. Opening the machine and removing dust from heatsinks, filters and fans fixed it. It's like a new machine now, so fast. The nvidia GPU is still useless though, even with Kernel 4.10.1-20 and nvidia-381 driver. I consider the cost of the nvidia GPU to have been a total waste. It's always given inferior performance to the integrated Intel GPU so I no longer bother switching over. Nvidia should be ashamed of themselves.

[aitorbk]

The NVIDIA Quadro M4000M is a very nice CAD GPU... something wrong with the driver.

I am pretty sure the mouse is no a problem.. will probably install mint on a new late 2016 27" iMAC to see if it improves.. if not, as I cant really pinpoint the issue, I will probably switch to ubuntu.

[craigs100]

I have occasional mouse freezes. It's an Evoluent vertical wireless mouse. When it freezes, I take the USB receiver out and pop it in another USB port and it's fine. It's like the USB system gets stuck. Though I can still use my USB keyboard. Evoluent insist it's not their driver, as they don't have Linux drivers, it's relying on the default mouse driver in Mint.

[maxkoryukov]

I think, point of this thread is not a mouse pointer, but the frozen system )))

@craigs100 thanks;) but the dust is not a problem in my case, it is all clear. The problem is continuous heating by one of running processes. Will switch to NVidia again, and try to find the culprit.

[gerrnot]

The solution of my last post only worked for about 1-2 months without freezes, then they came back.

-> I am now running on driver 'NVIDIA-Linux-x86_64-381.22.run' (from nvidia website) without erros, rest is standard settings.

[imperative]

Why is this issue closed? This still happens with latest version...

[Zerophase]

@imperative My guess is it's too general. For me it was an issue with how Icing Task Manager was opening libreoffice.

[jaszhix]

@Zerophase Still occurring with ITM v6?

[Zerophase]

@jaszhix nope. I'll have to check when I get back but at worst each document opened in libreoffice has its own icon on the Taskbar.

[aitorbk]

I have traced it back to high latency from the system HDD + the swap.
I don't think it can be easily fixed, the GUI seems to have a process that has to either read or write from these devices, and stalls.

My "solution" was to add 8GB of ram, and if my system doesnt swap, all is ok. Moving the swap to a different HDD improved the problem, but did not solve it completely.

[JustinTraer]

I'm experiencing 'freezing' my Cinnamon desktop as well. My mouse point still responds, I can switch to a TTY but I can not interact with any of the windows on the desktop sometimes. Killing the cinnamon process from a TTY restores the desktop to some degree -- I can interact with my windows again but I can't switch (which is understandable as the window manager was just killed.)

When I can switch to a xterm and run 'cinnamon --replace', the desktop is back to normal.

I recently have updated the both cinnamon, the NVIDIA driver and the kernel so I feel it's one of those items causing this as this is only recently effecting me.

Cinnamon 2.8.6
NVIDIA Driver Version: 387.12
Kernel: 4.10.0-37-generic

[jonorthwash]

@JustinTraer, you can always do DISPLAY=:0.0 cinnamon --replace from the console instead of killing cinnamon and trying to restart it from within X.

[JustinTraer]

@jonorthwash , Thanks! I knew I could do something like that having done it before but the syntax of it escaped me in the moment and there was deadlines to meet.

I'll put that in a script for later use.

I've noticed that CPU usage during this 'freezes' goes up with X using most of a core and cinnamon using 20% - %30 as well.

Would the output from 'cinnamon --replace' or any other log interest anyone?

[patrickelectric]

I have 16GB of RAM and more 32GB of SWAP SSD and cinnamon is freezing, the only thing that work is the mouse that I can move around and changing from cursor to 'hand' or 'write' while moving over google-chrome. But everything else is unclickable.
I am using cinnamon and muffin 3.4.6-1.
Besides that gnome shell work without problem.
@jonorthwash DISPLAY=:0.0 cinnamon --replace do not work, it appears that a program called cinnamon-killer or something like that start and is unable to kill cinnamon.
I am having this in the last 2 weeks.

[aitorbk]

@patrickelectric I have had the same problem for the last year and a half, and found no good solution.
The problem starts when the swap begins.. I moved the swap from the SSD to a HDD and it runs better.
I can simulate the problem using 100% of HDD with high priority, cinnamon just stalls.

I still use Mint at work but I uninstalled and change distro at home, I am afraid the problem is cinnamon.

[patrickelectric]

@aitorbk Ty for reply.
How can I check that ?
Here is my log: https://paste.ee/p/zPZJe
I would like to solve this problem

[Rubenzahl]

@patrickelectric @aitorbk @mxa @JustinTraer @jonorthwash
Got the same problem. But on MATE 18.2 (Sonya). Kernel: 4.11.0-14-generic
(I had the same problem from 17.1, 17.2, 17.3, 18, 18.1 and now with 18.2. :(( - Thats why I am upgrading that much in hope to get rid of this bug.
NVIDIA driver version: 384.90
RAM: 32 GB
I am normally always resuming. (I fully reboot only once a month)

What happens: Music keeps playing, Mouse can be moved and thats it. No other consoles. No keyboard input. No caps-lock light/NUM light change - nothing. I think I tried even Sys-Rq which had no effect.

Happens once every two weeks. It happens in all circumstances thats why I think that it is not related to any user interaction. I can sit and just watch youtube tutorials while it happens. It can happen while resizing Firefox windows. It happens while writing texts in writer. It just happens. :(( After 3 to 5 min. all is back to normal again. (video will keep on playing cuz sound can still be heard - but picture freezes.

So the problem cannot be only "Cinnamon". Must be somewhat deeper. And not kernel related too. I tested so many of them. (10?) Happens now on my Gigabyte/Ryzen and happened before on ASRock/intel i5. (???)

[patrickelectric]

@Rubenzahl
My configs:
kernel: 4.13.9-1
nvidia: 387.22-3

[aitorbk]

I have made an educated guess that some processes cannot continue without reading/writing from/to the main drive. Changing the swap from the main drive to rotating media alliviated most of my problems, but not all.
I have also had this problem since 17.
I also run Ubuntu, using the same hardware, and I dont have the problem. As mint is based on ubuntu, and the original versions do not have this problem, I am inclined to thing that this is cinnamon related. It might not be the case, as music , etc also stops, but it is still highly suspect.
I also have minor problems with sound, but dont want to derail the thread.

[Fantu]

@aitorbk if avoid swapping seems a good "workaround" for you, have you tried to set to start use swap only when 99% ram is used? (default is 60%)
if not edit /etc/sysctl.conf adding this line:
vm.swappiness = 1

[aitorbk]

@Fantu yes I did try to change the swappiness, but it only makes things worse. It gets unsuable the moment it starts swapping. So better to move the swap to another drive.
Right now I have:
$ free -h
total used free shared buff/cache available
Mem: 15G 10G 2.3G 246M 2.6G 4.2G
Swap: 16G 2.6G 14G

And I have no problems whatsoever.
Now, if I grab a huge backup file and run a test of it, etc, using 100% of the SSD read or write capabilities.. the system kind of freezes. Does not happen with ubuntu.
My swap:
$ swapon --summary
Filename Type Size Used Priority
/dev/sda5 partition 17635324 2747796 -1

And my drives
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 0 223.6G 0 disk
├─sdb2 8:18 0 1K 0 part
├─sdb5 8:21 0 7.7G 0 part
└─sdb1 8:17 0 215.9G 0 part /
sdc 8:32 1 30.3G 0 disk
└─sdc1 8:33 1 30.3G 0 part /media/aitor/EAGET
sda 8:0 0 931.5G 0 disk
├─sda4 8:4 0 784.2G 0 part
├─sda2 8:2 0 129.7G 0 part
├─sda5 8:5 0 16.8G 0 part [SWAP]
├─sda3 8:3 0 619.9M 0 part
└─sda1 8:1 0 200M 0 part

[Rubenzahl]

@aitorbk
I am here on mate. Do I also have cinnamon? Cuz you said that you think that it is cinnamon related. I think I have only mate packages installed and nothings else.

I have:
$ free -h
total used free shared buff/cache available
31G 6,9G 4,5G 246M 20G 23G
Swap: 64G 4,0M 64G

So could it be the SSD forcing the system to freeze??

[aitorbk]

@Rubenzahl I think you have way to much swap.

If you have no Cinnamon and have Mate and you have the same issues.. then we should consider closing this thread, as this is marked as "Cinnamon".

[patrickelectric]

If mate and cinnamon have this issue, both need this issue open. It is related to cinnamon, occurs in cinnamon, than we need to clarify what is going on and solve it.

[aitorbk]

@patrickelectric What we probably need to do is boot in console and try to reproduce the problem, as it might be a deeper problem.

[Rubenzahl]

@aitorbk
I have this much swap just in case I will install 64 GB of RAM. And thats why I already created this big swap partition. (I love to hibernate ... ;)) But I had 32 GB Swap before with the same bug.
But maybe some points we could check to clarify that we all suffer from the same bug:

1. Do we all work with a "resumed" machine? I only reboot once a month. All other times I do just hibernate. (I heard from people who "say" that they are bug free that they have never hibernated. (?)
2. Do we all have the OS installed on a SSD?
3. Does it freeze 3 to 5 min and then you can work with the pc again as usual? (I am really happy that my PC does not really crash but is usable again normally after the freeze. So it seems to me as if there is some "wait", some "task" running in the background. (so not really a bug - but still annoying)
   It would be helpful I think to find out what we all have in common. Otherwise this bug would affect everyone which does not seem to be true.

[JustinTraer]

I think that this thread contains a few different problems. I do not support closing the thread as in my instance, restarting cinnamon, the window manager, fixes the problem. If anyone here is experiencing 'freezing' problems and your not running Cinnamon, you likely have something else going on :D

For the record, I do not use hibernate on this workstation and my OS is on rotational hard drives.

My system does not recover with out intervention.

Also, when I use different window managers on the same machine, I do not have this problem.

For those of you that have systems 'freezing', it could be many different things. One thing I have encountered on previous systems, is that a malfunctioning drive or drive controller will cause the desktop to completely freeze for various lengths of time. Sometimes these faults can be IDE/SATA cables that have gone bad or poor connections and even faulty power supplies. Sometimes you'll see messages in dmesg about this.

@aitorbk Given what you've said about utilizing 100% of your disk's IO, yes, in most cases when that happens system to become laggy. I think you might want to look into tuning your setup. Might I suggest that you look into the CFQ scheduler for your drives or maybe 'noop' for the SSD's? Also if you try the CFQ scheduler you can lower the priority for a given tasks disk IO. I've done this for some disk IO heavy tasks and it helped immensely. You'll want to look into the chrt program and launch your disk IO heavy task something like this: sudo chrt -i [...]

@Rubenzahl, I think we are experiencing different problems perhaps. Are you able to switch to a console or SSH in to your afflicted machine, kill cinnamon, and then your keyboard works again?

[Rubenzahl]

@JustinTraer
You are right. Seems that we have different problems going on. So your problem really seems to be Cinnamon related. But thanks for your info about bad "SATA drives / controllers / cabling". I will check that and report back if I found the culprit.
Next freeze I will try to ssh remotely as you proposed - but as said before - after 3 - 5 min. all is fine again. I hope I can start another machine and login this fast. :D
But I will also report back if I find smth. unnusual. The only problem with killing my mate is that I often have unsaved work running when it happens. (it is as described by Murphy's law)
Thanks for you info though!

[E3V3A]

I totally agree with @JustinTraer and @Rubenzahl . These must be different problems.

@aitorbk I use 16GB + SSD with no swap whatsoever. I have the Cinnamon problem that is resolved according to my last posts. However, using Nvidia cards does, seem to be a common denominator.

Please don't close this thread until resolved or at least migrated or split.

[aitorbk]

At work I also have an Nvidia card.. will try to check this weekend with virtual machines.

[jonorthwash]

When I had freezing issues, I was running Intel video hardware. The freezing issues were very similar to @JustinTraer describes—just restarting cinnamon was all that was needed to fix it.

Do we all work with a "resumed" machine?

I suspend a lot, but never hibernate.

Do we all have the OS installed on a SSD?

Yes

Does it freeze 3 to 5 min and then you can work with the pc again as usual?

Nope.

My current issue is that keyboard input and mouse clicks (but not mouse cursor movement) becomes sluggish after cinnamon has been running for a while (days or more). Restarting cinnamon fixes it, but it eventually gets sluggish again. This happens even with less than full memory usage and no swap usage. Hardware is the same as mentioned above.

[Danny3]

Hi guys,
I have been experiencing Cinnamon freezes with being able to move only the mouse pointer for months.
I have been using Linux Mint 18.2 Cinnamon 64bit on my Acer 6935G laptop, more detailed system info here:
https://gist.github.com/anonymous/1c1b0e104cda96d9b44a9a0337c67f09
I'm not sure if I experienced Cinnamon crashes in 18.1 too, I don't remember exactly when the crashes started to appear.
While I couldn't find the cause or a solution, I observed two things:

1. The desktop freezes almost always when I leave the laptop running doing nothing (idle) for at least 30 or 60 minutes.
   I thought the culprit might be the screensaver or whatever starts running when the laptop is idle.
   I disabled the screensaver, but is still freezing, so it's not it.
2. The desktop freezes even in live ISO mode booted from a flash drive
   I started using 18.2 Cinnamon in live ISO mode to test a script I was making without leaving permanent changes to the OS.
   It froze in live mode a lot too, so I don't think it has anything to do with the upgraded kernel, installed programs, changed setting that I have in the installed version of it.
   Anyway, this is my experience and what I observed, maybe it help someone to figure out where the problem is.
   BTW, does anyone know an alternative to CTRL + ALT + BACKSPACE that leaves the programs open in the taskbar still open so I don't lose unsaved work?

[jonorthwash]

BTW, does anyone know an alternative to CTRL + ALT + BACKSPACE that leaves the programs open in the taskbar still open so I don't lose unsaved work?

Read up the thread, @Danny3. Try DISPLAY=:0.0 cinnamon --replace.

[patrickelectric]

`DISPLAY=:0.0 cinnamon --replace` Do not work with me. 2017-11-07 18:19 GMT-02:00 Jonathan Washington <notifications@github.com>:

…

BTW, does anyone know an alternative to CTRL + ALT + BACKSPACE that leaves the programs open in the taskbar still open so I don't lose unsaved work? Read up the thread, @Danny3 <https://github.com/danny3>. Try DISPLAY=:0.0 cinnamon --replace. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3275 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABKMCQQpxO3oRxVTanf9203GlZ1iX6Waks5s0LthgaJpZM4CE1IU> .

-- Patrick José Pereira Electronics Engineer Skype: patrickelectric434 IRC: patrickelectric +55 (048) 99917-4777

[jaszhix]

If Cinnamon is completely frozen and you're using lightdm, you can try switching to another tty, kill the cinnamon process, and then switch back - I've only tested this with Mate installed, but it will switch to mate-panel and should give you an option to restart Cinnamon. Before with MDM as the login manager, this didn't work and would kill the entire user session.

[jonorthwash]

DISPLAY=:0.0 cinnamon --replace Do not work with me.

@patrickelectric What result do you get? Does cinnamon restart or not, does it output any potentially useful debugging info, what happens when you switch back to X?

[patrickelectric]

The command do not return, that a program called cinnamon-killer appears in htop. It's necessary to kill cinnamon-session, than gdm restart and I can login again. If I choice cinnamon after the first crash, it will always crash after login, only a system reset solve the problem or login to gnome shell. 2017-11-08 0:03 GMT-02:00 Jonathan Washington <notifications@github.com>:

…

DISPLAY=:0.0 cinnamon --replace Do not work with me. @patrickelectric <https://github.com/patrickelectric> What result do you get? Does cinnamon restart or not, does it output any potentially useful debugging info, what happens when you switch back to X? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3275 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABKMCYE75859UpozZYtBzkiqD9LgV_3yks5s0QwDgaJpZM4CE1IU> .

-- Patrick José Pereira Electronics Engineer Skype: patrickelectric434 IRC: patrickelectric +55 (048) 99917-4777 <(48)%2099917-4777>

[JustinTraer]

@patrickelectric The command will not return. Here's what to do once this freeze happens:

Press CRTL-ALT-F1

Log in!

Once you are at the prompt type this ( or save it as a bash script now, and just run the script later)

env DISPLAY=:0 XAUTHORITY=~/.Xauthority cinnamon --replace

Switch back to the desktop with: CTRL-ALT-F7

If you know how to use screen, or tmux, then by all means, throw that in the mix too. If you don't know about those two programs, don't worry and check them out some time.

[JustinTraer]

So, I have had another lock up from cinnamon yesterday - the first one in perhaps two weeks.

What I noticed this time, was that the the 'lockup' coincided with opening a link to imgur from a coworker in Hangouts. Focused switched to Chrome and the system began thrashing (possibly heavy swapping).

RAM usage by cinnamon shot up to nearly 800MB, the chrome, cinnamon, and X servers where using alot of CPU.

The imgur page has Adchoices ads in it.

Killing all my chrome/chromium windows brought the system back to a state where it should have been stable but cinnamon was still exhibiting the aforementioned behavior.

Once I restarted cinnamon (with the --replace from a TTY), every thing was good. And other then what might have been in any web apps at the time, I didn't lose any work either.

Please note,I'm say this is not the same as my system thrashing and becoming unresponsive due to a badly programmed app or heavy thrashing (high swapping in/out rather then just having an app swapped out). If my system was only thrashing, I'd expect killing the offending app, or being patient on the desktop (or both) would resolve the issue.

I'm beginning to suspect that the ads in Chrome and Chromium are kicking off a chain reaction. My theory is that they somehow causing more window manager events and cinnamon is not coping well with that.

Once I'm in this state, the mouse cursor moves, I can not switch focus, and the hot corners no longer work. Usually Chrome/Chromium still work for a bit.. Youtube will stop eventually, but I noticed this last time that the ads in imgur kept on running fine adding to my suspicion of them.

I typically use imgur with out a problem, so it's not like it is the first time I've been on that site either.

[jaszhix]

Try installing the uBlock Origin extension in Chrome, and white list the sites you trust, or want to support.

Cinnamon freezing can be caused by extensions, it may help diagnose the issue if you list the output of these commands:

gsettings get org.cinnamon enabled-applets
gsettings get org.cinnamon enabled-desklets
gsettings get org.cinnamon enabled-extensions

[patrickelectric]

@JustinTraer I'll try that in the next freeze.

[egloffmark]

I have the same problem, but I recognize this issue since I upgraded my system from 18.0 to 18.2. And I don't use Chrome as Browser it was also not running in the background. Only Firefox was opened and a ssh session at this time. I had this issue already 5 times since my upgrade to 18.2.

restarting cinnamon with the key combinations CTRL +ALT + ESC or BACKSPACE helped as a workaround

• I am using SSD drive
• Kernel v 4.8.0-58-generic
• Hardware Lenovo 900 yoga with Intel graphic card

May be it is related to some applets on the taskbar? i.e. window list / manager

I executed the commands this is the output

megloff@YOGA-900 ~ $ gsettings get org.cinnamon enabled-applets
['panel1:left:0:menu@cinnamon.org:0', 'panel1:left:1:show-desktop@cinnamon.org:1', 'panel1:left:2:panel-launchers@cinnamon.org:48', 'panel1:left:3:windowlist@cobinja.de:79', 'panel1:right:0:notifications@cinnamon.org:4', 'panel1:right:3:removable-drives@cinnamon.org:6', 'panel1:right:4:keyboard@cinnamon.org:7', 'panel1:right:6:sound@cinnamon.org:10', 'panel1:right:7:power@cinnamon.org:11', 'panel1:right:8:systray@cinnamon.org:12', 'panel1:right:9:network@cinnamon.org:9', 'panel1:right:10:calendar@cinnamon.org:13', 'panel2:left:0:menu@cinnamon.org:49', 'panel2:left:1:show-desktop@cinnamon.org:50', 'panel2:left:2:panel-launchers@cinnamon.org:63', 'panel2:left:4:windowlist@cobinja.de:80', 'panel2:left:3:spacer@cinnamon.org:82', 'panel2:right:0:notifications@cinnamon.org:51', 'panel2:right:0:spacer@cinnamon.org:81', 'panel2:right:2:user@cinnamon.org:52', 'panel2:right:3:removable-drives@cinnamon.org:53', 'panel2:right:4:keyboard@cinnamon.org:54', 'panel2:right:6:sound@cinnamon.org:56', 'panel2:right:7:power@cinnamon.org:57', 'panel2:right:8:systray@cinnamon.org:58', 'panel2:right:9:network@cinnamon.org:55', 'panel2:right:10:calendar@cinnamon.org:59']
megloff@YOGA-900 ~ $ gsettings get org.cinnamon enabled-desklets
@as []
megloff@YOGA-900 ~ $ gsettings get org.cinnamon enabled-extensions
@as []

[E3V3A]

FWIW. I also noticed that my cinnamon issues, usually seem to occur when I am (or have been) copy/pasting to/from Firefox to/from terminal or elsewhere. (Note that Chrome is code similar to FF.) This is also true for running Mint in a Windows VM. BTW. If you are using a laptop and have an Nvidia card, you usually also have another Intel card built-in on the mobo.

Could this be a copy/clipboard buffer issue? Given all the available system logs, could someone tell us what logs would be helpful to collect? (And how to obtain them.)

@jaszhix You say "Cinnamon freezing can be caused by extensions". Is this a fact or theory? If fact, please explain how this happens.

[patrickelectric]

Ok, this do not work.. Em 08/11/2017 17:37, "JustinTraer" <notifications@github.com> escreveu:

…

@patrickelectric <https://github.com/patrickelectric> The command will not return. Here's what to do once this freeze happens: Press CRTL-ALT-F1 Log in! Once you are at the prompt type this ( or save it as a bash script now, and just run the script later) env DISPLAY=:0 XAUTHORITY=~/.Xauthority cinnamon --replace Switch back to the desktop with: CTRL-ALT-F7 If you know how to use screen, or tmux, then by all means, throw that in the mix too. If you don't know about those two programs, don't worry and check them out some time. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3275 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABKMCW2F2K9ls-hF3kbjaGDo2jhMBc1Pks5s0gL8gaJpZM4CE1IU> .

[jaszhix]

The extensions have access to all the same APIs that Cinnamon itself is using, which are bindings to the C libraries, which can cause a lot of problems in some cases. In any case, if I were running into this issue, I would first check ~/.xsession-errors or the output of cinnamon --replace, ~/.cinnamon/glass.log, and dmesg. If no errors are seen there, I would disable all the third party extensions.

If there's a segfault from Cinnamon reported in dmesg, then installing debug symbols (cinnamon-dbg) and running Cinnamon with gdb would be a good idea. There's a script in utils/ called cin-debug. You can clone the repo and call it with ./cin-debug cinnamon in the folder.

[jonorthwash]

Ok, this do not work..

@patrickelectric What result do you get? Does cinnamon restart or not, does it output any potentially useful debugging info, what happens when you switch back to X?

[patrickelectric]

@jaszhix I don't have a ~/.xsession-errors file.
glass.log here.
dmesg log here

If there's a segfault from Cinnamon reported in dmesg, then installing debug symbols (cinnamon-dbg) and running Cinnamon with gdb would be a good idea. There's a script in utils/ called cin-debug. You can clone the repo and call it with ./cin-debug cinnamon in the folder.
I'll try that in the next time.

@jonorthwash, same thing that I said in my comment.
When running the env DISPLAY=:0 XAUTHORITY=~/.Xauthority cinnamon --replace OF @JustinTraer, it give some Gtk-WARNING messages about theme parsing error
and a cinnamon warning about the adwaita theme. That's the same thing when running cinnamon --replace

[jaszhix]

@patrickelectric I don't see any Cinnamon segfaults, but chrome and pulseaudio. It looks like gnome shell and cinnamon are running at the same time?

`
Nov 02 11:27:54 dell kernel: chrome[20855]: segfault at 968 ip 00007fc3dac68393 sp 00007ffedac1a180 error 4 in libX11.so.6.3.0[7fc3dac3b000+139000]

Nov 02 11:27:59 dell kernel: pulseaudio[20862]: segfault at 38 ip 00007f0b8e2b9e20 sp 00007fff114871d8 error 4 in libasound.so.2.0.0[7f0b8e275000+e7000]
...
Nov 02 11:34:06 dell gnome-shell[22774]: Some code accessed the property 'STATUS_INDICATORS_SETTING_KEY' on the module 'settings'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Nov 02 11:34:06 dell gnome-shell[22774]: Some code accessed the property 'ESCoffGIconSel' on the module 'convenience'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Nov 02 11:34:06 dell upowerd[724]: energy 41.997600 bigger than full 39.421200
Nov 02 11:34:14 dell gvfsd[14885]: Error 2: PTP Layer error 02ff: Error getting friendlyname.
Nov 02 11:34:14 dell gvfsd[14885]: Error 2: Error 02ff: PTP I/O Error
Nov 02 11:34:14 dell systemd-logind[494]: Removed session c12.
...
Nov 02 11:34:48 dell kernel: INFO: task cinnamon:22468 blocked for more than 120 seconds.
Nov 02 11:34:48 dell kernel: Tainted: G O 4.13.9-1-ARCH #1
Nov 02 11:34:48 dell kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 02 11:34:48 dell kernel: cinnamon D 0 22468 1 0x00000004
`

You'll have to get the output that would be in xsession_errors from cinnamon --replace. Unless someone knows another way, I don't use GDM. Since Shell and Cinnamon are based on the same stack for the most part, but with different versions, it wouldn't surprise me if having both installed is causing problems.

[pwil3058]

This system doesn't seem to like me attaching these files and says that they're too big to just put in a comment,

[pwil3058]

I'm not deliberately running gdm and have no idea how it got started. In fact, according to dnf I don't have the gdm packages installed. Using ps seems to indicate that this program is being started/stopped by another program as the PID keeps changing (disregard that remark it's the pid of my ps|grep that I'm looking at. gdm isn't running at all as far as I can see.

[leigh123linux]

@patrickelectric Try editing

https://wiki.archlinux.org/index.php/GDM#Use_Xorg_backend

Personally I would dump the GDM crapware as it lies

GDM claims it's ready to start X

Nov 02 11:28:41 dell /usr/lib/gdm/gdm-x-session[21310]: localuser:patrick being added to access control list
Nov 02 11:28:41 dell /usr/lib/gdm/gdm-x-session[21310]: /etc/gdm/Xsession: Setup done, will execute: cinnamon-session-cinnamon

But clearly it hasn't finished!

Nov 02 11:28:42 dell /usr/lib/gdm/gdm-x-session[21310]: (II) modeset(0): EDID vendor "CMN", prod id 5600
Nov 02 11:28:42 dell /usr/lib/gdm/gdm-x-session[21310]: (II) modeset(0): Printing DDC gathered Modelines:
Nov 02 11:28:42 dell /usr/lib/gdm/gdm-x-session[21310]: (II) modeset(0): Modeline "1920x1080"x0.0  152.84  1920 2000 2054 2250  1080 1086 1094 1132 +hsync -vsync (67.9 kHz eP)
Nov 02 11:28:42 dell /usr/lib/gdm/gdm-x-session[21310]: (II) modeset(0): Modeline "1920x1080"x0.0  122.27  1920 2000 2054 2250  1080 1086 1094 1132 +hsync -vsync (54.3 kHz e)
Nov 02 11:28:42 dell /usr/lib/gdm/gdm-x-session[21310]: (II) modeset(0): EDID vendor "CMN", prod id 5600
Nov 02 11:28:42 dell /usr/lib/gdm/gdm-x-session[21310]: (II) modeset(0): Printing DDC gathered Modelines:
Nov 02 11:28:42 dell /usr/lib/gdm/gdm-x-session[21310]: (II) modeset(0): Modeline "1920x1080"x0.0  152.84  1920 2000 2054 2250  1080 1086 1094 1132 +hsync -vsync (67.9 kHz eP)
Nov 02 11:28:42 dell /usr/lib/gdm/gdm-x-session[21310]: (II) modeset(0): Modeline "1920x1080"x0.0  122.27  1920 2000 2054 2250  1080 1086 1094 1132 +hsync -vsync (54.3 kHz e)

[thoslin]

I got froze in the screensaver for couple times today, only mouse can move, unable to get into the system. I'm using Linux Mint 18.2 Cinnamon 64-bit. Cinnamon version is 3.4.6. And Kernel version is 4.10.0-38-generic.

There are some errors in ~/.xsession-errors. Please check out here https://pastebin.com/TTvxKG5q

[Bobavince]

Hi !

Arch with Cinnamon, freezing problem too.
Freezing time : 1 second to 30 seconds.
No SDD, just hard drive.
Nvidia card.

It seems to be related to Network manager for me (as for example, when my Wifi shutdown for one reason or another, the screen and not the mouse, freeze during seconds) but I did not found any solution (more than a year now)