Bug 444655 – crash in Email:

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


Summary:	crash in Email:


Status:	RESOLVED DUPLICATE of bug 431342

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-06 09:50 UTC by shop
Modified:	2007-06-06 10:29 UTC

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

Description shop 2007-06-06 09:50:20 UTC

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 136183808 vsize: 136183808 resident: 31621120 share: 16887808 rss: 31621120 rss_rlim: 4294967295
CPU usage: start_time: 1181123387 rtime: 421 utime: 367 stime: 54 cutime:0 cstime: 0 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208437024 (LWP 4038)]
[New Thread -1231230064 (LWP 4043)]
(no debugging symbols found)
0x001c2402 in __kernel_vsyscall ()

+ Trace 138699

Thread 1 (Thread -1208437024 (LWP 4038))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/nosegneg/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 camel_message_info_ptr
from /usr/lib/libcamel-provider-1.2.so.10
#6 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#7 ??
from /usr/lib/evolution/2.10/libetable.so.0
#8 e_tree_model_value_at
from /usr/lib/evolution/2.10/libetable.so.0
#9 e_table_sorting_utils_tree_sort
from /usr/lib/evolution/2.10/libetable.so.0
#10 ??
from /usr/lib/evolution/2.10/libetable.so.0
#11 ??
from /usr/lib/evolution/2.10/libetable.so.0
#12 ??
from /usr/lib/evolution/2.10/libetable.so.0
#13 g_cclosure_marshal_VOID__POINTER
from /lib/libgobject-2.0.so.0
#14 g_closure_invoke
from /lib/libgobject-2.0.so.0
#15 ??
from /lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#17 g_signal_emit
from /lib/libgobject-2.0.so.0
#18 e_tree_model_node_changed
from /usr/lib/evolution/2.10/libetable.so.0
#19 e_tree_memory_thaw
from /usr/lib/evolution/2.10/libetable.so.0
#20 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#21 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#22 ??
from /lib/libglib-2.0.so.0
#23 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#24 ??
from /lib/libglib-2.0.so.0
#25 g_main_loop_run
from /lib/libglib-2.0.so.0
#26 bonobo_main
from /usr/lib/libbonobo-2.so.0
#27 main
#0 __kernel_vsyscall



----------- .xsession-errors (7 sec old) ---------------------
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x4d
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x4d
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x1400e0e
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x1400e0e
--------------------------------------------------

Comment 1 palfrey 2007-06-06 10:29:54 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

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