Bug 599658 – evolution crashed with SIGSEGV in glade_xml_get_widget()

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 599658 - evolution crashed with SIGSEGV in glade_xml_get_widget()


Summary:	evolution crashed with SIGSEGV in glade_xml_get_widget()


Status:	RESOLVED FIXED

Product:	evolution-rss
Classification:	Other
Component:	general
Version:	0.1.4
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	evolution-rss-maint
QA Contact:	evolution-rss-maint

URL:
Whiteboard:

Duplicates:	610719 618549 (view as bug list)
Depends on:
Blocks:

Reported:	2009-10-26 14:11 UTC by Pedro Villavicencio
Modified:	2010-05-13 18:28 UTC

See Also:
GNOME target:	---
GNOME version:	2.27/2.28

Description Pedro Villavicencio 2009-10-26 14:11:11 UTC

this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/evolution-rss/+bug/459329

"When i subscribed to an RSS, evolution crashed."

".

+ Trace 218578

Thread 1 (process 2395)

#0 glade_xml_get_widget
at glade-xml.c line 515
#1 rss_folder_factory_commit
at rss-config-factory.c line 2272
#2 epl_invoke
at e-plugin.c line 1055
#3 e_plugin_invoke
at e-plugin.c line 768
#4 ech_commit
at e-config.c line 1279
#5 e_config_commit
at e-config.c line 1027
#6 emfp_dialog_response
at em-folder-properties.c line 65
#7 g_cclosure_marshal_VOID
from /usr/lib/libgobject-2.0.so.0
#8 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#9 ??
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#12 IA__gtk_dialog_response
at /build/buildd/gtk+2.0-2.18.3/gtk/gtkdialog.c line 928
#13 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#15 ??
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#18 IA__gtk_button_clicked
at /build/buildd/gtk+2.0-2.18.3/gtk/gtkbutton.c line 1111
#19 gtk_real_button_released
at /build/buildd/gtk+2.0-2.18.3/gtk/gtkbutton.c line 1707
#20 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#21 ??
from /usr/lib/libgobject-2.0.so.0
#22 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#23 ??
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#26 IA__gtk_button_released
at /build/buildd/gtk+2.0-2.18.3/gtk/gtkbutton.c line 1103
#27 gtk_button_button_release
at /build/buildd/gtk+2.0-2.18.3/gtk/gtkbutton.c line 1599
#28 _gtk_marshal_BOOLEAN__BOXED
at /build/buildd/gtk+2.0-2.18.3/gtk/gtkmarshalers.c line 84
#29 ??
from /usr/lib/libgobject-2.0.so.0
#30 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#31 ??
from /usr/lib/libgobject-2.0.so.0
#32 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#33 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#34 gtk_widget_event_internal
at /build/buildd/gtk+2.0-2.18.3/gtk/gtkwidget.c line 4767
#35 IA__gtk_propagate_event
at /build/buildd/gtk+2.0-2.18.3/gtk/gtkmain.c line 2417
#36 IA__gtk_main_do_event
at /build/buildd/gtk+2.0-2.18.3/gtk/gtkmain.c line 1622
#37 gdk_event_dispatch
at /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkevents-x11.c line 2369
#38 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#39 ??
from /lib/libglib-2.0.so.0
#40 g_main_loop_run
from /lib/libglib-2.0.so.0
#41 bonobo_main
at bonobo-main.c line 311
#42 main
at main.c line 732

Comment 1 Lucian Langa 2009-10-26 16:49:52 UTC

Already fixed in debian

http://packages.qa.debian.org/e/evolution-rss/news/20090923T223629Z.html

patch available here:

http://gnome.eu.org/patches/evolution-rss-0.1.4-folder-properties.patch

Comment 2 Pedro Villavicencio 2009-10-26 17:06:06 UTC

awesome, thanks for pointer!

Comment 3 Akhil Laddha 2010-02-23 03:53:36 UTC

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

Comment 4 Fabio Durán Verdugo 2010-05-13 18:28:28 UTC

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