Bug 515802 – evolution-data-server-2.22 crashed with signal 5 in g_type_class_ref()

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 515802 - evolution-data-server-2.22 crashed with signal 5 in g_type_class_ref()


Summary:	evolution-data-server-2.22 crashed with signal 5 in g_type_class_ref()


Status:	RESOLVED DUPLICATE of bug 64764

Product:	evolution-data-server
Classification:	Platform
Component:	Calendar
Version:	2.22.x (obsolete)
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-02-11 15:56 UTC by Pedro Villavicencio
Modified:	2013-09-14 16:50 UTC

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

Description Pedro Villavicencio 2008-02-11 15:56:00 UTC

This bug has been reported here:

https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/190883

"I had opened evolution and fetched email without any problem. Then, when I switched to calendar view (with two google-calendar-type ressources), evolution and eds went down."

"#0  IA__g_logv (log_domain=0xb7730a6b "GLib-GObject", 
    log_level=G_LOG_LEVEL_ERROR, format=0xb7735ad3 "%s()%s`%s'", 
    args1=0xb2ce291c "¶Zs·\027zs·x\032\001·1å_·´#")
    at /build/buildd/glib2.0-2.15.4/glib/gmessages.c:503
	depth = 1
	domain = (GLogDomain *) 0x80cfa38
	data = (gpointer) 0x8055d80
	log_func = (GLogFunc) 0x804aec0 <server_log_handler>
	domain_fatal_mask = 5
	test_level = <value optimized out>
	was_recursion = 0
	i = <value optimized out>

+ Trace 188838

#1 IA__g_log
#2 IA__g_type_class_ref
at /build/buildd/glib2.0-2.15.4/gobject/gtype.c line 2389
#3 IA__g_object_newv
at /build/buildd/glib2.0-2.15.4/gobject/gobject.c line 853
#4 IA__g_object_new_valist
at /build/buildd/glib2.0-2.15.4/gobject/gobject.c line 986
#5 IA__g_object_new
at /build/buildd/glib2.0-2.15.4/gobject/gobject.c line 795
#6 soup_session_sync_new
at soup-session-sync.c line 85
#7 gdata_google_service_instance_init
at gdata-google-service.c line 465
#8 IA__g_type_create_instance
at /build/buildd/glib2.0-2.15.4/gobject/gtype.c line 1569
#9 g_object_constructor
at /build/buildd/glib2.0-2.15.4/gobject/gobject.c line 1046
#10 IA__g_object_newv
at /build/buildd/glib2.0-2.15.4/gobject/gobject.c line 937
#11 IA__g_object_new_valist
at /build/buildd/glib2.0-2.15.4/gobject/gobject.c line 1027
#12 IA__g_object_new
at /build/buildd/glib2.0-2.15.4/gobject/gobject.c line 795
#13 gdata_google_service_new
at gdata-google-service.c line 666
#14 e_cal_backend_google_utils_connect
at e-cal-backend-google-utils.c line 290
#15 e_cal_backend_google_open
at e-cal-backend-google.c line 826
#16 e_cal_backend_sync_open
at e-cal-backend-sync.c line 186
#17 _e_cal_backend_open
at e-cal-backend-sync.c line 706
#18 e_cal_backend_open
at e-cal-backend.c line 618
#19 impl_Cal_open
at e-data-cal.c line 81
#20 _ORBIT_skel_small_GNOME_Evolution_Calendar_Cal_open
at Evolution-DataServer-Calendar-common.c line 44
#21 ORBit_POAObject_invoke
at poa.c line 1142
#22 ORBit_OAObject_invoke
at orbit-adaptor.c line 338
#23 ORBit_small_invoke_adaptor
at orbit-small.c line 844
#24 ORBit_POAObject_handle_request
at poa.c line 1351
#25 ORBit_POAObject_invoke_incoming_request
at poa.c line 1421
#26 giop_thread_queue_process
at giop.c line 771
#27 giop_request_handler_thread
at giop.c line 481
#28 g_thread_pool_thread_proxy
at /build/buildd/glib2.0-2.15.4/glib/gthreadpool.c line 265
#29 g_thread_create_proxy
at /build/buildd/glib2.0-2.15.4/glib/gthread.c line 635
#30 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#31 clone
from /lib/tls/i686/cmov/libc.so.6"

Comment 1 Srinivasa Ragavan 2008-02-15 20:39:47 UTC

Could be a glib issue.

Comment 2 Matthew Barnes 2008-03-03 02:51:15 UTC

(In reply to comment #1)
> Could be a glib issue. 

Or libsoup.

Comment 3 Dan Winship 2008-03-03 04:12:14 UTC

> (In reply to comment #1)
> > Could be a glib issue. 
> 
> Or libsoup.

Or glib. :)

In fact, this appears to be a 6-year-old gtype bug that by a strange coincidence was fixed in svn a week before this bug was filed...


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