Bug 425129 – crash in icaltimezone.c: zone->tznames == NULL

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 425129 - (Config) crash in icaltimezone.c: zone->tznames == NULL

(Config)
Summary:	crash in icaltimezone.c: zone->tznames == NULL


Status:	RESOLVED FIXED

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

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

URL:
Whiteboard:	This bug is on the auto-stacktrace-re...

Duplicates:	419675 421685 421911 425908 426144 426181 428926 429009 429225 429410 429984 430211 430378 432074 432077 432581 433705 435218 435554 436906 437474 438108 438310 438687 438848 439411 439551 440022 440133 440567 440912 442240 442713 442923 443046 443154 443245 443260 443261 443264 443273 443495 443508 443543 443544 443551 443621 443690 444424 444807 445428 445554 445670 445743 445755 445817 446641 446666 446678 446760 446762 446952 447200 447409 447523 447531 447791 447913 447981 448320 449106 449421 449518 449560 449703 449753 449946 450553 450625 450759 450855 450898 451214 451279 451477 451548 451561 451602 451771 451942 452190 452243 452459 452898 452931 453019 453040 453351 453682 453691 453709 453793 453887 453936 453992 454426 454550 454670 454683 455156 455161 455420 455431 455432 455524 455988 456162 456171 456210 461595 466137 467378 469514 471140 473258 475310 475396 (view as bug list)
Depends on:
Blocks:

Reported:	2007-04-01 11:59 UTC by Config
Modified:	2007-12-04 15:32 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Attachments
Don't crash when a zone does not have TZNAME (476 bytes, patch) 2007-04-13 13:28 UTC, Pascal Terjan	committed	Details \| Review
Add a timezone for Perth (585 bytes, patch) 2007-04-13 13:30 UTC, Pascal Terjan	committed	Details \| Review
resolve timezone check prob;em (619 bytes, patch) 2007-04-25 16:39 UTC, sin	none	Details \| Review

Description Config 2007-04-01 11:59:39 UTC

What were you doing when the application crashed?
Evolution simply doesn't launch, when I start it.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 222601216 vsize: 222601216 resident: 25882624 share: 15179776 rss: 25882624 rss_rlim: -1
CPU usage: start_time: 1175428734 rtime: 94 utime: 88 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution-2.8'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47161910119792 (LWP 8077)]
(no debugging symbols found)
0x00002ae4b89a5595 in waitpid () from /lib/libc.so.6

+ Trace 124037

Thread 1 (Thread 47161910119792 (LWP 8077))

#0 waitpid
from /lib/libc.so.6
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 killpg
from /lib/libc.so.6
#3 ??
#0 waitpid
from /lib/libc.so.6

Comment 1 palfrey 2007-04-02 13:18:11 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!

Comment 2 Config 2007-04-02 13:59:15 UTC

Had a look on the link above... The problem is that my evolution version is 2.8.1-0ubuntu4.1 and there is only -dbgsym for 2.8.1-0ubuntu4. I can't install it from repository because it doesn't like that my version is higher... What should I do?

Comment 3 palfrey 2007-04-02 14:14:03 UTC

There does appear to be dbgsyms for 2.8.1-0ubuntu4.1 in the repository. Not sure why they're not appear to you. You could try the folder http://people.ubuntu.com/~pitti/ddebs/pool/main/e/evolution/ and installing the .ddeb's directly? ("sudo dpkg -i something.ddeb" at the command line)

Comment 4 Config 2007-04-03 10:07:05 UTC

Downloaded and installed evolution and plugins -dbgsym from given page. I have started evolution once again, but Bug Buddy generated almost the same report... So, I tried gdb and the comands that were listed on "GettingTraces/Details" page. Here what we have:

+ Trace 124581

Thread 1 (Thread 47263941999984 (LWP 13841))

#0 strcmp
from /lib/libc.so.6
#1 icaltimezone_get_builtin_timezone_from_offset
from /usr/lib64/libecal-1.2.so.7
#2 e_timezone_dialog_set_timezone
at e-timezone-dialog.c line 327
#3 startup_wizard_timezone_page
at startup-wizard.c line 113
#4 epl_invoke
at e-plugin.c line 874
#5 ech_config_widget_factory
at e-config.c line 1353
#6 ec_rebuild
at e-config.c line 568
#7 e_config_create_widget
at e-config.c line 852
#8 e_config_create_window
at e-config.c line 897
#9 em_account_editor_new
at em-account-editor.c line 2832
#10 startup_wizard
#11 epl_invoke
at e-plugin.c line 874
#12 e_event_emit
at e-event.c line 296
#13 e_shell_attempt_upgrade
at e-shell.c line 906
#14 e_shell_construct
at e-shell.c line 690
#15 e_shell_new
at e-shell.c line 736
#16 idle_cb
at main.c line 350
#17 g_main_context_dispatch
from /usr/lib64/libglib-2.0.so.0
#18 g_main_context_check
from /usr/lib64/libglib-2.0.so.0
#19 g_main_loop_run
from /usr/lib64/libglib-2.0.so.0
#20 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#21 ??


Is it enough of debug info? Or should I do anything else?

Comment 5 palfrey 2007-04-03 10:49:01 UTC

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

Comment 6 palfrey 2007-04-03 10:49:05 UTC

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

Comment 7 palfrey 2007-04-03 10:49:09 UTC

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

Comment 8 palfrey 2007-04-03 10:52:33 UTC

(In reply to comment #4)
> Downloaded and installed evolution and plugins -dbgsym from given page. I have
> started evolution once again, but Bug Buddy generated almost the same report...
> So, I tried gdb and the comands that were listed on "GettingTraces/Details"
> page. Here what we have:

Thanks, that's a much better better stacktrace. However, we're still missing information from libecal. You should be able to install the libecal1.2-7-dbgsym package (available at http://people.ubuntu.com/~pitti/ddebs/pool/main/e/evolution-data-server/ if you can't find it), and then we can get the complete trace. 

Thanks for all your help!

Comment 9 Sebastien Bacher 2007-04-03 11:20:42 UTC

Debug backtrace on https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/99878:

+ Trace 124595

#0 strcmp
from /lib/tls/i686/cmov/libc.so.6
#1 icaltimezone_get_builtin_timezone_from_offset
at icaltimezone.c line 1436
#2 e_timezone_dialog_set_timezone
at e-timezone-dialog.c line 327
#3 startup_wizard_timezone_page
at startup-wizard.c line 113
#4 epl_invoke
at e-plugin.c line 874
#5 e_plugin_invoke
at e-plugin.c line 663
#6 ech_config_widget_factory
at e-config.c line 1353
#7 ec_rebuild
at e-config.c line 568
#8 e_config_create_widget
at e-config.c line 852
#9 e_config_create_window
at e-config.c line 897
#10 em_account_editor_new
at em-account-editor.c line 2832
#11 startup_wizard
at startup-wizard.c line 83
#12 epl_invoke
at e-plugin.c line 874
#13 e_plugin_invoke
at e-plugin.c line 663
#14 emph_event_handle
at e-event.c line 407
#15 e_event_emit
at e-event.c line 296
#16 e_shell_attempt_upgrade
at e-shell.c line 907
#17 e_shell_construct
at e-shell.c line 691
#18 e_shell_new
at e-shell.c line 737
#19 idle_cb
at main.c line 351
#20 g_idle_dispatch
at gmain.c line 3928
#21 IA__g_main_context_dispatch
at gmain.c line 2045
#22 g_main_context_iterate
at gmain.c line 2677
#23 IA__g_main_loop_run
at gmain.c line 2881
#24 bonobo_main
at bonobo-main.c line 311
#25 main
at main.c line 611

Comment 10 palfrey 2007-04-03 11:35:27 UTC

Marking as NEW now we've got duplicates and a detailed stacktrace.

Comment 11 Config 2007-04-03 13:28:29 UTC

I've installed libecall and ran gdb as did before (gdb evolution -> run -> thread apply all bt), but report is similar to previous one:

+ Trace 124626

Thread 1 (Thread 47740351135088 (LWP 18595))

#0 strcmp
from /lib/libc.so.6
#1 icaltimezone_get_builtin_timezone_from_offset
at icaltimezone.c line 1436
#2 e_timezone_dialog_set_timezone
at e-timezone-dialog.c line 327
#3 startup_wizard_timezone_page
at startup-wizard.c line 113
#4 epl_invoke
at e-plugin.c line 874
#5 ech_config_widget_factory
at e-config.c line 1353
#6 ec_rebuild
at e-config.c line 568
#7 e_config_create_widget
at e-config.c line 852
#8 e_config_create_window
at e-config.c line 897
#9 em_account_editor_new
at em-account-editor.c line 2832
#10 startup_wizard
#11 epl_invoke
at e-plugin.c line 874
#12 e_event_emit
at e-event.c line 296
#13 e_shell_attempt_upgrade
at e-shell.c line 906
#14 e_shell_construct
at e-shell.c line 690
#15 e_shell_new
at e-shell.c line 736
#16 idle_cb
at main.c line 350
#17 g_main_context_dispatch
from /usr/lib64/libglib-2.0.so.0
#18 g_main_context_check
from /usr/lib64/libglib-2.0.so.0
#19 g_main_loop_run
from /usr/lib64/libglib-2.0.so.0
#20 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#21 ??


Am I doing anything wrong?

Comment 12 palfrey 2007-04-03 13:41:46 UTC

(In reply to comment #11)
> I've installed libecall and ran gdb as did before (gdb evolution -> run ->
> thread apply all bt), but report is similar to previous one:

It's similar, but now frame #1 has the proper debugging symbols, so you've done the right thing. We now have enough information to hand over this bug to the main Evolution developers (hence why this bug has gone from being UNCONFIRMED/NEEDINFO to NEW). Thanks for your time!

Comment 13 Config 2007-04-03 15:09:18 UTC

You are welcome! Glad to be helpfull :)

Comment 14 Akhil Laddha 2007-04-04 03:52:53 UTC

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

Comment 15 Pascal Terjan 2007-04-04 21:39:23 UTC

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

Comment 16 Pascal Terjan 2007-04-04 22:17:50 UTC

2 zones don't have TZNAME set :

zoneinfo/Australia/Perth.ics
zoneinfo/Asia/Jerusalem.ics

this leads zone->tznames to be NULL

Comment 17 André Klapper 2007-04-12 21:48:26 UTC

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

Comment 18 André Klapper 2007-04-12 21:48:35 UTC

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

Comment 19 André Klapper 2007-04-12 21:50:29 UTC

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

Comment 20 Akhil Laddha 2007-04-13 12:37:38 UTC

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

Comment 21 Pascal Terjan 2007-04-13 13:28:03 UTC

Created attachment 86289 [details] [review]
Don't crash when a zone does not have TZNAME

Comment 22 Pascal Terjan 2007-04-13 13:30:19 UTC

Created attachment 86290 [details] [review]
Add a timezone for Perth

Here is a patch for Perth but as the ics contains :

PRODID:-//Ximian//NONSGML Evolution Olson-VTIMEZONE Converter//EN

I guess it is generated from elsewhere where it should be fixed...

Comment 23 palfrey 2007-04-16 14:12:48 UTC

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

Comment 24 sin 2007-04-25 16:39:13 UTC

Created attachment 86997 [details] [review]
resolve timezone check prob;em

With new updated timezones zone->tznames needs check for NULL

Comment 25 Pascal Terjan 2007-04-25 16:47:23 UTC

This is exactly the patch that I add already attached :)

Comment 26 Elijah Newren 2007-04-25 16:53:23 UTC

Marking patch from comment 24 as obsolete due to comment 25.

Comment 27 palfrey 2007-04-26 11:15:10 UTC

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

Comment 28 palfrey 2007-04-26 11:15:17 UTC

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

Comment 29 palfrey 2007-04-26 11:15:22 UTC

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

Comment 30 palfrey 2007-04-26 11:15:28 UTC

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

Comment 31 palfrey 2007-04-26 11:15:32 UTC

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

Comment 32 palfrey 2007-04-26 11:15:45 UTC

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

Comment 33 palfrey 2007-04-27 10:36:01 UTC

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

Comment 34 palfrey 2007-05-03 18:07:31 UTC

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

Comment 35 palfrey 2007-05-09 11:15:18 UTC

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

Comment 36 palfrey 2007-05-13 15:18:30 UTC

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

Comment 37 Bruno Boaventura 2007-05-15 21:16:30 UTC

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

Comment 38 André Klapper 2007-05-18 13:48:55 UTC

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

Comment 39 André Klapper 2007-05-18 13:49:11 UTC

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

Comment 40 André Klapper 2007-05-18 13:49:25 UTC

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

Comment 41 André Klapper 2007-05-18 13:50:30 UTC

bug 435218 is probably also a dup

Comment 42 Susana 2007-05-19 17:58:49 UTC

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

Comment 43 Susana 2007-05-19 17:58:59 UTC

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

Comment 44 André Klapper 2007-05-21 11:48:09 UTC

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

Comment 45 André Klapper 2007-05-21 11:48:22 UTC

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

Comment 46 André Klapper 2007-05-21 11:48:29 UTC

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

Comment 47 Pascal Terjan 2007-05-21 12:03:02 UTC

The patch avoiding the crash is _really_ trivial, can't any evolution maintainer have a look at it, or do we need more duplicates ?

Comment 48 Pedro Villavicencio 2007-05-22 21:12:05 UTC

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

Comment 49 André Klapper 2007-05-24 11:29:35 UTC

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

Comment 50 Chenthill P 2007-05-24 19:00:46 UTC

It would be safe to add a null check for the tzname string as well. Please commit the patches after incorporating the above mentioned change to svn HEAD and stable branch.

Comment 51 Pascal Terjan 2007-05-24 23:25:08 UTC

I committed the patches (with an additional check for tzname)

zoneinfo/Asia/Jerusalem.ics still has no TZNAME but I could not find it

Comment 52 palfrey 2007-05-30 10:41:07 UTC

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

Comment 53 Chenthill P 2007-05-31 08:22:27 UTC

(In reply to comment #51)
> I committed the patches (with an additional check for tzname)
> 
> zoneinfo/Asia/Jerusalem.ics still has no TZNAME but I could not find it
> 

The Tznames for standard and daylight zones for Jerusalem are IST and IDT respectively. You can update them as well. Timezone files are perfectly valid if they do not have the tzname as well.  Thanks for the patches !!! IMHO you can now mark the bug as resolved.

Comment 54 Pascal Terjan 2007-05-31 08:49:04 UTC

Thank you for the info !
The file is valid without tzname but it will be ignored if we look for the timezone by name like in this function so I prefer adding it.

Closing the bug.

Comment 55 Chenthill P 2007-05-31 09:21:14 UTC

Sure. Please add the tzname information.

Comment 56 palfrey 2007-06-01 13:14:38 UTC

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

Comment 57 Susana 2007-06-01 19:42:24 UTC

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

Comment 58 Pedro Villavicencio 2007-06-02 01:07:11 UTC

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

Comment 59 palfrey 2007-06-02 23:27:32 UTC

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

Comment 60 palfrey 2007-06-02 23:30:04 UTC

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

Comment 61 palfrey 2007-06-02 23:30:13 UTC

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

Comment 62 palfrey 2007-06-02 23:30:18 UTC

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

Comment 63 palfrey 2007-06-02 23:30:35 UTC

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

Comment 64 palfrey 2007-06-02 23:30:40 UTC

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

Comment 65 palfrey 2007-06-03 11:06:12 UTC

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

Comment 66 palfrey 2007-06-03 11:12:45 UTC

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

Comment 67 Susana 2007-06-03 16:06:37 UTC

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

Comment 68 Susana 2007-06-03 16:06:49 UTC

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

Comment 69 Susana 2007-06-03 16:07:05 UTC

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

Comment 70 Diego Escalante Urrelo (not reading bugmail) 2007-06-06 04:43:17 UTC

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

Comment 71 Diego Escalante Urrelo (not reading bugmail) 2007-06-06 04:43:21 UTC

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

Comment 72 palfrey 2007-06-06 10:29:01 UTC

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

Comment 73 Pascal Terjan 2007-06-10 19:47:20 UTC

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

Comment 74 Pascal Terjan 2007-06-10 19:47:35 UTC

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

Comment 75 André Klapper 2007-06-12 00:40:09 UTC

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

Comment 76 André Klapper 2007-06-12 00:40:17 UTC

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

Comment 77 André Klapper 2007-06-12 00:41:42 UTC

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

Comment 78 André Klapper 2007-06-12 00:41:49 UTC

from bug 444807:

>>
Unfortunately, order of expression evaluation is unspecified by standards in C
language. I afraid, patch
http://bugzilla.gnome.org/attachment.cgi?id=86289&action=view :

if (z_offset == offset && zone->tznames && !strcmp(tzname, zone->tznames))

may not completely resolve a crash problem, because in something combinations
of C-compilers, OS-es and optimization options may rearrange expressions
evaluation and, as a consequence, strcmp(tzname, zone->tznames) may be
evaluated before zone->tznames.

In my opinion, this code may be more safe expression:

if (zone->tznames == NULL) continue;

<<

Comment 79 André Klapper 2007-06-12 00:56:37 UTC

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

Comment 80 André Klapper 2007-06-12 00:56:46 UTC

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

Comment 81 Pascal Terjan 2007-06-12 05:24:38 UTC

(In reply to comment #78)
> from bug 444807:
> 
> Unfortunately, order of expression evaluation is unspecified by standards in C
> language

That's wrong && order is specified : all logical operators are evaluated left-to-right, stopping when the result is known (when false is met for && and when true is met for ||).

What is not specified is the order of evaluation of function arguments or arithmetic expressions.

Comment 82 André Klapper 2007-06-12 10:54:09 UTC

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

Comment 83 André Klapper 2007-06-12 10:54:14 UTC

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

Comment 84 André Klapper 2007-06-12 10:54:22 UTC

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

Comment 85 palfrey 2007-06-12 16:18:20 UTC

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

Comment 86 palfrey 2007-06-12 16:21:38 UTC

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

Comment 87 Oleg Sadov 2007-06-13 10:27:48 UTC

(In reply to comment #81)
> (In reply to comment #78)
> > from bug 444807:
> > 
> > Unfortunately, order of expression evaluation is unspecified by standards in C
> > language
> 
> That's wrong && order is specified : all logical operators are evaluated
> left-to-right, stopping when the result is known (when false is met for && and
> when true is met for ||).
> 
> What is not specified is the order of evaluation of function arguments or
> arithmetic expressions.
> 

Unfortunately, I don't have ANSI C standard near at hand now, but I think -- you are right & I am wrong ;).

Thanks for good comments, Pascal!

Comment 88 André Klapper 2007-06-13 12:02:13 UTC

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

Comment 89 André Klapper 2007-06-14 12:58:31 UTC

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

Comment 90 André Klapper 2007-06-14 12:58:37 UTC

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

Comment 91 André Klapper 2007-06-15 17:25:28 UTC

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

Comment 92 André Klapper 2007-06-15 17:25:51 UTC

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

Comment 93 André Klapper 2007-06-15 17:49:05 UTC

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

Comment 94 André Klapper 2007-06-15 23:08:00 UTC

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

Comment 95 André Klapper 2007-06-15 23:08:08 UTC

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

Comment 96 André Klapper 2007-06-17 21:20:34 UTC

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

Comment 97 André Klapper 2007-06-19 15:02:28 UTC

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

Comment 98 André Klapper 2007-06-20 10:29:56 UTC

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

Comment 99 André Klapper 2007-06-20 18:48:17 UTC

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

Comment 100 Karsten Bräckelmann 2007-06-20 20:26:18 UTC

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

Comment 101 André Klapper 2007-06-21 10:08:39 UTC

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

Comment 102 André Klapper 2007-06-21 16:18:03 UTC

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

Comment 103 André Klapper 2007-06-22 09:05:25 UTC

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

Comment 104 palfrey 2007-06-25 00:19:54 UTC

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

Comment 105 palfrey 2007-06-25 00:20:44 UTC

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

Comment 106 palfrey 2007-06-25 00:20:56 UTC

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

Comment 107 palfrey 2007-06-26 17:17:12 UTC

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

Comment 108 palfrey 2007-06-26 17:17:24 UTC

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

Comment 109 palfrey 2007-06-27 13:32:42 UTC

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

Comment 110 palfrey 2007-06-27 13:34:44 UTC

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

Comment 111 palfrey 2007-06-27 13:35:25 UTC

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

Comment 112 palfrey 2007-06-27 13:35:28 UTC

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

Comment 113 palfrey 2007-06-28 14:00:35 UTC

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

Comment 114 palfrey 2007-06-29 11:30:57 UTC

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

Comment 115 palfrey 2007-06-29 11:31:02 UTC

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

Comment 116 palfrey 2007-06-29 16:49:08 UTC

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

Comment 117 palfrey 2007-06-30 15:25:43 UTC

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

Comment 118 Karsten Bräckelmann 2007-06-30 22:26:01 UTC

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

Comment 119 Karsten Bräckelmann 2007-06-30 22:28:04 UTC

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

Comment 120 Karsten Bräckelmann 2007-07-01 18:18:06 UTC

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

Comment 121 Karsten Bräckelmann 2007-07-01 22:04:05 UTC

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

Comment 122 Karsten Bräckelmann 2007-07-02 20:09:13 UTC

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

Comment 123 Karsten Bräckelmann 2007-07-02 20:11:24 UTC

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

Comment 124 Karsten Bräckelmann 2007-07-03 13:06:22 UTC

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

Comment 125 palfrey 2007-07-06 14:46:29 UTC

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

Comment 126 palfrey 2007-07-07 21:24:21 UTC

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

Comment 127 palfrey 2007-07-07 21:28:52 UTC

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

Comment 128 palfrey 2007-07-07 21:30:19 UTC

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

Comment 129 André Klapper 2007-07-11 18:37:05 UTC

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

Comment 130 André Klapper 2007-07-11 18:39:30 UTC

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

Comment 131 André Klapper 2007-07-11 18:39:33 UTC

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

Comment 132 André Klapper 2007-07-11 18:39:36 UTC

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

Comment 133 André Klapper 2007-07-11 18:39:38 UTC

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

Comment 134 André Klapper 2007-07-11 18:39:41 UTC

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

Comment 135 André Klapper 2007-07-11 18:39:44 UTC

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

Comment 136 André Klapper 2007-07-11 18:39:55 UTC

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

Comment 137 André Klapper 2007-07-11 18:40:00 UTC

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

Comment 138 André Klapper 2007-07-11 18:40:02 UTC

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

Comment 139 André Klapper 2007-07-11 18:40:05 UTC

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

Comment 140 André Klapper 2007-07-11 18:40:08 UTC

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

Comment 141 André Klapper 2007-07-11 18:40:10 UTC

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

Comment 142 André Klapper 2007-07-11 18:40:14 UTC

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

Comment 143 André Klapper 2007-07-12 09:08:23 UTC

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

Comment 144 palfrey 2007-07-12 11:20:58 UTC

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

Comment 145 André Klapper 2007-07-12 13:26:46 UTC

The fix for this crash was committed on 2007-05-24:
http://svn.gnome.org/viewcvs/libical/branches/gnome-2-18/src/libical/icaltimezone.c?r1=591&r2=602

This fix is included in evolution-data-server version 1.10.2.

If you run Fedora 7, an updated version of evolution-data-server (containing the fix for this issue) has been available since 2007-06-16.

Comment 146 Susana 2007-07-29 23:00:35 UTC

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

Comment 147 André Klapper 2007-08-01 15:04:04 UTC

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

Comment 148 palfrey 2007-08-13 14:19:33 UTC

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

Comment 149 palfrey 2007-08-17 11:10:16 UTC

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

Comment 150 Mart Raudsepp 2007-08-23 12:14:59 UTC

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

Comment 151 André Klapper 2007-09-04 15:17:19 UTC

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

Comment 152 Suman Manjunath 2007-09-04 18:51:08 UTC

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

Comment 153 André Klapper 2007-09-10 11:21:18 UTC

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

Comment 154 Tobias Mueller 2007-12-04 15:32:42 UTC

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