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 622349 - crash in Evolution: clicked on invitation em...
crash in Evolution: clicked on invitation em...
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-22 06:14 UTC by eric
Modified: 2010-06-22 06:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30



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


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

System: Linux 2.6.33-tuxonice-r1 #1 SMP Tue Apr 20 06:26:33 CEST 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10801901
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 392638464 vsize: 392638464 resident: 149377024 share: 27615232 rss: 149377024 rss_rlim: 18446744073709551615
CPU usage: start_time: 1277186779 rtime: 3165 utime: 2950 stime: 215 cutime:32 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xacc96b70 (LWP 31226)]
[New Thread 0xa56a1b70 (LWP 31224)]
[New Thread 0xa05ffb70 (LWP 31223)]
[New Thread 0xaec2eb70 (LWP 30941)]
[New Thread 0xa7ea6b70 (LWP 30940)]
[New Thread 0xa8afbb70 (LWP 30917)]
[New Thread 0xa92fcb70 (LWP 30916)]
[New Thread 0xabc28b70 (LWP 30915)]
[New Thread 0xa9afdb70 (LWP 30914)]
[New Thread 0xaa2feb70 (LWP 30913)]
[New Thread 0xaaaffb70 (LWP 30912)]
[New Thread 0xab427b70 (LWP 30911)]
[New Thread 0xacc2ab70 (LWP 30908)]
[New Thread 0xadc2cb70 (LWP 30906)]
[New Thread 0xae42db70 (LWP 30905)]
[New Thread 0xaf42fb70 (LWP 30902)]
[New Thread 0xafc30b70 (LWP 30901)]
[New Thread 0xb0457b70 (LWP 30899)]
[New Thread 0xb0c58b70 (LWP 30898)]
0xb77ed424 in __kernel_vsyscall ()

Thread 3 (Thread 0xa56a1b70 (LWP 31224))

  • #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 30896] 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 (2467 sec old) ---------------------
(epiphany:14890): Gtk-CRITICAL **: gtk_tree_model_sort_real_unref_node: assertion `elt->ref_count > 0' failed
(epiphany:14890): Gtk-CRITICAL **: gtk_tree_model_filter_real_unref_node: assertion `elt->ref_count > 0' failed
** Message: console message: http://static.ubuntuusers.de/js/forum.js @168: SyntaxError: Parse error
Loading stream: http://s0.2mdn.net/2326319/Toner_caution_DE_300x250.swf
Loading stream: http://s0.2mdn.net/2326319/Toner_caution_DE_300x250.swf
Loading stream: http://s0.2mdn.net/1658458/1007_Alice_Light_ohneMVLZ_160x600.swf
Loading stream: http://s0.2mdn.net/2326319/Toner_caution_DE_300x250.swf
Loading stream: http://s0.2mdn.net/1658458/1007_Alice_Light_ohneMVLZ_160x600.swf
** Message: console message: http://gogrid.cedexis.com/cdn5.js?rnd=2395410552 @1: SyntaxError: Parse error
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Akhil Laddha 2010-06-22 06:41:34 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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