Linux Mint 17.3 Cinnamon crashes on first mouse move

[radi8]

After upgrading from Linux Mint 17.2 to LM 17.3, cinnamon crashes on the first movement of the mouse. I also downloaded the iso and installed to a memory stick. Using this to boot gave the same problem. Linux Mint runs fine on fallback mode and when I try to restart cinnamon I get the following message ...

gvj@gvj-Mint ~ $ cinnamon --replace Cjs-Message: JS LOG: About to start Cinnamon St-Message: cogl npot texture sizes SUPPORTED Cjs-Message: JS LOG: Cinnamon started at Thu Dec 10 2015 11:44:23 GMT+1300 (NZDT) Cjs-Message: JS LOG: network applet: Cannot find connection for active (or connection cannot be read) Cjs-Message: JS LOG: network applet: Found connection for active Window manager warning: Log level 6: The program 'cinnamon' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 4593 error_code 8 request_code 134 (SYNC) minor_code 16) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/breakpoint trap gvj@gvj-Mint ~ $

I strongly suspect the NVIDIA drivers are involved and have tried to use the following drivers ... driver : nvidia-304 - distro non-free recommended driver : nvidia-173 - distro non-free driver : nvidia-304-updates - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin

The 304 and 304 updates drivers give the fault described while the nouveau driver freezes the whole machine and I have to hardware reset it.

The severity of the bug is that I can only use Linux Mint in fallback mode but all software seems to run OK. The problem always happens either from the HDD upgrade install or from the memory stick run software.

My system information is as described below ...

gvj@gvj-Mint ~/Desktop $ inxi -Fxz System: Host: gvj-Mint Kernel: 3.16.0-38-generic x86_64 (64 bit gcc: 4.8.2) Desktop: Cinnamon 2.8.6 (Gtk 3.10.8~8+qiana) Distro: Linux Mint 17.3 Rosa Machine: Mobo: ASUSTeK model: M2N68-AM Plus v: Rev X.0x Bios: American Megatrends v: 0708 date: 06/29/2009 CPU: Dual core AMD Athlon II X2 240 (-MCP-) cache: 2048 KB flags: (lm nx sse sse2 sse3 sse4a svm) bmips: 11250 clock speeds: max: 2812 MHz 1: 2812 MHz 2: 2812 MHz Graphics: Card: NVIDIA C61 [GeForce 7025 / nForce 630a] bus-ID: 00:0d.0 Display Server: X.Org 1.15.1 drivers: nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 1920x1080@60.0hz GLX Renderer: GeForce 7025 / n clock speeds: max: 2812 MHz 1: 2812 MHz 2: 2812 MHzForce 630a/integrated/SSE2 GLX Version: 2.1.2 NVIDIA 304.131 Direct Rendering: Yes Audio: Card NVIDIA MCP61 High Definition Audio driver: snd_hda_intel bus-ID: 00:05.0 Sound: Advanced Linux Sound Architecture v: k3.16.0-38-generic Network: Card: NVIDIA MCP61 Ethernet driver: forcedeth port: e480 bus-ID: 00:07.0 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: Drives: HDD Total Size: 500.1GB (35.2% used) ID-1: /dev/sda model: WDC_WD5000AADS size: 500.1GB Partition: ID-1: / size: 455G used: 161G (38%) fs: ext4 dev: /dev/dm-0 ID-2: /boot size: 236M used: 48M (22%) fs: ext2 dev: /dev/sda1 ID-3: swap-1 size: 4.16GB used: 0.00GB (0%) fs: swap dev: /dev/dm-1 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 47.0C mobo: 35.0C gpu: 0.0: Fan Speeds (in rpm): cpu: 2576 Info: Processes: 166 Uptime: 1:10 Memory: 901.5/3827.0MB Init: Upstart runlevel: 2 Gcc sys: 4.8.4 Client: Shell (bash 4.3.111) inxi: 2.2.28

gvj@gvj-Mint ~/Desktop $ uname -a Linux gvj-Mint 3.16.0-38-generic #52~14.04.1-Ubuntu SMP Fri May 8 09:43:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux gvj@gvj-Mint ~/Desktop $

[gergelyv]

Exactly the same problem with my Nvidia Geforce GO 2300 after upgrading from Linux Mint 17.2 to 17.3, cinnamon keeps crashing:

$gevo@lm17 ~/Schreibtisch $ cinnamon --replace Cjs-Message: JS LOG: About to start Cinnamon St-Message: cogl npot texture sizes SUPPORTED Cjs-Message: JS LOG: Cinnamon started at Thu Dec 17 2015 10:54:01 GMT+0100 (CET) Cjs-Message: JS LOG: network applet: Cannot find connection for active (or connection cannot be read) Cjs-Message: JS LOG: network applet: Found connection for active Window manager warning: Log level 6: The program 'cinnamon' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 2762 error_code 8 request_code 134 (SYNC) minor_code 16) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/Breakpoint ausgelöst gevo@lm17 ~/Schreibtisch $

gevo@lm17 ~/Schreibtisch $ inxi -Fxz System: Host: lm17 Kernel: 3.19.0-32-generic i686 (32 bit gcc: 4.8.2) Desktop: Cinnamon 2.8.6 (Gtk 3.10.8~8+qiana) Distro: Linux Mint 17.3 Rosa Machine: Mobo: ASUSTeK model: A6JC v: 1.0 Bios: American Megatrends v: A6JCMAS.220 date: 10/04/2006 CPU: Dual core Intel Core2 T5500 (-MCP-) cache: 2048 KB flags: (lm nx pae sse sse2 sse3 ssse3) bmips: 6650 clock speeds: max: 1667 MHz 1: 1328 MHz 2: 1328 MHz Graphics: Card: NVIDIA G72M [Quadro NVS 110M/GeForce Go 7300] bus-ID: 01:00.0 Display Server: X.Org 1.15.1 driver: nvidia Resolution: 1280x800@60.0hz GLX Renderer: GeForce Go 7300/PCIe/SSE2 GLX Version: 2.1.2 NVIDIA 304.131 Direct Rendering: Yes Audio: Card Intel NM10/ICH7 Family High Definition Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 Sound: Advanced Linux Sound Architecture v: k3.19.0-32-generic Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 v: 2.3LK-NAPI port: c800 bus-ID: 02:00.0 IF: eth0 state: up speed: 100 Mbps duplex: full mac: Card-2: Intel PRO/Wireless 3945ABG [Golan] Network Connection driver: iwl3945 v: in-tree:s bus-ID: 03:00.0 IF: wlan0 state: down mac: Drives: HDD Total Size: 250.1GB (3.9% used) ID-1: /dev/sda model: WDC_WD2500BEVE size: 250.1GB Partition: ID-1: / size: 45G used: 7.8G (19%) fs: ext4 dev: /dev/sda9 ID-2: swap-1 size: 1.45GB used: 0.00GB (0%) fs: swap dev: /dev/sda7 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 65.0C mobo: N/A gpu: 0.0:57C Fan Speeds (in rpm): cpu: N/A Info: Processes: 153 Uptime: 21 min Memory: 272.7/2015.1MB Init: Upstart runlevel: 2 Gcc sys: 4.8.4 Client: Shell (bash 4.3.111) inxi: 2.2.28

gevo@lm17 ~/Schreibtisch $ uname -a Linux lm17 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 09:37:25 UTC 2015 i686 i686 i686 GNU/Linux gevo@lm17 ~/Schreibtisch

[clefebvre]

Can we get a stack trace?

[radi8]

Hi Clement,

Firstly thanks for the magnificent distro which has been amazingly bug free for me so far. Congratulations to you and the team.

I have never done a stack trace before so I hope this is what you need. I used "strace cinnamon |& tee ~/Desktop/cinnamon.txt" as the command to capture the stack. If you have something else which would be better please advise.

cinnamon_Nouveau.txt ... This file is using the Nouveau drivers with the Nvidia drivers purged. Cinnamon largely works like this but sometimes crashes particularly when opening firefox or thunderbird. It was working OK at the time of this stack trace.

cinnamon_After.txt ... This file was captured immediately after Cinnamon crashed. I had re-installed the Nvidia drivers here.

cinnamon.txt ... This file was an attempt to capture the stack as Cinnamon crashed and is likely to have the most useful information. Also with the Nvidia drivers.

cinnamon.txt cinnamon_After.txt cinnamon_Nouveau.txt

[palerail]

Worked around by dumping mdm and using lightdm and Mate.

[radi8]

Without removing Cinnamon, I have installed Mate and everything runs perfectly with this.

[hitekagpilot]

Clement.. I would like to echo what Radi8 said about such an excellent distro. I have been running LM since 12 (I think). Anyhow. I would like to add some possibly useful information to this conversation that may be of some help.

My workstation is running a fresh install of 17.3 on an Asus Z-97A mobo, Intel I7-4790k, PCIe SSD, Sata SSD and Sata 1 TB drive. I have had to revert to using the on-board intel graphics due to the nouveau driver (and NVIDIA driver for that matter) lock-up issue. I run 3 monitors (#1 Landscape, #2 Landscape and #3 Portrait). Using the built-in intel video this works without a hitch. I have tried the following 3 NVIDIA video cards using the Nouveau and the Nvidia drivers with the same Cinnamon lockup glitch : 9500GT, GT620 and GTS450.

The odd part of the glitch is.. I routinely run a Win7 workstation on VBox for windows related work. I had the Cinnamon window manager lockup (no mouse, no screen refresh of the VBox and no screen refresh from the Host OS. However, I was running a VOIP phone (in the VM) and was on a call during this and that continued to operate until I finished the call and had to 'hard reset' the CPU.

I have not tried any other desktops but I can and see if the issue follows or not - from the previous posts I suspect they will not. I usually Run LM with the Cinnamon or XFCE desktop - never been a MATE fan but I will give it a shot in the essence of troubleshooting.

If there are any particular configurations you would like me to test.. let me know. I will be AFK 1/2-1/5 as I will be travelling but I will get back to this upon my return.

HiTekAgPilot

[radi8]

Mate has been running perfectly for the last 4 days and outwardly there seems to be very little difference between Mate and Cinnamon. I am quite happy to stay with Mate for as long as it takes to fix Cinnamon but happy to revert at any time for further testing.

[colpanek]

Same problem, upgrade from 17.2. MATE works great. Using NVidia304.131 driver.

[benchrest]

Same here. I have it on a test machine I use to verify my applications work before updating my #1 machine. So I would be able to test a fix without much trouble. Just let me know what I can do. This is a big deal.

[uncles-a-m]

Same here on an old Lenovo 3000 N200. Using the NVidia 304 driver, Cinnamon crashes after the first action. With the nouveau driver, the system somehow "freezes" randomly. (I tried to boot with "nomodeset", as suggested by the release notes, but the problems does still occur.) One can still move the mouse, but the desktop doesn't respond anymore. Also Alt-F2, Ctrl-At-Esc, Ctrl-Alt-End or Ctrl-Alt-F3 etc. don't work. The only way is a hard reset.

With the xfce-desktop, both drivers work flawlessly. (I installed xfce as a temporary "solution".)

Any news on this issue?

Unfortunately, I cannot post any log, since this is not my machine and I don't have it here now.

[radi8]

Yes uncles-a-m it is exactly the problem. I am surprised that the bug has not been upgraded to critical and had someone assigned to it as in my opinion any bug which only makes upgrading safe on certain machines and completely brings the computer down is critical. The only work around I can discover is to use an alternative desktop as you are doing. In my case I am using Mate.

[briangmaddox]

For what it's worth, I'd like to chime in that I have this issue also. Linux Mint 17.3 Cinnamon running on a Dell E1705 with an NVidia G71M [GeForce Go 7900 GS] [10DE:298] with the nvidia-304 304.131-0ubuntu0.14.04.1 drivers. I get random graphics glitches where the desktop flashes. Coming back from a suspend the graphics are all corrupt and I have to reboot to fix them. Switching to a text VT and back to the GUI has no effect. I installed MATE and it works flawlessly on my E1705.

My work laptop is a new Dell running a current NVidia card with the 352 drivers and Cinnamon works flawlessly on it. Suspend/resume works fine. No random glitches or flashes on it. This also leads me to believe it's an issue with Cinnamon and the 304 drivers. I also hope this gets assigned soon since I hope it is fixed before Mint 18 comes out.

[benchrest]

As I mentioned earlier, my older (2007) HP laptop with Nivida graphics has the problem. My newer (2013) desktops use ASUS EN210 graphics with Nvidia 210 engine. Am I right to be gun shy to upgrade them from 17.2 to 17.3 Cinnamon?

[colpanek]

My 2011 HP laptop doesn't even reliably run Cinnamon on 17.2, so I'm sitting tight on 17.2 MATE until 18 comes along. Then... we'll see.

Col. Panek

On Thu, Jan 7, 2016 at 11:43 PM, benchrest notifications@github.com wrote:

As I mentioned earlier, my older (2007) HP laptop with Nivida graphics has the problem. My newer (2013) desktops use ASUS EN210 graphics with Nvidia 210 engine. Am I right to be gun shy to upgrade them from 17.2 to 17.3 Cinnamon?

— Reply to this email directly or view it on GitHub https://github.com/linuxmint/Cinnamon/issues/4932#issuecomment-169895971 .

[mtwebster]

I've tested this on nvidia hardware and unfortunately haven't been able to reproduce yet:

Graphics:  Card: NVIDIA GK106 [GeForce GTX 660]
           Display Server: X.Org 1.15.1 drivers: nvidia (unloaded: fbdev,vesa,nouveau)
           Resolution: 1920x1080@60.0hz
           GLX Renderer: GeForce GTX 660/PCIe/SSE2 GLX Version: 4.2.0 NVIDIA 304.131

I'd like to catch some debugging info on this if possible from affected users -

The following will install necessary debug packages, as well as a small script that automates information-gathering for us to a degree.

sudo apt-get install cinnamon-dbg
wget https://raw.githubusercontent.com/linuxmint/Cinnamon/master/utils/cin-debug
chmod a+x ./cin-debug

What cin-debug does is attaches a debugger to a process, waits until it crashes, then gets a back trace, saving all of this to a file in your home folder.

The trick in this case is going to be running it without causing cinnamon to crash.

the usage is: ./cin-debug cinnamon &

This will request your sudo password (required for attaching to a running process). The & (ampersand) will allow the process to run in the background - you can probably omit that in this case.

I'm not sure what actions you can get away with that won't cause the crash. If you can open a terminal with a hotkey (ctrl-alt-t by default), try to, and run the script, then allow cinnamon to crash. You could also run it from a tty screen (ctrl-alt-f2 for instance) or from a ssh session from another pc or smart device.

The resulting log file should end up in your home folder as cinnamon-xxxx.log with a time/date stamp. Paste that to dpaste.com or pastebin.com and link it here.

Once you're done with the tool, I'd recommend a reboot (it makes zombies occasionally).

Hopefully this will get us some more info on this issue.

Thanks!

[radi8]

Hi Michael,

Thanks for looking at this problem. I have just spent a very frustrating evening trying to get a back trace for you but there seems to be no way to run cin-debug before cinnamon crashes. I get time to open a terminal but no time to enter anything. When it goes to fallback mode the terminal is still open so I tried entering cin-debug cinnamon & and then restarting cinnamon. I have tried both responding yes to the restart message and typing cinnamon --replace in a terminal. I also tried running cin-debug and then ctl-alt F2 and startx but no luck i.e. cinnamon started and crashed. I looked for cin-debug with ps but don't think it runs when started with gnome because it can't find cinnamon and cinnamon does not last long enough to start it.

I wondered if it was a combination of cinnamon and something else like virtual box but I don't think that is the case because I downloaded the latest iso and put it on a usb stick and it crashes too with I guess the vanilla nouveaux drivers. If you can't reproduce the bug and I can't get a back trace, I think it is going to be very tricky to find the bug. I hope some of the other guys with the problem may be able to get a trace for you. Of course I am yours to command for any other testing but unfortunately my Linux knowledge is a bit light. Thanks for what you have done so far.

Cheers, Graeme

[clefebvre]

Tested here as well:

Mint 17.3 Cinnamon 2.8.4 and 2.8.6. nvidia 304.131 (also tested nvidia-updates-304, even though it's the same version) GeForce 9400

Works fine, no crash.

It looks like the issue isn't specific to the driver itself but to a generation of NVIDIA chipsets. I've also got a 9500GT and a 8300GS, I'll test that last one.

I don't have any older card to test the GeForce 7xxx series though (and it looks like it's the one that fails).

[clefebvre]

OK, here we go. I managed to set up a box with this:

Mint 17.3 Cinnamon 2.8 NVIDIA 304.131 GeForce 8300GS

MDM loads fine (so X seems to be ok), but after logging in the Cinnamon session, I see the mouse pointer being centered (that's part of the init() sequence for Cinnamon) and then boom... black screen and I'm back to MDM with no open session.

Installed openbox and could open a session that way.

"cinnamon --replace" in a terminal --> no visible output, black screen, I guess X dies and back to MDM.

installed muffin also... "muffin --replace" in a terminal -> same result -> back to MDM.

[clefebvre]

Sorry, it turned out to be a separate issue. I brought muffin back all the way to version 2.5.0 and experienced the same issue... so it's not related to this particular bug.

I'm afraid I'm not able to reproduce it then.

[benchrest]

I have been trying most of the morning to get a trace with no success. I get two slightly different symptoms whether I run nvidia-304 or nvidia-304-updates. both give this crash. Starting the system and doing nothing it just sits there fat and sasy. With nvidia-304-updates I can move the mouse but not to the panel or it crashes. I cannot select anything without a crash. Doing a ctrl-alt-t brings up the terminal window along with the crash. I can start tty with ctrl-alt-f2 and run the command. It give several messages that it cannot find files. Not sure if it started or not. But then I cannot get back to cinnamon. (I know nothing of tty). With nividia-304 I can move the mouse. But with this version I can put it on the panel. But if I select a program such as firefox a long pause occurs and then firefox starts with the crash. cntl-alt-f2 does not crash but the terminal window is hidden. I can tell this by moving the mouse. When I am outside the window I see the cursor arrow. When I am in the window a vertical bar. So I tried entering the command to start the debug and before I got 1/2 entered it crashed. I installed cin-debug using mate.

My HP laptop list the graphics card as Nvidia GeForce Go 7150M

sudo lshw -C video

   description: VGA compatible controller
   product: C67 [GeForce 7150M / nForce 630M]
   vendor: NVIDIA Corporation
   physical id: 12
   bus info: pci@0000:00:12.0
   version: a2
   width: 64 bits
   clock: 66MHz
   capabilities: pm msi vga_controller bus_master cap_list rom
   configuration: driver=nvidia latency=0
   resources: irq:16 memory:f6000000-f6ffffff memory:d0000000-dfffffff memory:f3000000-f3ffffff memory:80000000-8001ffff

Cinnamon just crashed. You are currently running in fallback mode. Do you want to restart Cinnamon?

cinnamon --replace Cjs-Message: JS LOG: About to start Cinnamon St-Message: cogl npot texture sizes SUPPORTED Cjs-Message: JS LOG: Cinnamon started at Tue Jan 12 2016 12:31:36 GMT-0600 (CST) Cjs-Message: JS LOG: network applet: Cannot find connection for active (or connection cannot be read) Cjs-Message: JS LOG: network applet: Found connection for active Window manager warning: Log level 6: The program 'cinnamon' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 2941 error_code 8 request_code 134 (SYNC) minor_code 16) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/breakpoint trap

[radi8]

Benchrest gets exactly the same results as me even though the card seems to be a newer model.

My video info ... sudo lshw -C video

*-display
description: VGA compatible controller product: C61 [GeForce 7025 / nForce 630a] vendor: NVIDIA Corporation physical id: d bus info: pci@0000:00:0d.0 version: a2 width: 64 bits clock: 66MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:21 memory:de000000-deffffff memory:c0000000-cfffffff memory:dd000000-ddffffff memory:dffc0000-dffdffff

I would be prepared to remove my mother board and ship it to whoever is working on the fix if it would help. I have another old box I can get going in the meantime.

[briangmaddox]

Hey mtwebster, the link is http://pastebin.com/HG1xrFnq. It'll consistently crash and come back in Fallback mode if I run anything like supertux or other such apps in full screen. I'm also pasting other info here if it helps. Please let me know if I can do anything else: bmaddox@sdf1:~$ sudo lshw -C video *-display
description: VGA compatible controller product: G71M [GeForce Go 7900 GS] vendor: NVIDIA Corporation physical id: 0 bus info: pci@0000:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:16 memory:ed000000-edffffff memory:d0000000-dfffffff memory:ee000000-eeffffff ioport:ef00(size=128) memory:efe00000-efe1ffff bmaddox@sdf1:~$

bmaddox@sdf1:~$ cat /proc/driver/nvidia/version NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 4.9.3 (Ubuntu 4.9.3-8ubuntu2~14.04) bmaddox@sdf1:~$

[colpanek]

I'm running a 6 year old eMachines, driver 304.131

description: VGA compatible controller product: C61 [GeForce 6150SE nForce 430] vendor: NVIDIA Corporation physical id: d bus info: pci@0000:00:0d.0 version: a2 width: 64 bits clock: 66MHz capabilities: pm msi vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:22 memory:de000000-deffffff memory:c0000000-cfffffff memory:dd000000-ddffffff memory:dff40000-dff5ffff

[mtwebster]

Can you guys also pastebin the following:

/var/log/Xorg.0.log
~/.xsession-errors (if you haven't yet)

It's important that you copy these immediately after reproducing the crash (do it from tty is probably simplest) - if you grab them after logging back onto another desktop, they'll have been overwritten.

Thanks again. Hopefully we can take some steps moving forward to make this sort of data collection easier for users (or even automatic in some way).

[colpanek]

OK, here's my Xorg.0.log cinnamon-crash-jimvandamme.txt

[radi8]

My Xorg.0.log as gvj.txt My ~/.xsession-errors as gvj1.txt gvj.txt gvj1.txt

[briangmaddox]

Just triggered another crash. Nothing was in my .xsession-errors. My new Xorg.log and cin-debug dump are at: http://pastebin.com/sCUzAwBQ - Xorg http://pastebin.com/SeFU6urM - new cindebug log.

This time a crash to fallback mode was triggered by switching between VT1 and 8 to start cindebug.

[omeletteo]

I have a similar problem. Nvidia 304.131 driver. Cinnamon crashes if I even move the mouse pointer over a desktop icon. Tried installing the Cinnamon debug packages but encounter a different set of problems - unmet dependencies, starting with gnome-dbg. As with the others, Mate runs perfectly. Forgot to add, it's a Dell laptop with a GeForce 7400 chipset.

[benchrest]

Looking at the forums we are not the only ones with this bug. I am willing to help if I can, have a laptop sitting idle I can test with. Will someone be assigned? Is this problem only effecting those using Nvidia 304 driver? Do those using a newer Nvidia driver safe? My desktops use Nvidia 340 driver. Should they be safe if upgraded?

[omeletteo]

I am wondering how many people affected by this are using 32-bit hardware? There are two major (imo) bugs with Mint where the only systems affected are 32-bit ones. My theory is that the Mint packages are being built with 64-bit compilers, and the '32-bit switch' doesn't work quite as intended. I have just posted about this Mint problem at https://bugs.launchpad.net/linuxmint/+bug/1468794

[briangmaddox]

64 bit here.

On 01/20/2016 12:20 PM, omeletteo wrote:

I am wondering how many people affected by this are using 32-bit hardware? There are two major (imo) bugs with Mint where the only systems affected are 32-bit ones. My theory is that the Mint packages are being built with 64-bit compilers, and the '32-bit switch' doesn't work quite as intended. I have just posted about this Mint problem at https://bugs.launchpad.net/linuxmint/+bug/1468794

— Reply to this email directly or view it on GitHub https://github.com/linuxmint/Cinnamon/issues/4932#issuecomment-173282876.

[briangmaddox]

Hey guys, added in another .xsession at http://pastebin.com/NtJpGEqz after I had a few issues today (not crashes, just graphics flashes). Also just got this as I was posting this and had several flickers: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x320008d (*xsession )

[omeletteo]

Aww well, that quashes that theory. Good to know though.

[briangmaddox]

Hey guys, here's another .xsession from today where I've had a lot of odd graphics flashes and what not. Looks like a lot of nemo errors. Hopefully this will help somehow. BTW, nothing shows up in syslog or Xorg.log, even when Cinnamon crashes to fallback mode.

http://pastebin.com/2UpkijiL

[briangmaddox]

Hey guys, sorry but here's another .xsession-errors. I'm noticing that the odd screen flashes are more prone to occur when I also fire up a KDE app lik choqok or kpatience. The crashes are always consistent when I run something like supertux2 in full screen.

http://pastebin.com/yfv8yCCe

[uncles-a-m]

Sorry for the late commit. I had no access to the machine up to now.

Info about the graphic-card: http://pastebin.com/Dx94Xnj0

Xorg.0.log: http://pastebin.com/XqMCrcNP

xsession-errors: http://pastebin.com/zWMVFUFj

I hope, this is somehow helpful.

[kc1di]

I have this problem with 6150se card as well, only with Cinnamon. Sorry for comming in late on this one , I no longer have cinnamon installed on this machine. xfce, mate and kde work perfectly with the 304.xx driver. cinnamon Crashes immediately upon signin. Sorry can't be of more help. But wanted to let you know that it's not just a 7xxxx series issue.

[mtwebster]

Hi guys - I've made a set of packages for muffin I'd like you to try (be sure to pick the right architecture):

64-bit:

https://dl.dropboxusercontent.com/u/8201170/muffin/64bit-no-frame-sync/gir1.2-muffin-3.0_2.8.4_amd64.deb https://dl.dropboxusercontent.com/u/8201170/muffin/64bit-no-frame-sync/libmuffin0_2.8.4_amd64.deb https://dl.dropboxusercontent.com/u/8201170/muffin/64bit-no-frame-sync/muffin_2.8.4_amd64.deb https://dl.dropboxusercontent.com/u/8201170/muffin/64bit-no-frame-sync/muffin-common_2.8.4_all.deb https://dl.dropboxusercontent.com/u/8201170/muffin/64bit-no-frame-sync/muffin-dbg_2.8.4_amd64.deb

32-bit:

https://dl.dropboxusercontent.com/u/8201170/muffin/32bit-no-frame-sync/gir1.2-muffin-3.0_2.8.4_i386.deb https://dl.dropboxusercontent.com/u/8201170/muffin/32bit-no-frame-sync/libmuffin0_2.8.4_i386.deb https://dl.dropboxusercontent.com/u/8201170/muffin/32bit-no-frame-sync/muffin_2.8.4_i386.deb https://dl.dropboxusercontent.com/u/8201170/muffin/32bit-no-frame-sync/muffin-common_2.8.4_all.deb https://dl.dropboxusercontent.com/u/8201170/muffin/32bit-no-frame-sync/muffin-dbg_2.8.4_i386.deb

Download all the files to the same folder (save as, don't use the deb installer), then in a terminal in that folder: sudo dpkg -i *.deb

Then reboot or log out/back in to Cinnamon. This is a bit of a blind test for now, as we're still attempting to reproduce this, but we have some hunches, and this will confirm or dispel them. I'm working on getting the correct hardware to reproduce this in the meantime.

Thanks for your patience.

_NOTE:_\ The update manager will want to reinstall the current release version of these packages - if you happen to blindly update, just reinstall these debs again. Otherwise, skip muffin updates or add them to your ignore list temporarily.

[briangmaddox]

I'm incredibly happy to report that this appears to have fixed my issues! Before when I would fire up something like Supertux2 or a PlayonLinux game in full screen, it would crash and go to fall back mode. Now both work and nothing crashes. So far so good that I also haven't had the odd graphics "flashing" that I had too where parts of the screen would oddly distort briefly. I'll keep banging on it today to see if it happens again. Thanks so much for working on this for us though!

On 01/30/2016 09:11 AM, Michael Webster wrote:

Hi guys - I've made a set of packages for muffin I'd like you to try (64 bit):

https://dl.dropboxusercontent.com/u/8201170/muffin/64bit-no-frame-sync/gir1.2-muffin-3.0_2.8.4_amd64.deb https://dl.dropboxusercontent.com/u/8201170/muffin/64bit-no-frame-sync/libmuffin0_2.8.4_amd64.deb https://dl.dropboxusercontent.com/u/8201170/muffin/64bit-no-frame-sync/muffin_2.8.4_amd64.deb https://dl.dropboxusercontent.com/u/8201170/muffin/64bit-no-frame-sync/muffin-common_2.8.4_all.deb https://dl.dropboxusercontent.com/u/8201170/muffin/64bit-no-frame-sync/muffin-dbg_2.8.4_amd64.deb

Download all the files to the same folder (save as, don't use the deb installer), then in a terminal in that folder: |sudo dpkg -i *.deb|

Then reboot or log out/back in to Cinnamon. This is a bit of a blind test for now, as we're still attempting to reproduce this, but we have some hunches, and this will confirm or dispel them. I'm working on getting the correct hardware to reproduce this in the meantime.

Thanks for your patience.

PS I'll build some 32 bit packages later.

— Reply to this email directly or view it on GitHub https://github.com/linuxmint/Cinnamon/issues/4932#issuecomment-177189225.

[briangmaddox]

Another comment, noticed suspend and resume works for me now as well.

On 01/30/2016 09:11 AM, Michael Webster wrote:

Hi guys - I've made a set of packages for muffin I'd like you to try (64 bit):

https://dl.dropboxusercontent.com/u/8201170/muffin/64bit-no-frame-sync/gir1.2-muffin-3.0_2.8.4_amd64.deb https://dl.dropboxusercontent.com/u/8201170/muffin/64bit-no-frame-sync/libmuffin0_2.8.4_amd64.deb https://dl.dropboxusercontent.com/u/8201170/muffin/64bit-no-frame-sync/muffin_2.8.4_amd64.deb https://dl.dropboxusercontent.com/u/8201170/muffin/64bit-no-frame-sync/muffin-common_2.8.4_all.deb https://dl.dropboxusercontent.com/u/8201170/muffin/64bit-no-frame-sync/muffin-dbg_2.8.4_amd64.deb

Download all the files to the same folder (save as, don't use the deb installer), then in a terminal in that folder: |sudo dpkg -i *.deb|

Then reboot or log out/back in to Cinnamon. This is a bit of a blind test for now, as we're still attempting to reproduce this, but we have some hunches, and this will confirm or dispel them. I'm working on getting the correct hardware to reproduce this in the meantime.

Thanks for your patience.

PS I'll build some 32 bit packages later.

— Reply to this email directly or view it on GitHub https://github.com/linuxmint/Cinnamon/issues/4932#issuecomment-177189225.

[xpansiv]

Hi guys,

I also had this problem after upgrading to 17.3 (GeForce Go 7300 with 304.131 driver, Cinnamon was going to fallback mode right after logging in). After installing the files posted by mtwebster, Cinnamon has been running smoothly on my system for the last 4 hours.

I'll keep testing it but it looks like your hunches were well-aimed!

[radi8]

Hi Michael,

Your patches are working brilliantly here now. I guessed you were beavering away quietly on the issue and one day you would have something for us to try. Thank you so much for your effort and this is looking really good.

My 32 bit machine (Dell E1505) works fine with Cinnamon but it is not using nvidea drivers so sorry but can't do any testing there.

Thanks again Michael, you have made my day.

Best wishes, Graeme

[briangmaddox]

So I've been banging on this all day and still no crashes. Suspend works. The full screen games work. So far so good. Haven't had any random graphics glitches since I reenabled vsync on opengl after putting the test .debs on (I had disabled it before while testing to see if it had any effect).

On 01/30/2016 05:08 PM, Graeme wrote:

Hi Michael,

Your patches are working brilliantly here now. I guessed you were beavering away quietly on the issue and one day you would have something for us to try. Thank you so much for your effort and this is looking really good.

My 32 bit machine (Dell E1505) works fine with Cinnamon but it is not using nvidea drivers so sorry but can't do any testing there.

Thanks again Michael, you have made my day.

Best wishes, Graeme

— Reply to this email directly or view it on GitHub https://github.com/linuxmint/Cinnamon/issues/4932#issuecomment-177317688.

[mtwebster]

Added 32-bit packages, and a note on upgrading to this post: https://github.com/linuxmint/Cinnamon/issues/4932#issuecomment-177189225

Good to hear we've narrowed the problem down a bit, and some of you are operational again.

[radi8]

There is a LinuxMint upgrade for muffin. I wonder if I should apply that or leave it until you are properly finished? [ Michael Webster ]

• meta-window-actor.c: Remove duplicate call to meta_window_get_input_rect()

[dralley]

@radi8 Don't update. Mint will always recognize the repository-provided copy of a package as being versioned higher than a non-repository copy of a package if they have the same version number. Updating would replace your functional Muffin with the broken one :)

[mtwebster]

@radi8 See the note I added to the end of my post with the .deb packages - the update manager will want to replace these with the repository versions. Either de-select any muffin updates when updating, or just be sure to re-install these packages immediately after.

[benchrest]

I'll join the chorus, your patch is working so far. I could never get more than a second or two before.

[sg2923]

I am a complete newbie in Linux so I could not really help with logs. Now I installed your patch (32 bit) and it works perfect. I have a NVIDIA G72M GeForce Go 7400 with nvidia-304-updates driver (304.131).

Thanks for your efforts!

[sg2923]

I still have one Laptop running fine on cinnamon Rafaela - without any fix. The context Menu there displays less entries than on the one on cinnamon Rosa with fix. I quess this just depends which programs you have installed and the kind of file etc. But on both I don't have anything like "make link". I run Linux in German but still... To give you a more precise answer I need more detailed informations: What kind of file did you choose? You can send me a screenshot if you like.

I can't imagine it's caused by the patch but you never now.

Am 03.02.2016 um 03:16 schrieb benchrest:

Question, maybe non-related. I have two computers running 17.3 cinnamon. One has the temporary fix. Using Nemo 2.8.6, the one with the patch does not display the full context menu when I right click on a file and I do not get the option to "make link". The other computer does. I have been comparing Nemo preferences and see no difference. About to pull out my hair on such a trivial problem. Could this be caused by the patch? If so I will just wait. I can find no other difference.

— Reply to this email directly or view it on GitHub https://github.com/linuxmint/Cinnamon/issues/4932#issuecomment-178959923.