Bug 564742 – File browser crashes gEdit

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 564742 - File browser crashes gEdit


Summary:	File browser crashes gEdit


Status:	RESOLVED DUPLICATE of bug 556410

Product:	gedit-plugins
Classification:	Other
Component:	General
Version:	2.24.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Gedit maintainers
QA Contact:	Gedit maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-12-16 15:08 UTC by Martin Vielsmaier
Modified:	2019-03-23 20:48 UTC

See Also:
GNOME target:	---
GNOME version:	2.23/2.24

Description Martin Vielsmaier 2008-12-16 15:08:42 UTC

Steps to reproduce:
1. Expand a folder in the browser
2. Expand a subfolder 
3. Double click the folder you expanded in 1.


Stack trace:
Program received signal SIGSEGV, Segmentation fault.

+ Trace 210851

Thread 3071620864 (LWP 17172)

#0 gtk_tree_path_next
from /usr/lib/libgtk-x11-2.0.so.0
#1 ??
from /usr/lib/gedit-2/plugins/libfilebrowser.so
#2 ??
from /usr/lib/gedit-2/plugins/libfilebrowser.so
#3 ??
from /usr/lib/gedit-2/plugins/libfilebrowser.so
#4 gedit_file_browser_store_set_virtual_root
from /usr/lib/gedit-2/plugins/libfilebrowser.so
#5 ??
from /usr/lib/gedit-2/plugins/libfilebrowser.so
#6 g_cclosure_marshal_VOID__BOXED
from /usr/lib/libgobject-2.0.so.0
#7 ??
from /usr/lib/libgobject-2.0.so.0
#8 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#9 ??
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#12 ??
from /usr/lib/gedit-2/plugins/libfilebrowser.so
#13 ??
from /usr/lib/gedit-2/plugins/libfilebrowser.so
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
from /usr/lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#17 ??
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#20 ??
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#23 ??
from /usr/lib/libgdk-x11-2.0.so.0
#24 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#25 ??
from /usr/lib/libglib-2.0.so.0
#26 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#27 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#28 main



Other information:

Comment 1 palfrey 2008-12-16 15:39:02 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!

Comment 2 Martin Vielsmaier 2008-12-16 18:03:38 UTC

I'm afraid there are now debug symbols for libfilebrowser, are there?

Program received signal SIGSEGV, Segmentation fault.

+ Trace 210860

Thread 3070781184 (LWP 8027)

#0 IA__gtk_tree_path_next
at /build/buildd/gtk+2.0-2.14.4/gtk/gtktreemodel.c line 786
#1 ??
from /usr/lib/gedit-2/plugins/libfilebrowser.so
#2 ??
from /usr/lib/gedit-2/plugins/libfilebrowser.so
#3 ??
from /usr/lib/gedit-2/plugins/libfilebrowser.so
#4 gedit_file_browser_store_set_virtual_root
from /usr/lib/gedit-2/plugins/libfilebrowser.so
#5 ??
from /usr/lib/gedit-2/plugins/libfilebrowser.so
#6 IA__g_cclosure_marshal_VOID__BOXED
at /build/buildd/glib2.0-2.18.2/gobject/gmarshal.c line 566
#7 g_type_class_meta_marshal
at /build/buildd/glib2.0-2.18.2/gobject/gclosure.c line 878
#8 IA__g_closure_invoke
at /build/buildd/glib2.0-2.18.2/gobject/gclosure.c line 767
#9 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.18.2/gobject/gsignal.c line 3282
#10 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.18.2/gobject/gsignal.c line 2977
#11 IA__g_signal_emit
at /build/buildd/glib2.0-2.18.2/gobject/gsignal.c line 3034
#12 ??
from /usr/lib/gedit-2/plugins/libfilebrowser.so
#13 ??
from /usr/lib/gedit-2/plugins/libfilebrowser.so
#14 _gtk_marshal_BOOLEAN__BOXED
at /build/buildd/gtk+2.0-2.14.4/gtk/gtkmarshalers.c line 84
#15 g_type_class_meta_marshal
at /build/buildd/glib2.0-2.18.2/gobject/gclosure.c line 878
#16 IA__g_closure_invoke
at /build/buildd/glib2.0-2.18.2/gobject/gclosure.c line 767
#17 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.18.2/gobject/gsignal.c line 3282
#18 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.18.2/gobject/gsignal.c line 2987
#19 IA__g_signal_emit
at /build/buildd/glib2.0-2.18.2/gobject/gsignal.c line 3034
#20 gtk_widget_event_internal
at /build/buildd/gtk+2.0-2.14.4/gtk/gtkwidget.c line 4745
#21 IA__gtk_propagate_event
at /build/buildd/gtk+2.0-2.14.4/gtk/gtkmain.c line 2391
#22 IA__gtk_main_do_event
at /build/buildd/gtk+2.0-2.14.4/gtk/gtkmain.c line 1581
#23 gdk_event_dispatch
at /build/buildd/gtk+2.0-2.14.4/gdk/x11/gdkevents-x11.c line 2365
#24 IA__g_main_context_dispatch
at /build/buildd/glib2.0-2.18.2/glib/gmain.c line 2144
#25 g_main_context_iterate
at /build/buildd/glib2.0-2.18.2/glib/gmain.c line 2778
#26 IA__g_main_loop_run
at /build/buildd/glib2.0-2.18.2/glib/gmain.c line 2986
#27 IA__gtk_main
at /build/buildd/gtk+2.0-2.14.4/gtk/gtkmain.c line 1200
#28 main

Comment 3 palfrey 2008-12-16 18:08:22 UTC

(In reply to comment #2)
> I'm afraid there are now debug symbols for libfilebrowser, are there?

This does at least help us find another bug report (with full debugging symbols) that this is a duplicate of. Of course, now that still needs fixing though, but this does help a little bit...

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