[BUG] Mint 17: Nemo: When trying to browse Windows Network, Nemo crashes 100% of time

I have experienced this behavior on two separate computers and while running the Live CD. I open Nemo, click on Networks in the left menu. Then I double click on Windows Network to browse it and Nemo completely crashes, taking all the desktop icons along with it. When I open Nemo again, the desktop icons come back and the same behavior of crashing when trying to open the Windows Network occurs. I can successfully access Windows network shares by going directly to the address in Nemo (smb://192.168.1.10/Share).

There are others who experience this. Others have tried Dolphin or another file explorer and they don't have the problem. Something is wrong with Nemo. On Mint 15, I did not have this issue.

[leigh123linux]

Can you reproduce the issue using nautilus file manager?

It is not installed. I will install it and try. Others have said they use something else such as Dolphin and that they can browse the network fine. Nemo used to work just fine but not now.

Ok, I ran nautilus and it gave me a "Segmentation Fault" when I tried to browse the Windows Network. I could directly connect to an smb:// share. Running Nemo also gives the "Segmentation Fault"

looking in /var/log/syslog I see this for Nemo:
Jun 6 23:53:19 Computer kernel: [ 483.222998] nemo[2998]: segfault at 0 ip 00000000004ealff sp 00007fff6f974b40 error 4 in nemo[400000+1aa000]

The Nautilus segfault shows this:
kernel: [ 179.122827] nautilus[2803]: segfault at 0 ip 00000000004befda sp 00007fff9e5ab080 error 4 in nautilus[400000+152000]

This same issue has been identified before with no solution.

#340

Can someone please address this? Mint is trying to take over the Linux OS and Windows XP scene and this dumb bug can't be bothered to be addressed?

[mtwebster]

Can you do the following:

sudo apt-get install gdb nemo-dbg

gdb nemo
run
...... do things to make nemo crash ....
thread apply all bt

And paste the output of that last command?

[mtwebster]

Cannot reproduce this in Mint 17. I can browse via networks to a Windows Network, and view folders there.

[queeup]

I'm seeing the same behavior in Mint 17 x64. Fresh install. Both my desktop and laptop have this issue.

But It crashes when I double click WORKGROUP directory on Network>Windows Network.

@mtwebster
This was my output. The crash happened at the segfault line. All I did was double-click on the Windows Network icon.

(gdb) run
Starting program: /usr/bin/nemo 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffed854700 (LWP 21885)]
[New Thread 0x7fffed053700 (LWP 21886)]
[New Thread 0x7fffec852700 (LWP 21887)]
[New Thread 0x7fffe7fff700 (LWP 21888)]
[New Thread 0x7fffe73ef700 (LWP 21889)]
[New Thread 0x7fffe4820700 (LWP 21891)]
[New Thread 0x7fffcda8c700 (LWP 21893)]
[Thread 0x7fffec852700 (LWP 21887) exited]
[Thread 0x7fffcda8c700 (LWP 21893) exited]
[Thread 0x7fffed053700 (LWP 21886) exited]

Program received signal SIGSEGV, Segmentation fault.
compare_by_display_name (file_1=0xcb8b40, file_2=0xcb8e80) at nemo-file.c:2892
2892    nemo-file.c: No such file or directory.
(gdb) thread apply all bt

Thread 7 (Thread 0x7fffe4820700 (LWP 21891)):
#0  0x00007ffff45997ce in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/x86_64-linux-gnu/libpthread.so.0
#1  0x00007ffff50afcf5 in g_cond_wait_until ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ffff50441c1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffff504474b in g_async_queue_timeout_pop ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007ffff5093966 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007ffff5092f15 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007ffff4595182 in start_thread ()
   from /lib/x86_64-linux-gnu/libpthread.so.0
#7  0x00007ffff42c230d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 6 (Thread 0x7fffe73ef700 (LWP 21889)):
#0  0x00007ffff42b4fbd in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007ffff506dfe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ffff506e0ec in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffff506e129 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007ffff5092f15 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007ffff4595182 in start_thread ()
---Type <return> to continue, or q <return> to quit---

[mtwebster]

@gaetawoo that helps some, but could you do again and hit until you get output of all threads? You only got thread 7 and part of 6 there (I should have mentioned this, sorry)

I'm suspecting there's a file or folder in your guys' windows shares that Nemo can't figure out. This initial trace points to a simple filename comparison function for sorting the files in the views.

Do any of your folders (particularly the one you're clicking on that crashes Nemo) have any strange characters in their name? Would you mind listing the files for me? (feel free to filter out personal stuff).

[queeup]