gedit crashed with SIGSEGV in gtk_tree_path_next()

[Matteo Settenvini]

Binary package hint: gedit

This is how I got hit by this. Your mileage may vary.

* Enable the "File browser plugin" for the sidebar
* In the sidebar, use a bookmarked SFTP folder to navigate to a remote share
* Make sure the filter for binary files is on
* Navigate into a directory which contains some unrecognized file formats (for example, and uncannily, "index.jsp"), no proper "text" files, and has a couple of children directories.
* Expand this folder
* Click on the parent folder name (the one having these directories and these "binary" files in).
* Crash.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/gedit
NonfreeKernelModules: fglrx
Package: gedit 2.24.0-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: gedit
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gedit
StacktraceTop:
 gtk_tree_path_next () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/gedit-2/plugins/libfilebrowser.so
 ?? () from /usr/lib/gedit-2/plugins/libfilebrowser.so
 ?? () from /usr/lib/gedit-2/plugins/libfilebrowser.so
 gedit_file_browser_store_set_virtual_root ()
Title: gedit crashed with SIGSEGV in gtk_tree_path_next()
Uname: Linux 2.6.27-7-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner uml-net video

[Apport retracing service (apport)]

StacktraceTop:IA__gtk_tree_path_next (path=0xa2d8bc0) at /build/buildd/gtk+2.0-2.14.3/gtk/gtktreemodel.c:786
model_fill (model=0xa302250, node=0xa354d28, path=0xa2d8bc0) at gedit-file-browser-store.c:2296
model_fill (model=0xa302250, node=0xa34c0f0, path=0xa2d8bc0) at gedit-file-browser-store.c:2293
set_virtual_root_from_node (model=0xa302250, node=0xa34c0f0) at gedit-file-browser-store.c:2384
gedit_file_browser_store_set_virtual_root (model=0xa302250, iter=0xa29bbd0) at gedit-file-browser-store.c:2703

[Pedro Villavicencio (pedro)]

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=556410

[Paolo Borelli (pborelli)]

I tried to reproduce with the steps you described, but it didn't crash? Can you reproduce it systematically?

A crash inside gtk_tree_path_next sounds very unlikely, so I think it may be some memory corruption: can you attach a valgrind log of the crash? To obtain it run:

G_SLICE=always-malloc G_DEBUG=gc-friendly,resident-modules valgrind --tool=memcheck --leak-check=full --leak-resolution=high --num-callers=20 --log-file=vgdump gedit

and attach the vgdump file

[Pedro Villavicencio (pedro)]

this is fixed upstream now , thanks for reporting.

[Sebastien Bacher (seb128)]

the new version is in jaunty now