Nemo Crash Desktop Icons Disappear

rageone · 2015-12-15 09:17:42

I have successfully been using cinnamon since I installed arch over a month ago. During that time I noticed that occasionally my desktop icons would disappear. I ignored it at first because I could not identify exactly what action caused it, when it actually happened, or how it fixed itself. Recently my desktop icons disappear more frequently and I was able to identify what action was causing it. Anytime that I use nemo to navigate to a nested folder more than one folder deeper than my home folder (/home/user/anyfolder), and then close nemo, my desktop icons disappear. When I launch nemo again, they re-appear. I have spent 48 hours trying everything I can find on google, the mint forums, and these forums to no avail. Specifically:

https://bugs.launchpad.net/linuxmint/+bug/1349271
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785486
http://forums.linuxmint.com/viewtopic.php?f=208&t=117974&start=40
http://forums.linuxmint.com/viewtopic.php?f=208&t=187349&p=909469#p909469
http://forums.linuxmint.com/viewtopic.php?f=208&t=154122
http://forums.linuxmint.com/viewtopic.php?f=90&t=200965

I have uninstalled nautilus, changed dconf-editor settings to every imaginable configuration, reset all cinnamon settings, removed cinnamon/nemo settings from .config and .cinnamon, etc. I am really at my wits end. The only relevant logs or output about this error I can find is from dmesg -T which reports at the end of the list:

nemo[758]: segfault at c7 ip 0000000000494984 sp 00007ffe5c2780c8 error 6 in nemo[400000+1c2000]

Any help and/or commiseration would be greatly appreciated.

severach · 2015-12-16 08:53:23

Good sleuthing. You can get that segfault easier by launching nemo from a terminal.

I tried installing as many Cinnamon AUR packages as I could but the disappearing desktop icons stayed the same and other aspects got worse.

My simple solution, a link to Thunar until it gets figured out.

sbsbs15 · 2015-12-17 03:14:03

I reported it on nemo's github (https://github.com/linuxmint/nemo/issues/1047).

Trying to replicate it in linux mint (with same version of nemo) I can confirm that this issue only happens in Arch Linux.

eschwartz · 2015-12-17 18:14:09

Nemo runs in the background (`nemo -n`) to manage the desktop. Running `nemo -q` will cause the desktop icons to disappear.
I assume when it segfaults it kills off the background process as well?

But I cannot get nemo to segfault on me by following your instructions... sorry...

sbsbs15 · 2015-12-18 00:07:51

Eschwartz wrote:

Nemo runs in the background (`nemo -n`) to manage the desktop. Running `nemo -q` will cause the desktop icons to disappear.
I assume when it segfaults it kills off the background process as well?
But I cannot get nemo to segfault on me by following your instructions... sorry...

version? I get the segfault on two different machines with nemo 2.8.6-1

eschwartz · 2015-12-18 03:54:44

Daily `yaourt -Syua`

+

[eschwartz@arch ~]$  yaourt -Q nemo
community/nemo 2.8.6-1

+

have rebooted since the last `yaourt -Syua`

...

So It's probably more than just Cinnamon+nemo+Arch, is all I am saying.

Matt3o · 2015-12-30 08:38:51

I confirm this issue. It's not just that the icons disappear, nemo simply crashes a lot. I get that every time I navigate to a sub dir and open a new tab. As soon as I open the tab, nemo dies.

systemd-coredump[20487]: Process 9499 (nemo) of user 1000 dumped core.
                                               
                                               Stack trace of thread 9499:
                                               #0  0x0000000000494984 n/a (nemo)
                                               #1  0x00007f3b47e5e015 g_closure_invoke (libgobject-2.0.so.0)
                                               #2  0x00007f3b47e70061 n/a (libgobject-2.0.so.0)
                                               #3  0x00007f3b47e78dfc g_signal_emit_valist (libgobject-2.0.so.0)
                                               #4  0x00007f3b47e7912f g_signal_emit (libgobject-2.0.so.0)
                                               #5  0x00007f3b49a2c3da n/a (libgtk-3.so.0)
                                               #6  0x00007f3b47e647b8 g_object_run_dispose (libgobject-2.0.so.0)
                                               #7  0x00007f3b497a46e0 n/a (libgtk-3.so.0)
                                               #8  0x00007f3b497a4692 n/a (libgtk-3.so.0)
                                               #9  0x00007f3b497a4692 n/a (libgtk-3.so.0)
                                               #10 0x00007f3b497a4692 n/a (libgtk-3.so.0)
                                               #11 0x00007f3b497a5495 n/a (libgtk-3.so.0)
                                               #12 0x00007f3b494282c8 n/a (libgdk-3.so.0)
                                               #13 0x00007f3b47b89c7a g_main_context_dispatch (libglib-2.0.so.0)
                                               #14 0x00007f3b47b8a020 n/a (libglib-2.0.so.0)
                                               #15 0x00007f3b47b8a0cc g_main_context_iteration (libglib-2.0.so.0)
                                               #16 0x00007f3b481498ec g_application_run (libgio-2.0.so.0)
                                               #17 0x0000000000430806 n/a (nemo)
                                               #18 0x00007f3b46d23610 __libc_start_main (libc.so.6)
                                               #19 0x0000000000430869 n/a (nemo)
                                               
                                               Stack trace of thread 9502:
                                               #0  0x00007f3b46de318d poll (libc.so.6)
                                               #1  0x00007f3b47b89fbc n/a (libglib-2.0.so.0)
                                               #2  0x00007f3b47b8a0cc g_main_context_iteration (libglib-2.0.so.0)
                                               #3  0x00007f3b47b8a109 n/a (libglib-2.0.so.0)
                                               #4  0x00007f3b47bb0715 n/a (libglib-2.0.so.0)
                                               #5  0x00007f3b470ae464 start_thread (libpthread.so.0)
                                               #6  0x00007f3b46dec13d __clone (libc.so.6)
                                               
                                               Stack trace of thread 9505:
                                               #0  0x00007f3b46de318d poll (libc.so.6)
                                               #1  0x00007f3b47b89fbc n/a (libglib-2.0.so.0)
                                               #2  0x00007f3b47b8a0cc g_main_context_iteration (libglib-2.0.so.0)
                                               #3  0x00007f3b3a3c725d n/a (libdconfsettings.so)
                                               #4  0x00007f3b47bb0715 n/a (libglib-2.0.so.0)
                                               #5  0x00007f3b470ae464 start_thread (libpthread.so.0)
                                               #6  0x00007f3b46dec13d __clone (libc.so.6)
                                               
                                               Stack trace of thread 9503:
                                               #0  0x00007f3b46de318d poll (libc.so.6)
                                               #1  0x00007f3b47b89fbc n/a (libglib-2.0.so.0)
                                               #2  0x00007f3b47b8a342 g_main_loop_run (libglib-2.0.so.0)
                                               #3  0x00007f3b48180236 n/a (libgio-2.0.so.0)
                                               #4  0x00007f3b47bb0715 n/a (libglib-2.0.so.0)
                                               #5  0x00007f3b470ae464 start_thread (libpthread.so.0)
                                               #6  0x00007f3b46dec13d __clone (libc.so.6)

rlees85 · 2015-12-31 11:59:02

Just thought I'd add my interest to this too. Nemo is core dumping a LOT (which is a shame as I've had this setup over a year with no issues). I cannot figure out what is doing it, it seems totally random. Just more and more often....

Just did a simple test. Changing view then closing always kills nemo. Sure hope this gets fixed soon, good work on those who managed to dig deeper with this issue though

Last edited by rlees85 (2015-12-31 12:00:09)

severach · 2015-12-31 19:31:57

I install Manjaro-Cinnamon, nemo crashes. I install Antergos-Cinnamon, nemo doesn't crash. Antergos uses the exact same package versions so I know it's not that. It's a config setting.

Antergos has some custom themes so I adjust in Arch until they are close to Antergos. Arch nemo still crashes.

I use startx instead of a DM so it's easy for me to exit and restart the DE. Test renaming folders shows that these aren't the problem: ~/{.cache,.cinnamon,.config}. Renaming ~/.local eliminates the crash.

Test renaming inside .local leads to the following command that solves the nemo crash.

rm -rf ~/.local/share/gvfs-metadata

Nemo runs without crashing until eventually this gets created again.

My problem where ejected removable media immediately remount has disappeared too.

Matt3o · 2016-01-05 14:42:03

tried to remove ~/.local/share/gvfs-metadata but still no dice...

esonn · 2016-01-05 15:25:00

Can confirm this issue, nemo 2.8.6-1. Matt3o, your trick works for me (at least for some time).

If it happens, I can always reproduce it when accessing a local USB3 disk (encrypted with dm-crypt), opening any random folder from USB root, and pressing Ctrl+t.

It also tends to happen very often when working with CIFS-mounted directories, so gvfs (or gvfs handling by nemo) may indeed play a vital role here.

Nemo says:

(nemo:19137): GLib-GObject-WARNING **: gsignal.c:2634: instance '0x2eced90' has no handler with id '30658'
Segmentation fault (core dumped)

Here are screenshots of GDB on a breakpoint immediately before the crash, and after the crash.

ltrace finishes with:

g_direct_hash(0x27bb890, 0x27bb890, 0, 2)                    = 0x27bb890
g_direct_hash(0x277c1d0, 0x277c1d0, 113, 6)                  = 0x277c1d0
g_direct_hash(0x277c1d0, 0x277c1d0, 0x277c1d0, 0x277c1d0)    = 0x277c1d0
g_cclosure_marshal_VOID__VOID(0x27ebc70, 0, 1, 0x7fffc9628850 <unfinished ...>
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++

esonn · 2016-01-06 13:31:25

On a closer look, the segmentation fault seems to always happen in nemo-view.c at about line 6654:

static void
on_menu_destroyed (GtkWidget *widget, NemoView *view)
{
    view->details->menu_widget_ref = NULL;
    view->details->expander_label_widget = NULL;
}

Commenting those two lines and recompiling gets rid of the segfaults. Nemo works for me without crashes, but I really didn't check for any kind of side effects (I'm neither into the code base nor GTK development).

It's most probably a very bad idea to do, honestly. However, I had no single crash ever since - will use as-is until a real fix is coming.

When building nemo with ABS, here's a patch for the nemo PKGBUILD (note that it also updates pkgrel, not sure if you want this):

--- xx/PKGBUILD	2016-01-06 14:23:20.079759921 +0100
+++ PKGBUILD	2016-01-06 14:23:03.333068437 +0100
@@ -1,10 +1,6 @@
-# $Id: PKGBUILD 153219 2015-12-14 04:41:33Z bgyorgy $
-# Maintainer: Alexandre Filgueira <alexfilgueira@cinnarch.com>
-# Contributor: Ner0
-
 pkgname=nemo
 pkgver=2.8.6
-pkgrel=1
+pkgrel=2
 pkgdesc="Cinnamon file manager (Nautilus fork)"
 arch=('i686' 'x86_64')
 url="https://github.com/linuxmint/nemo"
@@ -25,6 +21,10 @@
 
   # Rename 'Files' app name to avoid having the same as nautilus
   sed -i 's/^Name\(.*\)=.*/Name\1=Nemo/' data/nemo.desktop.in.in
+
+  # XXX HACK: comment lines which cause segfaults on 2.8.6
+  sed -i 's/(view->details->menu_widget_ref = NULL)/\/\/\0/' src/nemo-view.c
+  sed -i 's/(view->details->expander_label_widget = NULL)/\/\/\0/' src/nemo-view.c
 }
 
 build() {

An x86_64 build is avaliable at https://dl.delta-xi.net/nemo-2.8.6-2-x86_64.pkg.tar.xz

Last edited by esonn (2016-01-06 13:47:01)

Matt3o · 2016-01-06 13:59:53

looking at the code the only bad thing that could happen without those lines is some memory leak. did you notice increased memory usage over time?

esonn · 2016-01-06 15:03:48

That was my guess too. Well, I've been working with that build for several hours actively and did not notice a mentionable increase; no long-term experience though. Will monitor the next few days.

esonn · 2016-01-06 15:15:12

Issue should now be fixed in upstream commit fb97b62, see closed issue https://github.com/linuxmint/nemo/issues/1010 - let's wait for package updates.

Last edited by esonn (2016-01-06 15:25:18)

Matt3o · 2016-01-31 09:14:52

I've seen a nemo update today but it seems it is still crashing.

Matt3o · 2016-03-16 11:56:33

nemo 2.8.7-1 seems to have fixed this

Arch Linux

#1 2015-12-15 09:17:42

Nemo Crash Desktop Icons Disappear

#2 2015-12-16 08:53:23

Re: Nemo Crash Desktop Icons Disappear

#3 2015-12-17 03:14:03

Re: Nemo Crash Desktop Icons Disappear

#4 2015-12-17 18:14:09

Re: Nemo Crash Desktop Icons Disappear

#5 2015-12-18 00:07:51

Re: Nemo Crash Desktop Icons Disappear

#6 2015-12-18 03:54:44

Re: Nemo Crash Desktop Icons Disappear

#7 2015-12-30 08:38:51

Re: Nemo Crash Desktop Icons Disappear

#8 2015-12-31 11:59:02

Re: Nemo Crash Desktop Icons Disappear

#9 2015-12-31 19:31:57

Re: Nemo Crash Desktop Icons Disappear

#10 2016-01-05 14:42:03

Re: Nemo Crash Desktop Icons Disappear

#11 2016-01-05 15:25:00

Re: Nemo Crash Desktop Icons Disappear

#12 2016-01-06 13:31:25

Re: Nemo Crash Desktop Icons Disappear

#13 2016-01-06 13:59:53

Re: Nemo Crash Desktop Icons Disappear

#14 2016-01-06 15:03:48

Re: Nemo Crash Desktop Icons Disappear

#15 2016-01-06 15:15:12

Re: Nemo Crash Desktop Icons Disappear

#16 2016-01-31 09:14:52

Re: Nemo Crash Desktop Icons Disappear

#17 2016-03-16 11:56:33

Re: Nemo Crash Desktop Icons Disappear

Board footer