Bug 519050 – nautilus crashed with signal 7 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 519050 - nautilus crashed with signal 7 in g_closure_invoke()


Summary:	nautilus crashed with signal 7 in g_closure_invoke()


Status:	RESOLVED FIXED

Product:	nautilus
Classification:	Core
Component:	[obsolete] GIO
Version:	2.21.x
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	2.22.x
Assigned To:	Christian Neumair
QA Contact:	gvfs-maint

URL:
Whiteboard:

Duplicates:	519779 519984 520583 520951 521657 (view as bug list)
Depends on:
Blocks:

Reported:	2008-02-27 13:02 UTC by Pedro Villavicencio
Modified:	2008-03-10 20:38 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Attachments
Proposed patch (476 bytes, patch) 2008-02-27 13:18 UTC, Christian Neumair	committed	Details \| Review

Description Pedro Villavicencio 2008-02-27 13:02:34 UTC

this bug has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/nautilus/+bug/196096

"I was cleaning trash when this crash happened."

".

+ Trace 190619

Thread 1 (process 7054)

#0 trash_state_changed_cb
at nautilus-pathbar.c line 211
#1 IA__g_closure_invoke
at /build/buildd/glib2.0-2.15.6/gobject/gclosure.c line 490
#2 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.15.6/gobject/gsignal.c line 2440
#3 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.15.6/gobject/gsignal.c line 2199
#4 IA__g_signal_emit
at /build/buildd/glib2.0-2.15.6/gobject/gsignal.c line 2243
#5 update_info_cb
at nautilus-trash-monitor.c line 128
#6 query_info_async_cb
at gdaemonfile.c line 803
#7 async_path_call_done
at gdaemonfile.c line 563
#8 async_call_finish
at gvfsdaemondbus.c line 428
#9 handle_async_reply
at gdbusutils.c line 1245
#10 complete_pending_call_and_unlock
at dbus-connection.c line 2170
#11 dbus_connection_dispatch
at dbus-connection.c line 4296
#12 dbus_source_dispatch
at gdbusutils.c line 836
#13 IA__g_main_context_dispatch
at /build/buildd/glib2.0-2.15.6/glib/gmain.c line 2065
#14 g_main_context_iterate
at /build/buildd/glib2.0-2.15.6/glib/gmain.c line 2698
#15 IA__g_main_loop_run
at /build/buildd/glib2.0-2.15.6/glib/gmain.c line 2906
#16 IA__gtk_main
at /build/buildd/gtk+2.0-2.12.8/gtk/gtkmain.c line 1163
#17 main
at nautilus-main.c line 572
#18 __libc_start_main
from /lib/libc.so.6
#19 _start

Comment 1 Cosimo Cecchi 2008-02-27 13:10:24 UTC

-> GVfs
This seems to be a crash in GVfs, reassigning.

Comment 2 Christian Neumair 2008-02-27 13:18:01 UTC

Created attachment 106065 [details] [review]
Proposed patch

I disagree, it rather looks like a Nautilus issue. I'm attaching a patch that disconnects the trash monitor signal handler when the pathbar is destroyed:

http://mail.gnome.org/archives/nautilus-list/2008-February/msg00210.html

Comment 3 Cosimo Cecchi 2008-02-27 13:34:02 UTC

-> Nautilus

Ok, that's my fault then, since I introduced that code for bug #332162.

Comment 4 Christian Neumair 2008-02-27 15:04:01 UTC

Committed, closing.

Comment 5 Cosimo Cecchi 2008-03-02 12:15:42 UTC

*** Bug 519779 has been marked as a duplicate of this bug. ***

Comment 6 Cosimo Cecchi 2008-03-03 01:26:11 UTC

*** Bug 519984 has been marked as a duplicate of this bug. ***

Comment 7 Cosimo Cecchi 2008-03-06 16:32:25 UTC

*** Bug 520583 has been marked as a duplicate of this bug. ***

Comment 8 Cosimo Cecchi 2008-03-07 11:08:10 UTC

*** Bug 520951 has been marked as a duplicate of this bug. ***

Comment 9 Cosimo Cecchi 2008-03-10 20:38:01 UTC

*** Bug 521657 has been marked as a duplicate of this bug. ***