Bug 524843 – gnome-appearance-properties crashed with SIGSEGV in gnome_vfs_uri_unref()

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 524843 - gnome-appearance-properties crashed with SIGSEGV in gnome_vfs_uri_unref()


Summary:	gnome-appearance-properties crashed with SIGSEGV in gnome_vfs_uri_unref()


Status:	RESOLVED DUPLICATE of bug 524567

Product:	gnome-control-center
Classification:	Core
Component:	[obsolete] Appearance
Version:	2.22.x
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Control-Center Maintainers
QA Contact:	Control-Center Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-03-28 18:56 UTC by Sebastien Bacher
Modified:	2008-03-29 08:42 UTC

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

Description Sebastien Bacher 2008-03-28 18:56:21 UTC

The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/205469

"Binary package hint: gnome-control-center

When I dragged an archive containing a file, but the archive was the wrong type (.tar), the appearance preferences window stopped working and crashed after a while.

+ Trace 193554

#0 gnome_vfs_uri_unref
at gnome-vfs-uri.c line 1026
#1 IA__g_list_foreach
at /build/buildd/glib2.0-2.16.1/glib/glist.c line 789
#2 gnome_vfs_uri_list_unref
at gnome-vfs-uri.c line 2074
#3 theme_drag_data_received_cb
at appearance-themes.c line 813
#4 _gtk_marshal_VOID__OBJECT_INT_INT_BOXED_UINT_UINT
at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmarshalers.c line 2247
#5 IA__g_closure_invoke
at /build/buildd/glib2.0-2.16.1/gobject/gclosure.c line 490
#6 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.16.1/gobject/gsignal.c line 2440
#7 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.16.1/gobject/gsignal.c line 2199
#8 IA__g_signal_emit_by_name
at /build/buildd/glib2.0-2.16.1/gobject/gsignal.c line 2267
#9 gtk_drag_selection_received
at /build/buildd/gtk+2.0-2.12.9/gtk/gtkdnd.c line 1590
#10 IA__g_closure_invoke
at /build/buildd/glib2.0-2.16.1/gobject/gclosure.c line 490
#11 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.16.1/gobject/gsignal.c line 2440
#12 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.16.1/gobject/gsignal.c line 2199
#13 IA__g_signal_emit_by_name
at /build/buildd/glib2.0-2.16.1/gobject/gsignal.c line 2267
#14 gtk_selection_retrieval_report
at /build/buildd/gtk+2.0-2.12.9/gtk/gtkselection.c line 2772
#15 _gtk_selection_notify
at /build/buildd/gtk+2.0-2.12.9/gtk/gtkselection.c line 2578
#16 _gtk_marshal_BOOLEAN__BOXED
at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmarshalers.c line 84
#17 IA__g_closure_invoke
at /build/buildd/glib2.0-2.16.1/gobject/gclosure.c line 490
#18 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.16.1/gobject/gsignal.c line 2478
#19 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.16.1/gobject/gsignal.c line 2209
#20 IA__g_signal_emit
at /build/buildd/glib2.0-2.16.1/gobject/gsignal.c line 2243
#21 gtk_widget_event_internal
at /build/buildd/gtk+2.0-2.12.9/gtk/gtkwidget.c line 4678
#22 IA__gtk_main_do_event
at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c line 1576
#23 gdk_event_dispatch
at /build/buildd/gtk+2.0-2.12.9/gdk/x11/gdkevents-x11.c line 2351
#24 IA__g_main_context_dispatch
at /build/buildd/glib2.0-2.16.1/glib/gmain.c line 2003
#25 g_main_context_iterate
at /build/buildd/glib2.0-2.16.1/glib/gmain.c line 2636
#26 IA__g_main_loop_run
at /build/buildd/glib2.0-2.16.1/glib/gmain.c line 2844
#27 IA__gtk_main
at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c line 1163
#28 main
at appearance-main.c line 191

Comment 1 Jens Granseuer 2008-03-29 08:42:00 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 524567 ***