Bug 458282 – crash in Tasks: R?ception mails

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 458282 - crash in Tasks: R?ception mails


Summary:	crash in Tasks: R?ception mails


Status:	RESOLVED DUPLICATE of bug 444079

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-07-19 12:23 UTC by Lionel.Desrayaux
Modified:	2007-07-19 15:20 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description Lionel.Desrayaux 2007-07-19 12:23:14 UTC

Version: 2.10

What were you doing when the application crashed?
Réception mails


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 185708544 vsize: 185708544 resident: 92946432 share: 34344960 rss: 92946432 rss_rlim: 4294967295
CPU usage: start_time: 1184845385 rtime: 10837 utime: 8241 stime: 2596 cutime:40 cstime: 18 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208396064 (LWP 4197)]
[New Thread -1356870768 (LWP 6610)]
[New Thread -1264977008 (LWP 4271)]
[New Thread -1231737968 (LWP 4266)]
[New Thread -1220727920 (LWP 4222)]
(no debugging symbols found)
0x006d0402 in __kernel_vsyscall ()

+ Trace 149083

Thread 1 (Thread -1208396064 (LWP 4197))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 ??
from /lib/libglib-2.0.so.0
#6 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 g_slice_free_chain_with_offset
from /lib/libglib-2.0.so.0
#9 g_slist_free
from /lib/libglib-2.0.so.0
#10 ??
from /usr/lib/libpango-1.0.so.0
#11 pango_layout_set_text
from /usr/lib/libpango-1.0.so.0
#12 ??
from /usr/lib/evolution/2.10/libemiscwidgets.so.0
#13 e_clipped_label_set_text
from /usr/lib/evolution/2.10/libemiscwidgets.so.0
#14 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#15 ??
from /lib/libglib-2.0.so.0
#16 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#17 ??
from /lib/libglib-2.0.so.0
#18 g_main_loop_run
from /lib/libglib-2.0.so.0
#19 bonobo_main
from /usr/lib/libbonobo-2.so.0
#20 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
warning: .dynamic section for "/usr/lib/libnss3.so" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/lib/libselinux.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libsoftokn3.so" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/librsvg-2.so.2" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------

Comment 1 palfrey 2007-07-19 15:20:46 UTC

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 444079 ***