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 623141 - crash in Evolution: clicked on meeting invit...
crash in Evolution: clicked on meeting invit...
Status: RESOLVED DUPLICATE of bug 619959
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.30.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-06-29 14:42 UTC by eric
Modified: 2010-06-29 15:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30


Description eric 2010-06-29 14:42:47 UTC 
What were you doing when the application crashed?
clicked on meeting invitation


Distribution: Gentoo Base System release 2.0.1
Gnome Release: 2.30.2 2010-06-22 (Gentoo)
BugBuddy Version: 2.30.0

System: Linux 2.6.34-tuxonice #1 SMP Mon Jun 28 16:17:25 CEST 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10801902
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 400056320 vsize: 400056320 resident: 147886080 share: 26812416 rss: 147886080 rss_rlim: 18446744073709551615
CPU usage: start_time: 1277822489 rtime: 2363 utime: 2243 stime: 120 cutime:31 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xae878b70 (LWP 8964)]
[New Thread 0xa642cb70 (LWP 8962)]
[New Thread 0xa742eb70 (LWP 8922)]
[New Thread 0xa8430b70 (LWP 8921)]
[New Thread 0xa8dffb70 (LWP 8897)]
[New Thread 0xa99f2b70 (LWP 8896)]
[New Thread 0xaa1f3b70 (LWP 8895)]
[New Thread 0xaa9f4b70 (LWP 8894)]
[New Thread 0xab1f5b70 (LWP 8893)]
[New Thread 0xab9f6b70 (LWP 8892)]
[New Thread 0xac1f7b70 (LWP 8891)]
[New Thread 0xad1f9b70 (LWP 8890)]
[New Thread 0xac9f8b70 (LWP 8889)]
[New Thread 0xad9fab70 (LWP 8887)]
[New Thread 0xae1fbb70 (LWP 8886)]
[New Thread 0xaf1fdb70 (LWP 8884)]
[New Thread 0xaf9feb70 (LWP 8883)]
[New Thread 0xb01ffb70 (LWP 8882)]
[New Thread 0xb40b4b70 (LWP 8881)]
0xb775f424 in __kernel_vsyscall ()

+ Trace 222641

Thread 3 (Thread 0xa642cb70 (LWP 8962))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_lock_501
    from /lib/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #4 <signal handler called>
  • #5 format_itip
    from /usr/lib/evolution/2.30/plugins/liborg-gnome-itip-formatter.so
  • #6 plugin_lib_invoke
    from /usr/lib/evolution/2.30/modules/libevolution-module-plugin-lib.so
  • #7 e_plugin_invoke
    from /usr/lib/evolution/2.30/libeutil.so.0
  • #8 emfh_format_format
    from /usr/lib/evolution/2.30/libevolution-mail.so.0
  • #9 em_format_part_as
    from /usr/lib/evolution/2.30/libemformat.so.0
  • #10 em_format_part
    from /usr/lib/evolution/2.30/libemformat.so.0
  • #11 emf_multipart_alternative
    from /usr/lib/evolution/2.30/libemformat.so.0
  • #12 org_gnome_prefer_plain_multipart_alternative
    from /usr/lib/evolution/2.30/plugins/liborg-gnome-prefer-plain.so
  • #13 plugin_lib_invoke
    from /usr/lib/evolution/2.30/modules/libevolution-module-plugin-lib.so
  • #14 e_plugin_invoke
    from /usr/lib/evolution/2.30/libeutil.so.0
  • #15 emfh_format_format
    from /usr/lib/evolution/2.30/libevolution-mail.so.0
  • #16 em_format_part_as
    from /usr/lib/evolution/2.30/libemformat.so.0
  • #17 em_format_part
    from /usr/lib/evolution/2.30/libemformat.so.0
  • #18 efh_multipart_related
    from /usr/lib/evolution/2.30/libevolution-mail.so.0
  • #19 em_format_part_as
    from /usr/lib/evolution/2.30/libemformat.so.0
  • #20 em_format_part
    from /usr/lib/evolution/2.30/libemformat.so.0
  • #21 emf_multipart_mixed
    from /usr/lib/evolution/2.30/libemformat.so.0
  • #22 em_format_part_as
    from /usr/lib/evolution/2.30/libemformat.so.0
  • #23 em_format_part
    from /usr/lib/evolution/2.30/libemformat.so.0
  • #24 efh_format_message
    from /usr/lib/evolution/2.30/libevolution-mail.so.0
  • #25 efh_format_exec
    from /usr/lib/evolution/2.30/libevolution-mail.so.0
  • #26 mail_msg_proxy
    from /usr/lib/evolution/2.30/libevolution-mail.so.0
  • #27 g_thread_pool_thread_proxy
    from /usr/lib/libglib-2.0.so.0
  • #28 g_thread_create_proxy
    from /usr/lib/libglib-2.0.so.0
  • #29 start_thread
    from /lib/libpthread.so.0
  • #30 clone
    from /lib/libc.so.6 
A debugging session is active.

	Inferior 1 [process 8877] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


---- Critical and fatal warnings logged during execution ----

** libecal **: e_cal_util_get_system_timezone: assertion `location != NULL' failed 


----------- .xsession-errors (39 sec old) ---------------------
** (epiphany:6519): DEBUG: NP_Initialize
** (epiphany:6519): DEBUG: NP_Initialize succeeded
** (epiphany:6519): DEBUG: NP_Initialize
** (epiphany:6519): DEBUG: NP_Initialize succeeded
** (epiphany:6519): DEBUG: NP_Initialize
** (epiphany:6519): DEBUG: NP_Initialize succeeded
** (epiphany:6519): DEBUG: NP_Initialize
** (epiphany:6519): DEBUG: NP_Initialize succeeded
(evolution:25653): camel-WARNING **: Camel operation status stack non empty: 
(evolution:8877): e-data-server-DEBUG: Loading categories from "/home/eric/.evolution/categories.xml"
(evolution:8877): e-data-server-DEBUG: Loaded 29 categories
(evolution:8877): libecal-CRITICAL **: e_cal_util_get_system_timezone: assertion `location != NULL' failed
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2010-06-29 15:19:35 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


The fix is in 2.30.3

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