Bug 509266 – crash in Email: Nothing

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 509266 - crash in Email: Nothing


Summary:	crash in Email: Nothing


Status:	RESOLVED DUPLICATE of bug 447591

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.10.x (obsolete)
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-14 01:11 UTC by hklee
Modified:	2008-02-25 06:35 UTC

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

Description hklee 2008-01-14 01:11:07 UTC

Version: 2.10

What were you doing when the application crashed?
Nothing


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

System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 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: 165789696 vsize: 165789696 resident: 64573440 share: 45633536 rss: 64573440 rss_rlim: 4294967295
CPU usage: start_time: 1200269979 rtime: 1903 utime: 1548 stime: 355 cutime:8002 cstime: 635 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 -1208215840 (LWP 3718)]
[New Thread -1225090160 (LWP 5888)]
[New Thread -1326548080 (LWP 4996)]
[New Thread -1247810672 (LWP 3745)]
[New Thread -1235973232 (LWP 3744)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 185227

Thread 2 (Thread -1225090160 (LWP 5888))

#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 __nptl_deallocate_tsd
from /lib/libpthread.so.0
#9 start_thread
from /lib/libpthread.so.0
#10 clone
from /lib/libc.so.6



----------- .xsession-errors (47 sec old) ---------------------
report junk?? Satisfactory sexual intercourse
report junk?? ematihs
report junk?? mmletise
error getting update info:  Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again
(evolution:3718): Gtk-CRITICAL **: gtk_toggle_button_get_active: assertion `GTK_IS_TOGGLE_BUTTON (toggle_button)' failed
(evolution:3718): 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:3718): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x97ef018'
(evolution:3718): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x97ef138'
--------------------------------------------------

Comment 1 Tobias Mueller 2008-02-25 06:35:58 UTC

Dear Reporter,

thanks for you bugreport :)
This particular bug is very likely to
be the fedora specific bug 447591 where 
   GLib-GObject-WARNING **: gsignal.c:1669: signal
   `source_selected' is invalid for instance
indicates some memory corruption. Hence marking this as dup of bug 447591.

Feel free to report more bugs ;-)

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