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 538063 - Evolution crashes when pressing Enter in an empty To: field
Evolution crashes when pressing Enter in an empty To: field
Status: RESOLVED DUPLICATE of bug 458670
Product: evolution
Classification: Applications
Component: Mailer
2.10.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-06-12 21:31 UTC by Robert F. Chapman
Modified: 2008-06-13 05:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Robert F. Chapman 2008-06-12 21:31:49 UTC
Steps to reproduce:
1. Compose a new email
2. Once the window opens, the cursor will be located in the To: field
3. Press Enter, and crash...


Stack trace:
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.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 154923008 vsize: 154923008 resident: 45953024 share: 19689472 rss: 45953024 rss_rlim: 4294967295
CPU usage: start_time: 1213305967 rtime: 788 utime: 739 stime: 49 cutime:42 cstime: 10 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/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208293664 (LWP 3739)]
[New Thread -1310901360 (LWP 4123)]
[New Thread -1266689136 (LWP 3791)]
[New Thread -1245709424 (LWP 3757)]
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208293664 (LWP 3739))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 g_utf8_offset_to_pointer
    from /lib/libglib-2.0.so.0
  • #6 get_entry_substring
    at e-name-selector-entry.c line 520
  • #7 entry_activate
    at e-name-selector-entry.c line 1402
  • #8 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #10 ??
    from /lib/libgobject-2.0.so.0
  • #11 g_signal_emitv
    from /lib/libgobject-2.0.so.0
  • #12 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_bindings_activate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 ??
    from /lib/libgobject-2.0.so.0
  • #20 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #21 ??
    from /lib/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #24 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 gtk_window_propagate_key_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 ??
    from /usr/lib/libbonoboui-2.so.0
  • #28 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 ??
    from /lib/libgobject-2.0.so.0
  • #30 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #31 ??
    from /lib/libgobject-2.0.so.0
  • #32 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #33 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #34 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #38 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #39 ??
    from /lib/libglib-2.0.so.0
  • #40 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #41 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #42 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
warning: the debug information found in "/usr/lib/debug//usr/lib/evolution/2.10/plugins/liborg-gnome-evolution-startup-wizard.so.debug" does not match "/usr/lib/evolution/2.10/plugins/liborg-gnome-evo
warning: the debug information found in "/usr/lib/debug//usr/lib/evolution/2.10/plugins/liborg-gnome-publish-calendar.so.debug" does not match "/usr/lib/evolution/2.10/plugins/liborg-gnome-publish-cal
warning: the debug information found in "/usr/lib/debug//usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so.debug" does not match "/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-not
warning: the debug information found in "/usr/lib/debug//usr/lib/evolution/2.10/plugins/liborg-gnome-sa-junk-plugin.so.debug" does not match "/usr/lib/evolution/2.10/plugins/liborg-gnome-sa-junk-plugi
warning: the debug information found in "/usr/lib/debug//usr/lib/evolution/2.10/plugins/liborg-gnome-groupwise-features.so.debug" does not match "/usr/lib/evolution/2.10/plugins/liborg-gnome-groupwise
--------------------------------------------------


Other information:
Comment 1 Akhil Laddha 2008-06-13 05:18:11 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 458670 ***