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 464442 - crash in Evolution: Sending an e-mail
crash in Evolution: Sending an e-mail
Status: RESOLVED DUPLICATE of bug 410823
Product: evolution
Classification: Applications
Component: general
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-07 17:47 UTC by Jason Martens
Modified: 2007-08-17 08:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Jason Martens 2007-08-07 17:47:41 UTC 
What were you doing when the application crashed?
Sending an e-mail


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.18-4-xen-686 #1 SMP Mon Mar 26 21:49:04 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 186908672 vsize: 186908672 resident: 55181312 share: 22777856 rss: 55181312 rss_rlim: 4294967295
CPU usage: start_time: 1186497318 rtime: 1817 utime: 1648 stime: 169 cutime:2069 cstime: 149 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232988496 (LWP 5439)]
[New Thread -1320531056 (LWP 12044)]
[New Thread -1320264816 (LWP 5702)]
[New Thread -1273848944 (LWP 5571)]
[New Thread -1311118448 (LWP 5532)]
[New Thread -1302332528 (LWP 5531)]
[New Thread -1292551280 (LWP 5511)]
[New Thread -1282241648 (LWP 5509)]
[New Thread -1265456240 (LWP 5506)]
[New Thread -1256670320 (LWP 5505)]
[New Thread -1248277616 (LWP 5503)]
[New Thread -1238713456 (LWP 5502)]
0xb7f4c402 in __kernel_vsyscall ()

+ Trace 153539

Thread 1 (Thread -1232988496 (LWP 5439))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 segv_redirect
    at main.c line 427
  • #4 <signal handler called>
  • #5 get_range_at_position
    at e-name-selector-entry.c line 244
  • #6 update_completions_on_idle_cb
    at e-name-selector-entry.c line 856
  • #7 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #12 main
    at main.c line 611
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
(evolution-2.10:5439): libebook-CRITICAL **: photo_setter: assertion `photo->data.inlined.length > 0' failed
(evolution-2.10:5439): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkEntry'
(evolution-2.10:5439): Gtk-CRITICAL **: gtk_entry_get_text: assertion `GTK_IS_ENTRY (entry)' failed
(evolution-2.10:5439): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkEditable'
(evolution-2.10:5439): Gtk-CRITICAL **: gtk_editable_get_position: assertion `GTK_IS_EDITABLE (editable)' failed
warning: .dynamic section for "/usr/lib/libexpat.so.1" is not at the expected address
warning: .dynamic section for "/usr/lib/libsasl2.so.2" is not at the expected address
warning: .dynamic section for "/usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so" is not at the expected address
--------------------------------------------------
Comment 1 André Klapper 2007-08-17 08:59:44 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 410823 ***