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 610517 - crash in Evolution Mail and Calendar: No interaction
crash in Evolution Mail and Calendar: No interaction
Status: RESOLVED DUPLICATE of bug 569700
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.24.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-02-20 09:22 UTC by marcus.pedersen
Modified: 2010-02-20 20:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description marcus.pedersen 2010-02-20 09:22:47 UTC 
What were you doing when the application crashed?
No interaction


Distribution: Debian squeeze/sid
Gnome Release: 2.26.1 2009-04-14 (Debian)
BugBuddy Version: 2.24.2

System: Linux 2.6.26-2-amd64 #1 SMP Thu Feb 11 00:59:32 UTC 2010 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10601000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 651972608 vsize: 651972608 resident: 33263616 share: 19791872 rss: 33263616 rss_rlim: 18446744073709551615
CPU usage: start_time: 1266656660 rtime: 489 utime: 430 stime: 59 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7faaf43607f0 (LWP 3689)]
[New Thread 0x7faad11f6950 (LWP 3895)]
[New Thread 0x7faacfd8b950 (LWP 3894)]
[New Thread 0x7faad39fb950 (LWP 3893)]
[New Thread 0x7faad8817950 (LWP 3772)]
[New Thread 0x7faad9222950 (LWP 3706)]
[New Thread 0x7faad9a23950 (LWP 3701)]
0x00007faaef75031f in waitpid () from /lib/libpthread.so.0

+ Trace 220652

Thread 5 (Thread 0x7faad8817950 (LWP 3772))

  • #0 __lll_lock_wait
    from /lib/libpthread.so.0
  • #1 _L_lock_102
    from /lib/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #3 <signal handler called>
  • #4 camel_mime_parser_read
    at camel-mime-parser.c line 655
  • #5 stream_read
    at camel-http-stream.c line 487
  • #6 emfh_gethttp
    at em-format-html.c line 529
  • #7 efh_format_exec
    at em-format-html.c line 1302
  • #8 mail_msg_proxy
    at mail-mt.c line 520
  • #9 g_thread_pool_thread_proxy
    at /tmp/buildd/glib2.0-2.20.1/glib/gthreadpool.c line 265
  • #10 g_thread_create_proxy
    at /tmp/buildd/glib2.0-2.20.1/glib/gthread.c line 635
  • #11 start_thread
    from /lib/libpthread.so.0
  • #12 clone
    from /lib/libc.so.6
  • #13 ?? 


----------- .xsession-errors (11 sec old) ---------------------
(npviewer.bin:4643): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: fel ELF-klass: ELFCLASS64
(npviewer.bin:4643): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: fel ELF-klass: ELFCLASS64
(npviewer.bin:4643): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: fel ELF-klass: ELFCLASS64
(npviewer.bin:4643): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: fel ELF-klass: ELFCLASS64
(npviewer.bin:4643): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: fel ELF-klass: ELFCLASS64
(npviewer.bin:4643): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: fel ELF-klass: ELFCLASS64
(npviewer.bin:4643): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: fel ELF-klass: ELFCLASS64
Gtk-Message: Failed to load module "gnomebreakpad": /usr/lib/gtk-2.0/modules/libgnomebreakpad.so: fel ELF-klass: ELFCLASS64
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2010-02-20 20:32:17 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.

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