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 318104 - evolution crashed when changing calendar timezone and keeps crashing
evolution crashed when changing calendar timezone and keeps crashing
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other other
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 318101 (view as bug list)
Depends on:
Blocks: 318200
 
 
Reported: 2005-10-06 11:21 UTC by Vladimir Mencl
Modified: 2008-08-07 03:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Vladimir Mencl 2005-10-06 11:21:10 UTC
Distribution: Fedora Core release 4 (Stentz)
Package: Evolution
Severity: normal
Version: GNOME2.10.0 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: evolution crashed when changing calendar timezone and keeps crashing
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:

I changed the calendar timezone from Europe/Prague to Asia/Macau (via
Evolution Preferences).

I had some data in the calendar, I had open the calendar in the
clock-applet (I started evolution from the clock-applet).
The system timezone already is Asia/Macau, originally, it was
Europe/Prague.

When I changed the timezone, both Evolution and Clock Applet crashed.

Now, Evolution keeps crashing upon start up.
Also, Clock Applet crashes when I open the calendar.

Steps to reproduce the crash:
1. Start evolution under my account.
2. 
3. 

Expected Results:
Evolution started.

How often does this happen?
100%

Additional Information:
Contact me at mencl@nenya.ms.mff.cuni.cz





Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209129280 (LWP 32305)]
[New Thread -1211835472 (LWP 32313)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x00a67402 in ?? ()

Thread 1 (Thread -1209129280 (LWP 32305))

  • #0 ??
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 es_menu_hook_get_type
  • #4 <signal handler called>
  • #5 e_cal_set_default_timezone
    from /usr/lib/libecal-1.2.so.2
  • #6 gnome_calendar_view_popup_factory
    from /usr/lib/evolution/2.2/components/libevolution-calendar.so
  • #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 g_signal_stop_emission
    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 e_cal_open
    from /usr/lib/libecal-1.2.so.2
  • #13 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #17 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #18 main




------- Bug moved to this database by unknown@gnome.bugs 2005-10-06 11:21 UTC -------

Comment 1 Chakravarthi 2005-10-20 12:33:14 UTC
I have tried and failed to replicate this on evo 2.4.1.
Heres is what I did
1) I went to Edit->Preferences my timezone from "Asia/Calcutta" to 
  "America/Denver" and observed that all appointments got shifted by 
   around 12 hrs (as expected)
2) Then i shutdown evolution and clicked on a date in clock applet.
   i got evo calendar opened due to this ..with my "America/Denver" 
   timezone effect still intact.
   Nothing happened... no crash.
Then I tried the same without shutting down evo .. i got 2 calendar views
which are exactly same with "America/Denver" timezone appointments intact.

Is there something I'm missing .. ?

Comment 2 Vladimir Mencl 2005-10-20 14:08:00 UTC
I have tried to reproduce it on my system.

Unfortunately, I suceeded. 

I changed my Evolution timezone to Europe/Prague. I saw all the events
rescheduled. Afterwards, I clicked to change my timezone to Asia/Macau, and the
crash happened again.

There may be a particular problem with the definition of the Asia/Macau
timezone, and evolution crashes when it is changed to this zone.

Please note that I had found no way to recover my Evolution database from the
crash, and I had to delete everything I had there (not really a lot), and start
a clean database.

If you need it for debugging, I can send you my evolution database, there's
nothing really confidential or personal there.

Please note that the version I use is evolution-2.2.3-2.fc4
- the latest update released for FC4.
Comment 3 Vladimir Mencl 2005-10-21 11:15:00 UTC
BTW, I found how to recover from the error.

After reproducing the error, I was again in the situation when Evolution crashed
immediately after started, and I could not access my data, and neither could I
change the timezone to something else then Asia/Macau.

I solved the problem by running

evolution -c=Mail

- asking Evolution to start with component mail. Which is not a valid component
name, but it at least prevented Evolution from opening the calendar. I could go
to Preferences=> Calendar=> Timezone.

I changed the timezone from Asia/Macau to Asia/Hong_Kong - which is at all times
the same, and Evolution works for me again.

Apparently, the Asia/Macau timezone definition is corrupted.

My system is a regularly updated Fedora Core 4 (with all updates released in
FC4-updates as far as 2005-10-19).

The versions of relevant packages on my system are:

tzdata-2005m-1.fc4
evolution-data-server-1.2.3-3.fc4
evolution-data-server-devel-1.2.3-3.fc4
evolution-devel-2.2.3-2.fc4
evolution-2.2.3-2.fc4

I have checked that these packages are not corrupt; 
rpm --verify tzdata-2005m-1.fc4 evolution-data-server-1.2.3-3.fc4
evolution-data-server-devel-1.2.3-3.fc4 evolution-devel-2.2.3-2.fc4
evolution-2.2.3-2.fc4

does not print any error.

I have reproduced the error: changing timezone from Asia/Hong_Kong to Asia/Macau
causes Evolution to crash upon opening calendar; changing it back solves the
problem.

Comment 4 Chakravarthi 2005-10-22 04:22:27 UTC
thanx. I too get the crash with "Asia/Macau"
Will look into it as soon as possible.
Assigning it to myself.
Comment 5 Chakravarthi 2005-10-22 08:54:17 UTC
*** Bug 318101 has been marked as a duplicate of this bug. ***
Comment 6 Chakravarthi 2005-10-22 08:59:02 UTC
This bug and the likes (e.g. 318101) are due to a spelling mistake
timezone information

Please follow the steps given below to get rid of this bug
1) Locate for Macao.ics (yes ... not Macau) file in your installation area.
2) Once u find it, rename it to Macau.ics 
3) open this renamed file, change all instances of Macao to Macau.
4) Locate for a zones.tab file and change the spelling if necessary .. there too.

restart evolution.
Comment 7 Vladimir Mencl 2005-10-22 10:36:28 UTC
Thank you, the solution works for me.

:-) please not that I would not call it a spelling mistake but rather a spelling
inconsistency - both Macao and Macau and correct spellings, the first one in
English and the second one in Portuguese.

Quoting from http://en.wikipedia.org/wiki/Macau#Names

<quote>
The form "Macao" was the original Portuguese spelling, and has been retained in
most European languages. In modern Portuguese, the correct spelling is "Macau".
During the 20th century, the official spelling "Macau" became more and more
common in English-language sources, including most print media.

Since the handover of sovereignty, the government of Macau considers "Macao" the
official English spelling of the name, whereas "Macau" remains the official
spelling in Portuguese. This is the practice followed in official documents such
as passports and immigration forms.
</quote>


Of course, the bottom line is that from the programming point of view, the
spelling must be consistent. I do not know what the policy is: whether the
zonename should be the English spelling or the spelling in the local language.

As a suggestion to prevent similar problems in the future: Shouldn't Evolution
do some sanity checks to avoid a crash in case the timezone definition is not found?
Comment 8 Chakravarthi 2005-10-25 10:21:47 UTC
I agree, it is generally the case that sanity checks are done.
We just happened to overlook this one.
the code here will be cleaned now to avoid crashes.. thank you.
Comment 9 Chakravarthi 2005-10-25 10:26:17 UTC
in evo 2.5.2
Comment 10 Suman Manjunath 2008-08-06 05:02:02 UTC
Is this still a valid issue?

Could you please check if this has been fixed with the latest stable release (2.22.x)?
Comment 11 Vladimir Mencl 2008-08-06 22:45:52 UTC
I believe it's not an issue anymore.  Just from looking at my Evolution installation, it does not look like Evolution installs individual timezone ICS files anymore.  I don't know if it now relies on systemwide timezone database - but I think the issue is now long gone.  I think it's safe to close the issue now.

Cheers,
Vladimir
Comment 12 Suman Manjunath 2008-08-07 03:05:36 UTC
Yes.. Evolution uses system timezone information since the 2.12 series.