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 744588 - nautilus crashes when reordering bookmarks
nautilus crashes when reordering bookmarks
Status: RESOLVED DUPLICATE of bug 739150
Product: nautilus
Classification: Core
Component: Bookmarks
3.14.x
Other Linux
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-02-16 11:56 UTC by Jonas
Modified: 2015-02-16 18:59 UTC
See Also:
GNOME target: ---
GNOME version: 3.13/3.14


Description Jonas 2015-02-16 11:56:23 UTC 
Nautilus 3.14.1-0ubuntu1~utopic1 crash when I try to reorder bookmarks via drag-and-drop. I select a bookmark and drag it up or down in the bookmarks list, and when I release the mouse button, it results in "Segmentation fault (core dumped)"

OS is Ubuntu 14.10 Gnome edition.
Comment 1 André Klapper 2015-02-16 18:04:54 UTC 
Thanks for taking the time to report this.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so. When pasting a stack trace in this bug report, please reset the status of this bug report from NEEDINFO to its previous status. Thanks in advance!
Comment 2 Jonas 2015-02-16 18:39:49 UTC 
I followed the instructions and got the stack trace using gdb. I hope it helps. Here it is:

+ Trace 234657

Thread 1 (Thread 0x7f2be2135a40 (LWP 26021))

  • #0 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #1 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #2 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #3 g_closure_invoke
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #4 ??
  • #5 g_signal_emit_valist
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #6 g_signal_emit
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #7 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #8 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #9 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #10 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #11 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #12 g_closure_invoke
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  • #16 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #17 ??
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #18 gtk_main_do_event
    from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  • #19 ??
    from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  • #20 g_main_context_dispatch
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #21 ??
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #22 g_main_context_iteration
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #23 g_application_run
    from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  • #24 main
    at nautilus-main.c line 103 






Comment 3


Jonas





          2015-02-16 18:46:55 UTC
        



Sorry, I seem to have forgotten to instal dbg packages. I'm also unable to set any other status of this bug rather than NEEDINFO. Updated stack trace: 





+
Trace
    234658






Thread 1
          (Thread 0x7f2be2135a40 (LWP 26021))


    

  • 
#0
clicked_eject_button

    
                at /build/buildd/gtk+3.0-3.14.4/./gtk/gtkplacessidebar.c
                  line
                  1426

    

    • 

  • 
#1
bookmarks_button_release_event_cb

    
                at /build/buildd/gtk+3.0-3.14.4/./gtk/gtkplacessidebar.c
                  line
                  3588

    

    • 

  • 
#2
_gtk_marshal_BOOLEAN__BOXED

    
                at /build/buildd/gtk+3.0-3.14.4/./gtk/gtkmarshalers.c
                  line
                  85

    

    • 

  • 
#3
g_closure_invoke

    • 

  • 
#4
signal_emit_unlocked_R

    
                at /build/buildd/glib2.0-2.42.1/./gobject/gsignal.c
                  line
                  3553

    

    • 

  • 
#5
g_signal_emit_valist

    
                at /build/buildd/glib2.0-2.42.1/./gobject/gsignal.c
                  line
                  3319

    

    • 

  • 
#6
g_signal_emit

    
                at /build/buildd/glib2.0-2.42.1/./gobject/gsignal.c
                  line
                  3365

    

    • 

  • 
#7
gtk_widget_event_internal

    
                at /build/buildd/gtk+3.0-3.14.4/./gtk/gtkwidget.c
                  line
                  7773

    

    • 

  • 
#8
propagate_event_up

    
                at /build/buildd/gtk+3.0-3.14.4/./gtk/gtkmain.c
                  line
                  2424

    

    • 

  • 
#9
propagate_event

    • 

  • 
#10
gtk_propagate_event

    
                at /build/buildd/gtk+3.0-3.14.4/./gtk/gtkmain.c
                  line
                  2561

    

    • 

  • 
#11
gtk_drag_end

    
                at /build/buildd/gtk+3.0-3.14.4/./gtk/gtkdnd.c
                  line
                  4212

    

    • 

  • 
#12
gtk_drag_button_release_cb

    
                at /build/buildd/gtk+3.0-3.14.4/./gtk/gtkdnd.c
                  line
                  4401

    

    • 

  • 
#13
_gtk_marshal_BOOLEAN__BOXED

    
                at /build/buildd/gtk+3.0-3.14.4/./gtk/gtkmarshalers.c
                  line
                  85

    

    • 

  • 
#14
g_closure_invoke

    
                at /build/buildd/glib2.0-2.42.1/./gobject/gclosure.c
                  line
                  768

    

    • 

  • 
#15
signal_emit_unlocked_R

    
                at /build/buildd/glib2.0-2.42.1/./gobject/gsignal.c
                  line
                  3553

    

    • 

  • 
#16
g_signal_emit_valist

    
                at /build/buildd/glib2.0-2.42.1/./gobject/gsignal.c
                  line
                  3319

    

    • 

  • 
#17
g_signal_emit

    
                at /build/buildd/glib2.0-2.42.1/./gobject/gsignal.c
                  line
                  3365

    

    • 

  • 
#18
gtk_widget_event_internal

    
                at /build/buildd/gtk+3.0-3.14.4/./gtk/gtkwidget.c
                  line
                  7773

    

    • 

  • 
#19
_gtk_window_check_handle_wm_event

    
                at /build/buildd/gtk+3.0-3.14.4/./gtk/gtkwindow.c
                  line
                  7719

    

    • 

  • 
#20
gtk_main_do_event

    
                at /build/buildd/gtk+3.0-3.14.4/./gtk/gtkmain.c
                  line
                  1566

    

    • 

  • 
#21
gdk_event_source_dispatch

    
                at /build/buildd/gtk+3.0-3.14.4/./gdk/x11/gdkeventsource.c
                  line
                  364

    

    • 

  • 
#22
g_main_dispatch

    
                at /build/buildd/glib2.0-2.42.1/./glib/gmain.c
                  line
                  3111

    

    • 

  • 
#23
g_main_context_dispatch

    
                at /build/buildd/glib2.0-2.42.1/./glib/gmain.c
                  line
                  3710

    

    • 

  • 
#24
g_main_context_iterate

    • 

  • 
#25
g_main_context_iteration

    
                at /build/buildd/glib2.0-2.42.1/./glib/gmain.c
                  line
                  3842

    

    • 

  • 
#26
g_application_run

    
                at /build/buildd/glib2.0-2.42.1/./gio/gapplication.c
                  line
                  2282

    

    • 

  • 
#27
main

    
                at nautilus-main.c
                  line
                  103

    

    • 













Comment 4


Cosimo Cecchi





          2015-02-16 18:59:07 UTC
        



Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade provided by your Linux distribution.

*** This bug has been marked as a duplicate of bug 739150 ***