Bug 420603 – crash while sycnronizing calendar with opensync

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 420603 - crash while sycnronizing calendar with opensync


Summary:	crash while sycnronizing calendar with opensync


Status:	RESOLVED INCOMPLETE

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

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

URL:
Whiteboard:

Duplicates:	472960 (view as bug list)
Depends on:
Blocks:

Reported:	2007-03-20 16:51 UTC by David Juran
Modified:	2011-02-09 10:53 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description David Juran 2007-03-20 16:51:19 UTC

Steps to reproduce:
I believe this is a followup to Bug 36102. I'm using evolution-data-server-1.8.3-4.fc6 which has the patch from Bug 36102 applied. When I now try to synchronise my evolution calendar with my phone using opensync, evolution-data-server still crashes, but this time in a different place. Note in the stack trace below how zone changes in a fishy way where it shouldn't...

(gdb) up 5

+ Trace 120404

Thread 1 (Thread -1208961328 (LWP 12493))

#0 __kernel_vsyscall
#1 raise
from /lib/i686/nosegneg/libc.so.6
#2 abort
from /lib/i686/nosegneg/libc.so.6
#3 __libc_message
from /lib/i686/nosegneg/libc.so.6
#4 free
from /lib/i686/nosegneg/libc.so.6
#5 icaltimezone_reset
at icaltimezone.c line 238
#6 icaltimezone_free
at icaltimezone.c line 227
#7 e_cal_backend_file_finalize
at e-cal-backend-file.c line 306
#8 e_cal_backend_file_events_finalize
at e-cal-backend-file-events.c line 137
#9 IA__g_object_unref
at gobject.c line 1788
#10 g_value_object_free_value
at gobject.c line 1908
#11 IA__g_value_unset
at gvalue.c line 155
#12 IA__g_signal_emit_valist
at gsignal.c line 2229
#13 IA__g_signal_emit
at gsignal.c line 2243
#14 e_cal_backend_remove_client
at e-cal-backend.c line 391
#15 listener_died_cb
at e-cal-backend.c line 385
#16 link_connection_get_type
from /usr/lib/libORBit-2.so.0
#17 link_connection_exec_disconnect
from /usr/lib/libORBit-2.so.0
#18 g_idle_dispatch
at gmain.c line 3928
#19 IA__g_main_context_dispatch
at gmain.c line 2045
#20 g_main_context_iterate
at gmain.c line 2677
#21 IA__g_main_loop_run
at gmain.c line 2881
#22 bonobo_main
at bonobo-main.c line 311
#23 main
at server.c line 400
#24 __libc_start_main
from /lib/i686/nosegneg/libc.so.6
#25 _start



Other information:

Comment 1 David Juran 2007-03-20 16:55:20 UTC

And the bug I'm referring to is of course 363102 )-:

Comment 2 Matthew Barnes 2007-03-20 18:56:51 UTC

Just to make it clicky, that's bug #363102.

Comment 3 Christian Kirbach 2007-03-21 18:47:59 UTC

good trace, no dups, confirming

Comment 4 Peter 2007-04-28 10:26:34 UTC

We also received bugreport about this issue in our bugzilla:
https://bugs.gentoo.org/show_bug.cgi?id=176216

Comment 5 Peter 2007-08-31 07:46:55 UTC

Previously I've just looked at backtrace, but look: our user receives the same backtrace with the different actions:

"I leave "alltray evolution" process running when shutting down the machine.
When I log on next day EDS starts and crashes. "

Thus this is not only opensync problem. I'd like to change subject, but I can't :(

Comment 6 palfrey 2007-09-03 17:02:35 UTC

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

Comment 7 Akhil Laddha 2010-12-30 09:17:40 UTC

Could you please confirm if this bug is still happening at your end ? Please try in GNOME 2.30.3 or 2.32.1 and report back, thanks.

Comment 8 Akhil Laddha 2011-02-09 10:53:24 UTC

Closing this bug report as no further information has been provided. 
Please feel free to reopen the bug if the problem still occurs with a newer
version of GNOME 2.32.1 or later, thanks.