inkscape crashed with SIGSEGV in gtk_file_info_get_is_folder()

[Juho Vuori]

Binary package hint: inkscape

This possibly happened when changing a svg-file with an external program, while it was being held open by inkscape. Don't know how to reproduce 100% sure.

ProblemType: Crash
Architecture: i386
Date: Sun Sep 23 22:51:30 2007
Disassembly: 0x0:
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/inkscape
NonfreeKernelModules: cdrom
Package: inkscape 0.45.1-1ubuntu5
PackageArchitecture: i386
ProcCmdline: inkscape
ProcCwd: /home/juho
ProcEnviron:
 PATH=/home/juho/bin:/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: inkscape
StacktraceTop:
 gtk_file_info_get_is_folder ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
Title: inkscape crashed with SIGSEGV in gtk_file_info_get_is_folder()
Uname: Linux loppa 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:name_sort_func (model=0xce74888, a=0xbf99f7ac, b=0xbf99f7fc, user_data=0x919c5a0) at /build/buildd/gtk+2.0-2.12.0/gtk/gtkfilechooserdefault.c:6273
gtk_tree_model_sort_level_find_insert (tree_model_sort=0xcdb19f0, level=0xa19dc40, iter=0xbf99f7fc, skip_index=1)
gtk_tree_model_sort_row_changed (s_model=0xce74888, start_s_path=0xa623368, start_s_iter=0xb882c60, data=0xcdb19f0)
_gtk_marshal_VOID__BOXED_BOXED (closure=0xce66ec8, return_value=0x0, n_param_values=3, param_values=0xbf99fa8c, invocation_hint=0xbf99f99c,
IA__g_closure_invoke (closure=0xce66ec8, return_value=0x0, n_param_values=3, param_values=0xbf99fa8c, invocation_hint=0xbf99f99c)

[Bryce Harrington (bryce)]

We've uploaded a preview release of Inkscape 0.46 to Hardy - can you check if you can reproduce this bug on Hardy's inkscape?

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!