Bug 390984 – crash in Evolution:

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 390984 - crash in Evolution:


Summary:	crash in Evolution:


Status:	RESOLVED DUPLICATE of bug 390574

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

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-30 14:39 UTC by Albert Hopkins
Modified:	2006-12-30 14:40 UTC

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

Description Albert Hopkins 2006-12-30 14:39:05 UTC

Version: 2.10.x

What were you doing when the application crashed?



Distribution: Gentoo Base System version 1.12.8
Gnome Release: 2.17.2 2006-12-30 (Gentoo)
BugBuddy Version: 2.17.3

System: Linux 2.6.19.1 #1 SMP PREEMPT Thu Dec 28 22:27:12 CST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Enabled

Memory status: size: 98070528 vsize: 0 resident: 98070528 share: 0 rss: 22892544 rss_rlim: 0
CPU usage: start_time: 1167489195 rtime: 0 utime: 112 stime: 0 cutime:99 cstime: 0 timeout: 13 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1230166352 (LWP 14142)]
[New Thread -1272972400 (LWP 14154)]
[New Thread -1283458160 (LWP 14153)]
[New Thread -1263219824 (LWP 14151)]
[New Thread -1253672048 (LWP 14150)]
[New Thread -1245238384 (LWP 14148)]
0xb7fc6410 in __kernel_vsyscall ()

+ Trace 98024

Thread 1 (Thread -1230166352 (LWP 14142))

#0 __kernel_vsyscall
#1 ??
from /lib/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 870
#3 <signal handler called>
#4 __kernel_vsyscall
#5 *__GI_raise
at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
#6 *__GI_abort
at abort.c line 88
#7 IA__g_logv
at gmessages.c line 497
#8 IA__g_log
at gmessages.c line 517
#9 IA__g_return_if_fail_warning
#10 IA__gtk_check_menu_item_set_active
at gtkcheckmenuitem.c line 193
#11 e_search_bar_set_item_menu
at e-search-bar.c line 1381
#12 set_property
at e-filter-bar.c line 752
#13 IA__g_object_set_valist
at gobject.c line 697
#14 IA__g_object_set
at gobject.c line 1207
#15 emfb_set_folder
at em-folder-browser.c line 1888
#16 emfv_got_folder
at em-folder-view.c line 691
#17 get_folder_got
at mail-ops.c line 1230
#18 mail_msgport_replied
at mail-mt.c line 473
#19 g_io_unix_dispatch
at giounix.c line 162
#20 IA__g_main_context_dispatch
at gmain.c line 2045
#21 g_main_context_iterate
at gmain.c line 2677
#22 IA__g_main_loop_run
at gmain.c line 2881
#23 bonobo_main
at bonobo-main.c line 311
#24 main
at main.c line 617
#25 __libc_start_main
at libc-start.c line 238
#26 _start
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
(gnome_segv2:14155): Gnome-WARNING **: Accessibility: failed to find module 'libgail-gnome' which is needed to make this application accessible
(gnome_segv2:14155): Gnome-WARNING **: Accessibility: failed to find module 'libatk-bridge' which is needed to make this application accessible
Gtk-Message: Failed to load module "atk-bridge": libatk-bridge.so: cannot open shared object file: No such file or directory
GTK Accessibility Module initialized
(bug-buddy:14156): Gnome-WARNING **: Accessibility: failed to find module 'libgail-gnome' which is needed to make this application accessible
(bug-buddy:14156): Gnome-WARNING **: Accessibility: failed to find module 'libatk-bridge' which is needed to make this application accessible
(bug-buddy:14156): Gtk-WARNING **: Theme directory scalable/mimetypes of theme random-eXperienceCrystal-1167489134.19 has no size field
Cannot access memory at address 0x373e
Cannot access memory at address 0x373e
--------------------------------------------------

Comment 1 Albert Hopkins 2006-12-30 14:40:12 UTC

Accidentally opened this bug.

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