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 732513 - Segmentation fault with Nautilus 3.12.2
Segmentation fault with Nautilus 3.12.2
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: general
3.12.x
Other Linux
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 739238 742513 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2014-06-30 18:42 UTC by John Doe
Modified: 2015-01-08 12:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Gdb backtrace for Nautilus 3.12.2 (2.76 KB, text/plain)
2014-06-30 18:42 UTC, John Doe
Details

Description John Doe 2014-06-30 18:42:51 UTC
Created attachment 279633 [details]
Gdb backtrace for Nautilus 3.12.2

I use Nautilus 3.12.2 on a Gentoo Linux system.

I have several video files whose name has the following form: "XYZ - Title". I have to manually copy the "XYZ" substring of each file to another application. After that I simply delete the current file and move to the next one. While I was doing this Nautilus crashed a lot of times (segmentation fault). After a while I finally decided to file a bug report. Unfortunately I don't know what exactly caused the crash (renaming? deleting?). I was using the list view mode. I hope the backtrace I'm attaching is clear enough. It was obtained after having recompiled glib, nautilus and gtk+ with the -ggdb C(XX)FLAGS. I also added the "nostrip" option to the FEATURES variable.
Comment 1 André Klapper 2014-07-01 11:11:41 UTC
Pasting the stacktrace inline so traceparser can pick it up:

  • #0 cell_renderer_edited
    at nautilus-list-view.c line 1320
  • #1 g_closure_invoke
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/gobject/gclosure.c line 768
  • #2 signal_emit_unlocked_R
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/gobject/gsignal.c line 3551
  • #3 g_signal_emit_valist
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/gobject/gsignal.c line 3307
  • #4 g_signal_emit
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/gobject/gsignal.c line 3363
  • #5 gtk_cell_renderer_text_editing_done
    at gtkcellrenderertext.c line 1947
  • #6 popdown_timeout
    at gtkcellrenderertext.c line 1960
  • #7 gdk_threads_dispatch
    at gdk.c line 635
  • #8 g_timeout_dispatch
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gmain.c line 4472
  • #9 g_main_dispatch
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gmain.c line 3064
  • #10 g_main_context_dispatch
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gmain.c line 3663
  • #11 g_main_context_iterate
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gmain.c line 3734
  • #12 g_main_context_iteration
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gmain.c line 3795
  • #13 g_application_run
    at /var/tmp/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/gio/gapplication.c line 2114
  • #14 main
    at nautilus-main.c line 103

Comment 2 Cosimo Cecchi 2014-09-13 18:00:07 UTC
Thanks for the report, I pushed a fix to git master.
Comment 3 Cosimo Cecchi 2015-01-08 11:50:30 UTC
*** Bug 742513 has been marked as a duplicate of this bug. ***
Comment 4 Michael Clerx 2015-01-08 12:37:08 UTC
*** Bug 739238 has been marked as a duplicate of this bug. ***