Bug 273594 – mail component started crashing

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 273594 - mail component started crashing


Summary:	mail component started crashing


Status:	RESOLVED DUPLICATE of bug 132551

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.0.x (obsolete)
Hardware:	Other All

Importance:	Normal major
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2005-03-11 14:53 UTC by Kaj-Michael Lang
Modified:	2005-04-09 23:14 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Kaj-Michael Lang 2005-03-11 14:53:36 UTC

Distribution: Unknown
Package: Evolution
Priority: Major
Version: GNOME2.8.3 2.0.4
Gnome-Distributor: TA-Linux
Synopsis: mail component started crashing
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous
Bugzilla-Version: 2.0.4
BugBuddy-GnomeVersion: 2.0 (2.8.1)
Description:
Description of the crash:
Evolution mail view started to crash with the message:

** ERROR **: file gailtreeview.c: line 2277 (idle_expand_row): should
not be reched

on the console.

Steps to reproduce the crash:
1. Start evolution
2. Select mail component
3. 

Expected Results:
Be able to read my mail.

How often does this happen?
Started to happen suddenly. Sometimes it works just fine, but mostly it
just crashes.

Additional Information:



Debugging Information:

Backtrace was generated from '/usr/local/bin/evolution-2.0'

[New Thread 1024 (LWP 5406)]
[New Thread 2049 (LWP 5408)]
[New Thread 1024 (LWP 5406)]
[New Thread 2049 (LWP 5408)]
[New Thread 1024 (LWP 5406)]
[New Thread 2049 (LWP 5408)]
[New Thread 1026 (LWP 5409)]
[New Thread 2051 (LWP 5410)]
[New Thread 3076 (LWP 5411)]
[New Thread 4101 (LWP 5412)]
[New Thread 5126 (LWP 5413)]
[New Thread 12295 (LWP 5423)]
[New Thread 13320 (LWP 5425)]
[New Thread 10249 (LWP 5418)]
[New Thread 9226 (LWP 5417)]
[New Thread 11275 (LWP 5419)]
0x412cd5e9 in __wait4 () from /lib/libc.so.6

+ Trace 56709

Thread 1 (Thread 1024 (LWP 5406))

#0 __wait4
from /lib/libc.so.6
#1 waitpid
from /lib/libc.so.6
#2 waitpid
from /lib/libpthread.so.0
#3 libgnomeui_segv_handle
from /usr/local/lib/libgnomeui-2.so.0
#4 pthread_sighandler
from /lib/libpthread.so.0
#5 <signal handler called>
#6 __kill
from /lib/libc.so.6
#7 pthread_kill
from /lib/libpthread.so.0
#8 raise
from /lib/libpthread.so.0
#9 abort
from /lib/libc.so.6
#10 g_logv
#11 g_log
#12 idle_expand_row
from /usr/local/lib/gtk-2.0/modules/libgail.so
#13 g_idle_dispatch
at gmain.c line 3821
#14 g_main_dispatch
at gmain.c line 1947
#15 g_main_context_dispatch
at gmain.c line 2497
#16 g_main_context_iterate
at gmain.c line 2578
#17 g_main_loop_run
at gmain.c line 2782
#18 bonobo_main
from /usr/local/lib/libbonobo-2.so.0
#19 main
at main.c line 585
#0 __wait4
from /lib/libc.so.6




Unknown reporter: milang@tal.org, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Olav Vitters 2005-04-09 23:14:32 UTC

Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you find.

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