Bug 624717 – f-spot.exe crashed with SIGSEGV in g_closure_invoke()

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 624717 - f-spot.exe crashed with SIGSEGV in g_closure_invoke()


Summary:	f-spot.exe crashed with SIGSEGV in g_closure_invoke()


Status:	RESOLVED INCOMPLETE

Product:	f-spot
Classification:	Other
Component:	Editing
Version:	0.7.0
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	F-spot maintainers
QA Contact:	F-spot maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-07-19 10:52 UTC by Pedro Villavicencio
Modified:	2010-10-19 06:58 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Pedro Villavicencio 2010-07-19 10:52:13 UTC

this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/f-spot/+bug/606422

"Selecting multiple images (specifically, more than 4) and trying to edit tags causes f-spot to crash. There is a specific place in the right click menu, that once hovered over, causes f-spot to crash."

is this more like a gtk+ crash?

Backtrace:

".

+ Trace 222905

Thread 1 (process 24666)

#0 ??
#1 ??
#2 ??
#3 ??
#4 ??
#5 ??
#6 ??
#7 ??
#8 ??
#9 ??
#10 ??
#11 ??
#12 ??
from /lib/libpthread.so.0
#13 ___fprintf_chk
at fprintf_chk.c line 37
#14 ??
#15 ??
#16 ??
#17 ??
#18 mono_jit_walk_stack_from_ctx
at mini-exceptions.c line 675
#19 mono_handle_native_sigsegv
at mini-exceptions.c line 1758
#20 mono_arch_handle_altstack_exception
at exceptions-amd64.c line 879
#21 <signal handler called>
#22 _gtk_rbtree_next
at /build/buildd/gtk+2.0-2.21.2/gtk/gtkrbtree.c line 1287
#23 gtk_tree_view_bin_expose
at /build/buildd/gtk+2.0-2.21.2/gtk/gtktreeview.c line 4967
#24 gtk_tree_view_expose
at /build/buildd/gtk+2.0-2.21.2/gtk/gtktreeview.c line 5038
#25 _gtk_marshal_BOOLEAN__BOXED
at /build/buildd/gtk+2.0-2.21.2/gtk/gtkmarshalers.c line 84
#26 g_closure_invoke
at /build/buildd/glib2.0-2.25.11/gobject/gclosure.c line 288
#27 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.25.11/gobject/gsignal.c line 3095
#28 g_signal_emit_valist
at /build/buildd/glib2.0-2.25.11/gobject/gsignal.c line 2995
#29 g_signal_emitv
at /build/buildd/glib2.0-2.25.11/gobject/gsignal.c line 2816
#30 ??

Comment 1 Ruben Vermeersch 2010-07-20 12:00:21 UTC

This might be fixed in 0.7.1. Please retest and include the console output of running with --debug.

Comment 2 Fabio Durán Verdugo 2010-09-04 04:25:05 UTC

@pedro any news, can you retest in this version?

Comment 3 Pedro Villavicencio 2010-09-06 12:43:52 UTC

I'm asking on the downstream report.

Comment 4 Akhil Laddha 2010-10-19 06:58:30 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!