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 573558 - crash in Evolution Mail and Calendar: Reading mail
crash in Evolution Mail and Calendar: Reading mail
Status: RESOLVED DUPLICATE of bug 569700
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.24.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-02-28 18:20 UTC by Braden
Modified: 2009-02-28 18:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Braden 2009-02-28 18:20:59 UTC
What were you doing when the application crashed?
Reading mail


Distribution: Fedora release 10 (Cambridge)
Gnome Release: 2.24.3 2009-01-16 (Red Hat, Inc)
BugBuddy Version: 2.24.2

System: Linux 2.6.27.15-170.2.24.fc10.x86_64 #1 SMP Wed Feb 11 23:14:31 EST 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: gnome

Memory status: size: 746528768 vsize: 746528768 resident: 74739712 share: 21422080 rss: 74739712 rss_rlim: 18446744073709551615
CPU usage: start_time: 1235845113 rtime: 307 utime: 259 stime: 48 cutime:1 cstime: 10 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7f3e7425e7e0 (LWP 11595)]
[New Thread 0x7f3e6881f950 (LWP 11679)]
[New Thread 0x7f3e5b5c8950 (LWP 11678)]
[New Thread 0x7f3e62d46950 (LWP 11676)]
[New Thread 0x7f3e63fff950 (LWP 11622)]
0x000000359620ec2f in __libc_waitpid (pid=11684, stat_loc=0x7fff7c2aaf50, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

Thread 4 (Thread 0x7f3e62d46950 (LWP 11676))

  • #0 __lll_lock_wait
    at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S line 130
  • #1 _L_lock_102
    from /lib64/libpthread.so.0
  • #2 __pthread_mutex_lock
    at pthread_mutex_lock.c line 86
  • #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 525
  • #7 efh_format_exec
    at em-format-html.c line 1299
  • #8 mail_msg_proxy
    at mail-mt.c line 520
  • #9 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #10 g_thread_create_proxy
    at gthread.c line 635
  • #11 start_thread
    at pthread_create.c line 297
  • #12 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 112


----------- .xsession-errors (6632618 sec old) ---------------------
** (gnome-panel:3565): WARNING **: panel-applet-frame.c:1285: failed to load applet OAFIID:SensorsApplet:
(null)
** (gnome-panel:3565): WARNING **: Failed to establish a connection with GDM: No such file or directory
Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-4001-2094043385-1229212449 --active --geometry 80x24+285+108 --title braden@hinge:/home/br
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus 0x1600237 (LaCie) with a timestamp of 0.  This shouldn't happen!
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!
kerneloops-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
bluetooth-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
applet.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
gpk-update-icon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2009-02-28 18:40:44 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 569700 ***