Viewing mounted network share after losing network crashes nautilus

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

 If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

 If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

 If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.
 I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

apport fails to report the bug with the following error:

"The problem cannot be reported:

The program crashed on an assertion failure, but the message could not be retrieved. Apport does not support reporting these crashes."

I have attached the .crash file.

Could you get a stracktrace using gdb?

Below is a stacktrace as requested. I don't have the debug symbols, so I'm not sure how useful it is. If you can point me to the packages with debug symbols or whatever else is required to get them I will do so.

Program received signal SIGABRT, Aborted.
0x003b2422 in __kernel_vsyscall ()
(gdb) bt
#0 0x003b2422 in __kernel_vsyscall ()
#1 0x01c95641 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2 0x01c98a72 in *__GI_abort () at abort.c:92
#3 0x00a0d133 in g_assertion_message () from /lib/libglib-2.0.so.0
#4 0x00a0d78d in g_assertion_message_expr () from /lib/libglib-2.0.so.0
#5 0x08127172 in ?? ()
#6 0x08127c29 in ?? ()
#7 0x080a3c72 in ?? ()
#8 0x080fd205 in ?? ()
#9 0x08101824 in ?? ()
#10 0x009e36c1 in ?? () from /lib/libglib-2.0.so.0
#11 0x009e5645 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#12 0x009e9338 in ?? () from /lib/libglib-2.0.so.0
#13 0x009e9877 in g_main_loop_run () from /lib/libglib-2.0.so.0
#14 0x010f0299 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#15 0x08080e08 in ?? ()
#16 0x01c81bd6 in __libc_start_main (main=0x8080700, argc=1, ubp_av=0xbf9be464, init=0x81a9030, fini=0x81a9020,
    rtld_fini=0xf540c0 <_dl_fini>, stack_end=0xbf9be45c) at libc-start.c:226
#17 0x0806c6b1 in ?? ()

Here's a better st with debug symbols for nautilus:

Program received signal SIGABRT, Aborted.
0x0019c422 in __kernel_vsyscall ()
(gdb) bt
#0 0x0019c422 in __kernel_vsyscall ()
#1 0x06081641 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#2 0x06084a72 in *__GI_abort () at abort.c:92
#3 0x00726133 in g_assertion_message () from /lib/libglib-2.0.so.0
#4 0x0072678d in g_assertion_message_expr () from /lib/libglib-2.0.so.0
#5 0x08127172 in nautilus_file_get_internal (location=0x0, create=1) at nautilus-file.c:657
#6 0x08127c29 in nautilus_file_get (location=0x0) at nautilus-file.c:709
#7 0x080a3c72 in got_file_info_for_view_selection_callback (file=0x952a9c8, callback_data=0x94dd318)
    at nautilus-window-manage-views.c:1177
#8 0x080fd205 in ready_callback_call (directory=0x9524350, callback=<value optimized out>) at nautilus-directory-async.c:1304
#9 0x08101824 in call_ready_callbacks_at_idle (callback_data=0x9524350) at nautilus-directory-async.c:1886
#10 0x006fc6c1 in ?? () from /lib/libglib-2.0.so.0
#11 0x006fe645 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#12 0x00702338 in ?? () from /lib/libglib-2.0.so.0
#13 0x00702877 in g_main_loop_run () from /lib/libglib-2.0.so.0
#14 0x00e38299 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#15 0x08080e08 in main (argc=1, argv=0xbfa6a1c4) at nautilus-main.c:583