GNOME Bugzilla – Bug 485311
crash in icaltimezone_init_builtin_timezones () at icaltimezone.c:1610
Last modified: 2009-02-27 15:12:37 UTC
What were you doing when the application crashed? edit-preferences Distribution: Debian lenny/sid Gnome Release: 2.20.0 2007-09-21 (Debian) BugBuddy Version: 2.20.0 System: Linux 2.6.11-1-k7 #1 Mon Jun 20 21:26:23 MDT 2005 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 76369920 vsize: 76369920 resident: 26558464 share: 17117184 rss: 26558464 rss_rlim: 4294967295 CPU usage: start_time: 1192006009 rtime: 197 utime: 179 stime: 18 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb697b6b0 (LWP 3094)] [New Thread 0xb4906b90 (LWP 3161)] [New Thread 0xb5115b90 (LWP 3159)] [New Thread 0xb5985b90 (LWP 3158)] [New Thread 0xb61e1b90 (LWP 3157)] 0xb7901bf1 in waitpid () from /lib/libpthread.so.0
+ Trace 169200
Thread 1 (Thread 0xb697b6b0 (LWP 3094))
----------- .xsession-errors (88219 sec old) --------------------- icewm-session: Warning: Closing file descriptor: 5 icewm-session: Warning: File still open: fd=7, target='pipe:[3864]' (missing FD_CLOEXEC?) icewm-session: Warning: Closing file descriptor: 7 icewm-session: Warning: File still open: fd=5, target='pipe:[3860]' (missing FD_CLOEXEC?) icewm-session: Warning: Closing file descriptor: 5 icewm-session: Warning: File still open: fd=7, target='pipe:[3864]' (missing FD_CLOEXEC?) icewm-session: Warning: Closing file descriptor: 7 icewm-session: Warning: File still open: fd=5, target='pipe:[3860]' (missing FD_CLOEXEC?) icewm-session: Warning: Closing file descriptor: 5 icewm-session: Warning: File still open: fd=7, target='pipe:[3864]' (missing FD_CLOEXEC?) icewm-session: Warning: Closing file descriptor: 7 icewm-session: using /home/michael/.icewm for private configuration files IceWM: using /home/michael/.icewm for private configuration files icewmtray: using /home/michael/.icewm for private configuration files icewmbg: using /home/michael/.icewm for private configuration files --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 485310 ***
485310 is not the same as this report - this one relates to once opened that evolution crashes later when edit-preferences is chosen; the other to evolution "crashing" when trying to open the application (it doesn't crash completely since I can then check some accounts etc)
Created attachment 97020 [details] fuller stack trace
(In reply to comment #2) > 485310 is not the same as this report - this one relates to once opened that > evolution crashes later when edit-preferences is chosen; the other to evolution > "crashing" when trying to open the application (it doesn't crash completely > since I can then check some accounts etc) > I think the reason for the crashers are the same. Both stacktraces show a function in libecal-1.2.so.7 and then strlen just before the crash happens. Even the stacktraces you attached to both bugs match in three functions :) Both show
+ Trace 169602
whereas bug 485310 doesn't have these functions.
Can you check if you have any of these directories on your system, please? "/usr/share/zoneinfo", "/usr/lib/zoneinfo", "/etc/zoneinfo", "/usr/share/lib/zoneinfo" I guess you do not have any of these, thus icaltzutil_get_zone_directory returns NULL. Chen, what do you think?
dup of bug 492426 ?
Akhil, hmm, probably not, that one was for a first time run, but here he has filled "Europe/London" location already. But I can be wrong, that's right.
*** Bug 485310 has been marked as a duplicate of this bug. ***
I recalled that there were some changes around this, the builtin table of timezones is more or less "static", and on some places these has been freed, thus accessing it next time can do anything. Thus I believe all this is related to the bug #475781 which introduced bug #523402 and probably this one too. Does it make sense? Aka can you reproduce on actual stable evolution 2.22.x?
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME 2.22.3.1, thanks.
*** Bug 514357 has been marked as a duplicate of this bug. ***
*** Bug 573116 has been marked as a duplicate of this bug. ***