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 308869 - Selecting a way to receive email causes an instant crash.
Selecting a way to receive email causes an instant crash.
Status: RESOLVED DUPLICATE of bug 307956
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other other
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-06-24 02:16 UTC by cat.okita
Modified: 2005-06-24 14:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description cat.okita 2005-06-24 02:16:07 UTC
Distribution: SUSE LINUX Enterprise Server 9 (i586)
Package: Evolution
Priority: Critical
Version: GNOME2.11.3 unspecified
Gnome-Distributor: SUSE
Synopsis: Selecting a way to receive email causes an instant crash.
Bugzilla-Product: Evolution
Bugzilla-Component: Mailer
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
Configuring an email account causes evolution to crash.

Steps to reproduce the crash:
1. Attempt to configure an email account
2. Select a method to receive email.
3. Crash.

Expected Results:

Being able to configure and receive email.

How often does this happen?

Every time - evolution is not currently useable.

Additional Information:



Debugging Information:

Backtrace was generated from '/opt/gnome/bin/evolution'

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/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)...(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)...(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)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...[Thread debugging using
libthread_db enabled]
[New Thread 1099070272 (LWP 22745)]
[New Thread 1114352560 (LWP 22747)]
[Thread debugging using libthread_db enabled]
[New Thread 1099070272 (LWP 22745)]
[New Thread 1114352560 (LWP 22747)]
[Thread debugging using libthread_db enabled]
[New Thread 1099070272 (LWP 22745)]
[New Thread 1114352560 (LWP 22747)]
0xffffe410 in ?? ()

Thread 1 (Thread 1099070272 (LWP 22745))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #5 libgnomeui_segv_handle
    from /opt/gnome/lib/libgnomeui-2.so.0
  • #6 segv_redirect
  • #7 <signal handler called>
  • #8 gtk_combo_box_menu_item_activate
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #9 g_cclosure_marshal_VOID__VOID
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #10 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #11 signal_emit_unlocked_R
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #14 gtk_widget_activate
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #15 gtk_menu_shell_activate_item
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #16 gtk_menu_shell_button_release
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #17 gtk_menu_button_release
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #18 _gtk_marshal_BOOLEAN__BOXED
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #19 g_type_class_meta_marshal
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #20 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #21 signal_emit_unlocked_R
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #24 gtk_widget_event_internal
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #25 gtk_propagate_event
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #26 gtk_main_do_event
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #27 gdk_event_dispatch
    from /opt/gnome/lib/libgdk-x11-2.0.so.0
  • #28 g_main_context_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #29 g_main_context_iterate
    from /opt/gnome/lib/libglib-2.0.so.0
  • #30 g_main_loop_run
    from /opt/gnome/lib/libglib-2.0.so.0
  • #31 bonobo_main
    from /opt/gnome/lib/libbonobo-2.so.0
  • #32 main
  • #0 ??




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-06-24 02:16 UTC -------


The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was cat.okita@hp.com.

Comment 1 Sebastien Bacher 2005-06-24 14:49:58 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 307956 ***