After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 759175 - sigsegv in nautilus_list_model_is_empty
sigsegv in nautilus_list_model_is_empty
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: Cut Copy Paste Undo
3.18.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-12-08 12:59 UTC by Sebastien Bacher
Modified: 2016-01-07 09:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastien Bacher 2015-12-08 12:59:51 UTC 
The bug was reported against nautilus 3.18.2 in the ubuntu error tracker
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1523909

It looks similar to https://bugzilla.redhat.com/show_bug.cgi?id=1277625 which was closed as fixed in 3.18.2 but seems there are still users having the issue there

"#0  nautilus_list_model_is_empty (model=0x0) at nautilus-list-model.c:962
No locals.

+ Trace 235797

  • #1 nautilus_files_view_is_empty
    at nautilus-files-view.c line 765
  • #2 real_update_actions_state
    at nautilus-files-view.c line 6418
  • #3 nautilus_files_view_update_toolbar_menus
    at nautilus-files-view.c line 6752
  • #4 done_loading
    at nautilus-files-view.c line 3137
  • #5 done_loading
    at nautilus-files-view.c line 7142
  • #6 nautilus_files_view_stop_loading
    at nautilus-files-view.c line 7236
  • #7 nautilus_files_view_destroy
    at nautilus-files-view.c line 2828
  • #8 g_closure_invoke
    at /build/glib2.0-IfQpAv/glib2.0-2.47.3/./gobject/gclosure.c line 804
  • #9 signal_emit_unlocked_R
    at /build/glib2.0-IfQpAv/glib2.0-2.47.3/./gobject/gsignal.c line 3745
  • #10 g_signal_emit_valist
    at /build/glib2.0-IfQpAv/glib2.0-2.47.3/./gobject/gsignal.c line 3385
  • #11 g_signal_emit
    at /build/glib2.0-IfQpAv/glib2.0-2.47.3/./gobject/gsignal.c line 3441
  • #12 gtk_widget_dispose
    at /build/gtk+3.0-JTuwRW/gtk+3.0-3.18.5/./gtk/gtkwidget.c line 12010
  • #13 g_object_run_dispose
    at /build/glib2.0-IfQpAv/glib2.0-2.47.3/./gobject/gobject.c line 1082
  • #14 gtk_widget_destroy
    at /build/gtk+3.0-JTuwRW/gtk+3.0-3.18.5/./gtk/gtkwidget.c line 4656
  • #15 nautilus_window_slot_dispose
    at nautilus-window-slot.c line 2402
  • #16 g_object_unref
    at /build/glib2.0-IfQpAv/glib2.0-2.47.3/./gobject/gobject.c line 3146
  • #17 gtk_container_remove
    at /build/gtk+3.0-JTuwRW/gtk+3.0-3.18.5/./gtk/gtkcontainer.c line 1900
  • #18 g_list_foreach
    at /build/glib2.0-IfQpAv/glib2.0-2.47.3/./glib/glist.c line 1005
  • #19 nautilus_window_destroy
    at nautilus-window.c line 2127
  • #20 g_closure_invoke
    at /build/glib2.0-IfQpAv/glib2.0-2.47.3/./gobject/gclosure.c line 804
  • #21 signal_emit_unlocked_R
    at /build/glib2.0-IfQpAv/glib2.0-2.47.3/./gobject/gsignal.c line 3745
  • #22 g_signal_emit_valist
    at /build/glib2.0-IfQpAv/glib2.0-2.47.3/./gobject/gsignal.c line 3385
  • #23 g_signal_emit
    at /build/glib2.0-IfQpAv/glib2.0-2.47.3/./gobject/gsignal.c line 3441
  • #24 gtk_widget_dispose
    at /build/gtk+3.0-JTuwRW/gtk+3.0-3.18.5/./gtk/gtkwidget.c line 12010
  • #25 gtk_window_dispose
    at /build/gtk+3.0-JTuwRW/gtk+3.0-3.18.5/./gtk/gtkwindow.c line 3063
  • #26 gtk_application_window_dispose
    at /build/gtk+3.0-JTuwRW/gtk+3.0-3.18.5/./gtk/gtkapplicationwindow.c line 792
  • #27 g_object_run_dispose
    at /build/glib2.0-IfQpAv/glib2.0-2.47.3/./gobject/gobject.c line 1082
  • #28 nautilus_window_delete_event
    at nautilus-window.c line 2370
  • #29 _gtk_marshal_BOOLEAN__BOXEDv
    at /build/gtk+3.0-JTuwRW/gtk+3.0-3.18.5/./gtk/gtkmarshalers.c line 131
  • #30 _g_closure_invoke_va
    at /build/glib2.0-IfQpAv/glib2.0-2.47.3/./gobject/gclosure.c line 867
  • #31 g_signal_emit_valist
    at /build/glib2.0-IfQpAv/glib2.0-2.47.3/./gobject/gsignal.c line 3294
  • #32 g_signal_emit
    at /build/glib2.0-IfQpAv/glib2.0-2.47.3/./gobject/gsignal.c line 3441
  • #33 gtk_widget_event_internal
    at /build/gtk+3.0-JTuwRW/gtk+3.0-3.18.5/./gtk/gtkwidget.c line 7692
  • #34 gtk_main_do_event
    at /build/gtk+3.0-JTuwRW/gtk+3.0-3.18.5/./gtk/gtkmain.c line 1732
  • #35 send_delete_event
    at /build/gtk+3.0-JTuwRW/gtk+3.0-3.18.5/./gtk/gtkwindow.c line 1288
  • #36 gdk_threads_dispatch
    at /build/gtk+3.0-JTuwRW/gtk+3.0-3.18.5/./gdk/gdk.c line 719
  • #37 g_main_dispatch
    at /build/glib2.0-IfQpAv/glib2.0-2.47.3/./glib/gmain.c line 3154
  • #38 g_main_context_dispatch
    at /build/glib2.0-IfQpAv/glib2.0-2.47.3/./glib/gmain.c line 3769
  • #39 g_main_context_iterate
    at /build/glib2.0-IfQpAv/glib2.0-2.47.3/./glib/gmain.c line 3840
  • #40 g_main_context_iteration
    at /build/glib2.0-IfQpAv/glib2.0-2.47.3/./glib/gmain.c line 3901
  • #41 g_application_run
    at /build/glib2.0-IfQpAv/glib2.0-2.47.3/./gio/gapplication.c line 2311
  • #42 main
    at nautilus-main.c line 103 






Comment 1


Carlos Soriano





          2015-12-09 10:07:26 UTC
        



Are you using templates?






Comment 2


Sebastien Bacher





          2015-12-09 10:24:27 UTC
        



I'm not able to reproduce and the error tracker just do collection/stats on issues so we know if happens but don't have the details you are asking for ... still it's a real issue and would be nice to not dismiss it






Comment 3


Carlos Soriano





          2015-12-09 16:36:32 UTC
        



(In reply to Sebastien Bacher from comment #2)
> I'm not able to reproduce and the error tracker just do collection/stats on
> issues so we know if happens but don't have the details you are asking for
> ... still it's a real issue and would be nice to not dismiss it

Sadly it's hard without ability to ask about the issue.

There are some similar fixes in the 3.18 branch that will be available in 3.18.3, was happening when using templates.






Comment 4


Sebastien Bacher





          2016-01-07 09:45:25 UTC
        



there are be no new reports since > 3.18.2, assuming it's resolved in the current version and closing