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 310211 - Crash, while trying to set up an email-account
Crash, while trying to set up an email-account
Status: RESOLVED DUPLICATE of bug 307794
Product: evolution
Classification: Applications
Component: Importers
2.2.x (obsolete)
Other other
: Normal normal
: ---
Assigned To: Harish Krishnaswamy
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-07-13 12:06 UTC by silvia.prohl
Modified: 2005-07-13 12:37 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description silvia.prohl 2005-07-13 12:06:09 UTC
Distribution: Fedora Core release 4 (Stentz)
Package: Evolution
Priority: Normal
Version: GNOME2.11.4 2.2.3
Gnome-Distributor: Red Hat, Inc
Synopsis: Crash, while trying to set up an email-account
Bugzilla-Product: Evolution
Bugzilla-Component: Importers
Bugzilla-Version: 2.2.3
BugBuddy-GnomeVersion: 2.0 (2.11.1)
Description:
Description of the crash:


Steps to reproduce the crash:
1. First start of Evolution
2. Entering Name and Email address
3. choosing the kind of emailaccount - whatever I choose, it crashes
Evolution 2.2.3

Expected Results:


How often does this happen?
Everytime

Additional Information:



Debugging Information:

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 -1208912208 (LWP 21652)]
[New Thread 52022192 (LWP 21687)]
0x00ae4402 in ?? ()

Thread 1 (Thread -1208912208 (LWP 21652))

  • #0 ??
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 segv_redirect
    at main.c line 429
  • #4 <signal handler called>
  • #5 gtk_combo_box_set_active_iter
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #11 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_menu_reorder_child
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_marshal_VOID__UINT_STRING
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #21 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 gdk_screen_get_setting
    from /usr/lib/libgdk-x11-2.0.so.0
  • #25 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #26 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #27 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #28 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 startup_wizard
    at startup-wizard.c line 268




------- Bug moved to this database by unknown@gnome.bugs 2005-07-13 12:06 UTC -------


Unknown version 2.2.3 in product Evolution.  Setting version to "2.2.x".
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@gnome.bugs.
   Previous reporter was silvia.prohl@gmail.com.

Comment 1 Teppo Turtiainen 2005-07-13 12:37:57 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 307794 ***