gedit crashed with SIGSEGV in g_file_get_child()

[John Vivirito]

Binary package hint: gedit

9 out of every 10 time gedit crashes when opening any document including when starting a new doc. Doesnt matter if i open it from CLI or GUI it still crashes.

version of gedit is 2.23.1-0ubuntu1

Distributor ID: Ubuntu
Description: Ubuntu intrepid (development branch)
Release: 8.10
Codename: intrepid

Linux Development 2.6.24-17-generic #1 SMP Thu May 1 14:31:33 UTC 2008 i686 GNU/Linux

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Jun 9 09:44:39 2008
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/gedit
NonfreeKernelModules: nvidia
Package: gedit 2.23.1-0ubuntu1
PackageArchitecture: i386
ProcCmdline: gedit debian/changelog
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gedit
StacktraceTop:
 g_file_get_child () from /usr/lib/libgio-2.0.so.0
 ?? () from /usr/lib/gedit-2/plugins/libfilebrowser.so
 ?? () from /usr/lib/libgio-2.0.so.0
 g_simple_async_result_complete ()
 ?? () from /usr/lib/libgio-2.0.so.0
Title: gedit crashed with SIGSEGV in g_file_get_child()
Uname: Linux 2.6.24-17-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

[John Vivirito (gnomefreak)]

This is still happening as of june 24 2008

[John Vivirito (gnomefreak)]

June 29th still crashing pretty much every other time i open it

[Apport retracing service (apport)]

StacktraceTop:IA__g_file_get_child_for_display_name (file=0x84a2160,
model_iterate_next_files_cb (enumerator=0x8444880, result=0x8480630, parent=0x8435900)
g_file_enumerator_real_next_files_async (enumerator=0x8444880, num_files=138937904,
IA__g_simple_async_result_set_op_res_gboolean (simple=0x8435900, op_res=137366280)
IA__g_simple_async_result_set_op_res_gboolean (simple=0x8480630, op_res=0)

[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=546435

[John Vivirito (gnomefreak)]

This seems to have been fixed well atleast for me.

[Daniel Holbach (dholbach)]

It seems the issue was fixed for you, if it happens again, please reopen the bug.