Bug 450381 – crash in Email: niente

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 450381 - crash in Email: niente


Summary:	crash in Email: niente


Status:	RESOLVED DUPLICATE of bug 432796

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-06-23 15:52 UTC by filippovalle
Modified:	2007-07-01 18:01 UTC

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

Description filippovalle 2007-06-23 15:52:13 UTC

Version: 2.10

What were you doing when the application crashed?
niente


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (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: Glossy P
Icon Theme: Fedora

Memory status: size: 126005248 vsize: 126005248 resident: 52355072 share: 37003264 rss: 52355072 rss_rlim: 4294967295
CPU usage: start_time: 1182613139 rtime: 1983 utime: 1767 stime: 216 cutime:85 cstime: 109 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 -1208617248 (LWP 3135)]
[New Thread -1357796464 (LWP 3722)]
[New Thread -1229145200 (LWP 3233)]
[New Thread -1326326896 (LWP 3229)]
(no debugging symbols found)
0x008d7402 in __kernel_vsyscall ()

+ Trace 143145

Thread 4 (Thread -1326326896 (LWP 3229))

#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 (61 sec old) ---------------------
(evolution:3135): 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:3135): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9c37008'
(evolution:3135): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9c37128'
(evolution:3135): e-data-server-ui-WARNING **: Il file chiavi non presenta la chiave "pop:__valle.fil%40tiscali.it@pop.tiscali.it_"
Loading "installonlyn" plugin
(evolution:3135): 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?)
(evolution:3135): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9c37248'
(evolution:3135): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9c37368'
--------------------------------------------------

Comment 1 Karsten Bräckelmann 2007-07-01 18:01:19 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 432796 ***