Bug 505734 – crash in Tasks: Clicked "Send" button after compose

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 505734 - crash in Tasks: Clicked "Send" button after compose


Summary:	crash in Tasks: Clicked "Send" button after compose


Status:	RESOLVED DUPLICATE of bug 239441

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	2.10.x (obsolete)
Hardware:	Other Linux

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-12-26 13:44 UTC by cwebster
Modified:	2008-02-26 23:19 UTC

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

Attachments
evolution-data-server-1.10-bugreport (9.90 KB, text/plain) 2008-01-05 13:23 UTC, cwebster	Details

Description cwebster 2007-12-26 13:44:46 UTC

Version: 2.10

What were you doing when the application crashed?
Clicked "Send" button after composing a "forward" message.


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: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 192430080 vsize: 192430080 resident: 87699456 share: 42799104 rss: 87699456 rss_rlim: 4294967295
CPU usage: start_time: 1198675760 rtime: 1352 utime: 1232 stime: 120 cutime:46 cstime: 12 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208764704 (LWP 26031)]
[New Thread -1261839472 (LWP 26075)]
[New Thread -1290331248 (LWP 26056)]
[New Thread -1240466544 (LWP 26051)]
0x00110402 in __kernel_vsyscall ()

+ Trace 183107

Thread 1 (Thread -1208764704 (LWP 26031))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 872
#3 segv_redirect
at main.c line 408
#4 <signal handler called>
#5 resort_node
at e-tree-table-adapter.c line 158
#6 etta_sort_info_changed
at e-tree-table-adapter.c line 824
#7 resort_model
at e-tree-table-adapter.c line 751
#8 g_idle_dispatch
at gmain.c line 3928
#9 IA__g_main_context_dispatch
at gmain.c line 2045
#10 g_main_context_iterate
at gmain.c line 2677
#11 IA__g_main_loop_run
at gmain.c line 2881
#12 bonobo_main
from /usr/lib/libbonobo-2.so.0
#13 main
at main.c line 586
#0 __kernel_vsyscall



----------- .xsession-errors (12 sec old) ---------------------
(evolution:26031): libebook-WARNING **: invalid escape, passing it through
(evolution:26031): libebook-WARNING **: invalid escape, passing it through
(evolution:26031): libebook-WARNING **: invalid escape, passing it through
(evolution:26031): libebook-WARNING **: invalid escape, passing it through
(evolution:26031): libebook-WARNING **: invalid escape, passing it through
(evolution:26031): libebook-WARNING **: invalid escape, passing it through
(evolution:26031): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `ETableModel'
(evolution:26031): e-table-CRITICAL **: e_table_model_pre_change: assertion `E_IS_TABLE_MODEL (e_table_model)' failed
--------------------------------------------------

Comment 1 cwebster 2008-01-05 13:23:27 UTC

Created attachment 102208 [details]
evolution-data-server-1.10-bugreport

This crash occurred immediately on startup of Evolution. Evolution startup was triggered on login to restore previous session.

Comment 2 Akhil Laddha 2008-02-11 05:21:56 UTC

Please file the bug separately for different crash. TIA.

Comment 3 Tobias Mueller 2008-02-26 23:19:47 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 239441 ***