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 245840 - The Contacts component crashes (segmentation fault), when I try to edit multiple contacts
The Contacts component crashes (segmentation fault), when I try to edit multi...
Status: RESOLVED DUPLICATE of bug 245260
Product: evolution
Classification: Applications
Component: Contacts
pre-1.5 (obsolete)
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2003-07-04 10:45 UTC by Siim Ainsaar
Modified: 2003-07-07 18:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Siim Ainsaar 2003-07-04 10:45:16 UTC 
Package: Evolution
Priority: Normal
Version: 1.2.2
Synopsis: The Contacts component crashes (segmentation fault), when I try to edit multiple contacts
Bugzilla-Product: Evolution
Bugzilla-Component: Contacts [was: Addressbook]

Description:
Description of Problem:
The Contacts page crashes with a segmentation fault, when I edit
multiple contacts (open with Ctrl+O, modify, save an close) and try to
open the next one (press Ctrl+O again). I usually have to edit several
contacts, before the error occurs.

Steps to reproduce the problem:
1. Open a contact with Ctrl+O, modify it (I changed the addresses), save
and close the modifying window
2. Open another contact with Ctrl+O
3. Repeat several times

Actual Results:
The Contacts component of Evolution crashed with a segmentation fault,
so I had to restart Evolution to continue work with the contacts.

Expected Results:
I hoped to just edit my contacts, mainly their addresses

How often does this happen?
It has happened already 3 times in a row, after editing 2-3 contacts. 




Debugging Information:

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

(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)...[New
Thread 1092038976 (LWP 4311)]
0xffffe002 in ??
    ()

+ Trace 38419

Thread 1 (Thread 1092038976 (LWP 4311))

  • #0 ??
  • #1 gnome_init
    from /usr/lib/libgnomeui.so.32
  • #2 <signal handler called>
  • #3 gtk_window_set_default_size
    from /usr/lib/libgtk-1.2.so.0
  • #4 gtk_marshal_NONE__NONE
    from /usr/lib/libgtk-1.2.so.0
  • #5 gtk_signal_set_funcs
    from /usr/lib/libgtk-1.2.so.0
  • #6 gtk_signal_emit
    from /usr/lib/libgtk-1.2.so.0
  • #7 gtk_widget_show
    from /usr/lib/libgtk-1.2.so.0
  • #8 e_contact_editor_show
  • #9 e_contact_editor_confirm_delete
  • #10 e_book_view_get_type
    from /usr/lib/evolution/1.2/libebook.so.0
  • #11 e_book_view_get_type
    from /usr/lib/evolution/1.2/libebook.so.0
  • #12 gtk_marshal_NONE__NONE
    from /usr/lib/libgtk-1.2.so.0
  • #13 gtk_signal_remove_emission_hook
    from /usr/lib/libgtk-1.2.so.0
  • #14 gtk_signal_set_funcs
    from /usr/lib/libgtk-1.2.so.0
  • #15 gtk_signal_emit
    from /usr/lib/libgtk-1.2.so.0
  • #16 GNOME_Evolution_Composer_send
    from /usr/lib/evolution/1.2/libebook.so.0
  • #17 g_main_set_poll_func
    from /usr/lib/libglib-1.2.so.0
  • #18 g_get_current_time
    from /usr/lib/libglib-1.2.so.0
  • #19 g_get_current_time
    from /usr/lib/libglib-1.2.so.0
  • #20 g_main_run
    from /usr/lib/libglib-1.2.so.0
  • #21 gtk_main
    from /usr/lib/libgtk-1.2.so.0
  • #22 bonobo_main
    from /usr/lib/libbonobo.so.2
  • #23 main
  • #24 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ?? 


Unknown reporter: punanetiiger@hot.ee, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Comment 1 Gerardo Marin 2003-07-07 18:13:11 UTC 

*** This bug has been marked as a duplicate of 245260 ***