Bug 457830 – crash in Tasks: opening email to read in...

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 457830 - crash in Tasks: opening email to read in...


Summary:	crash in Tasks: opening email to read in...


Status:	RESOLVED DUPLICATE of bug 405646

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-18 03:17 UTC by bbell
Modified:	2007-08-01 15:03 UTC

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

Description bbell 2007-07-18 03:17:56 UTC

Version: 2.10

What were you doing when the application crashed?
opening email to read in evolution


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: 130924544 vsize: 130924544 resident: 50184192 share: 33247232 rss: 50184192 rss_rlim: 4294967295
CPU usage: start_time: 1184707407 rtime: 2151 utime: 1984 stime: 167 cutime:37 cstime: 20 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 -1208555808 (LWP 3293)]
[New Thread -1325601904 (LWP 4655)]
[New Thread -1251779696 (LWP 4259)]
[New Thread -1262269552 (LWP 4257)]
[New Thread -1219454064 (LWP 3332)]
(no debugging symbols found)
0x005f6402 in __kernel_vsyscall ()

+ Trace 148738

Thread 5 (Thread -1219454064 (LWP 3332))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#2 _L_mutex_lock_79
from /lib/libpthread.so.0
#3 pthread_mutex_lock
from /lib/libpthread.so.0
#4 ??
#5 <signal handler called>
#6 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 ??
from /lib/libglib-2.0.so.0
#9 __nptl_deallocate_tsd
from /lib/libpthread.so.0
#10 start_thread
from /lib/libpthread.so.0
#11 clone
from /lib/libc.so.6



----------- .xsession-errors (4760 sec old) ---------------------
(evolution:3293): libebook-WARNING **: invalid escape, passing it through
(evolution:3293): libebook-WARNING **: invalid escape, passing it through
(evolution:3293): libebook-WARNING **: invalid escape, passing it through
(evolution:3293): libebook-WARNING **: invalid escape, passing it through
(evolution:3293): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:3293): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa1da128'
(evolution:3293): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa1da248'
--------------------------------------------------

Comment 1 André Klapper 2007-08-01 15:03:42 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 405646 ***