Bug 474596 – crash in Tasks: Composing a new mail mes...

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 474596 - crash in Tasks: Composing a new mail mes...


Summary:	crash in Tasks: Composing a new mail mes...


Status:	RESOLVED DUPLICATE of bug 458670

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-09-07 16:43 UTC by hoover
Modified:	2007-10-26 06:33 UTC

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

Description hoover 2007-09-07 16:43:19 UTC

Version: 2.10

What were you doing when the application crashed?
Composing a new mail message.  I had typed in two addresses.  Actually, the mail message was a forward of one I had just read.


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

System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 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: 168751104 vsize: 168751104 resident: 79486976 share: 42598400 rss: 79486976 rss_rlim: 4294967295
CPU usage: start_time: 1189145315 rtime: 16212 utime: 13659 stime: 2553 cutime:1747 cstime: 601 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 -1208887584 (LWP 2585)]
[New Thread -1284506736 (LWP 2693)]
[New Thread -1282442352 (LWP 2692)]
[New Thread -1222468720 (LWP 2636)]
0x00110402 in __kernel_vsyscall ()

+ Trace 161144

Thread 1 (Thread -1208887584 (LWP 2585))

#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 IA__g_utf8_offset_to_pointer
at gutf8.c line 302
#6 get_entry_substring
at e-name-selector-entry.c line 520
#7 entry_activate
at e-name-selector-entry.c line 1402
#8 IA__g_cclosure_marshal_VOID__VOID
at gmarshal.c line 77
#9 IA__g_closure_invoke
at gclosure.c line 490
#10 signal_emit_unlocked_R
at gsignal.c line 2440
#11 IA__g_signal_emitv
at gsignal.c line 2111
#12 gtk_binding_entry_activate
at gtkbindings.c line 535
#13 binding_match_activate
at gtkbindings.c line 955
#14 gtk_bindings_activate_list
at gtkbindings.c line 1089
#15 IA__gtk_bindings_activate_event
at gtkbindings.c line 1166
#16 gtk_widget_real_key_press_event
at gtkwidget.c line 3659
#17 gtk_entry_key_press
at gtkentry.c line 2044
#18 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 84
#19 g_type_class_meta_marshal
at gclosure.c line 567
#20 IA__g_closure_invoke
at gclosure.c line 490
#21 signal_emit_unlocked_R
at gsignal.c line 2478
#22 IA__g_signal_emit_valist
at gsignal.c line 2209
#23 IA__g_signal_emit
at gsignal.c line 2243
#24 gtk_widget_event_internal
at gtkwidget.c line 3915
#25 IA__gtk_window_propagate_key_event
at gtkwindow.c line 4670
#26 gtk_window_key_press_event
at gtkwindow.c line 4700
#27 bonobo_window_key_press_event
at bonobo-window.c line 265
#28 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 84
#29 g_type_class_meta_marshal
at gclosure.c line 567
#30 IA__g_closure_invoke
at gclosure.c line 490
#31 signal_emit_unlocked_R
at gsignal.c line 2478
#32 IA__g_signal_emit_valist
at gsignal.c line 2209
#33 IA__g_signal_emit
at gsignal.c line 2243
#34 gtk_widget_event_internal
at gtkwidget.c line 3915
#35 IA__gtk_propagate_event
at gtkmain.c line 2315
#36 IA__gtk_main_do_event
at gtkmain.c line 1575
#37 gdk_event_dispatch
at gdkevents-x11.c line 2318
#38 IA__g_main_context_dispatch
at gmain.c line 2045
#39 g_main_context_iterate
at gmain.c line 2677
#40 IA__g_main_loop_run
at gmain.c line 2881
#41 bonobo_main
at bonobo-main.c line 311
#42 main
at main.c line 586
#0 __kernel_vsyscall



----------- .xsession-errors (242 sec old) ---------------------
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Max failures exceeded, exiting now
(evolution:2585): camel-WARNING **: No from set for message
report junk?? contribution market
--------------------------------------------------

Comment 1 Akhil Laddha 2007-10-26 06:33:34 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 458670 ***