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 597255 - Evo address book quits unexpectedly when clicking on GW address book
Evo address book quits unexpectedly when clicking on GW address book
Status: RESOLVED DUPLICATE of bug 569329
Product: evolution
Classification: Applications
Component: Contacts
2.28.x (obsolete)
Other Linux
: High critical
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
evolution[groupwise]
Depends on:
Blocks:
 
 
Reported: 2009-10-04 01:26 UTC by Magnus Boman
Modified: 2009-10-05 11:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Magnus Boman 2009-10-04 01:26:19 UTC
When going to contacts and clicking on "Novell GroupWise Address Book" the following dialog pops up:

"The Evolution address book has quit unexpectedly.

Your contacts for groupwise://xyz@xxx.xx.xx.xx/;Novell GroupWise Address Book will not be available until Evolution is restarted"

Running Evo 2.28.0 on openSUSE 11.2
Comment 1 Akhil Laddha 2009-10-05 04:11:02 UTC
(In reply to comment #0)
> 
> "The Evolution address book has quit unexpectedly.
> 

It means eds had been crashed.

Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Magnus Boman 2009-10-05 04:34:26 UTC
Is this enough or do you need me to install debug packages of something more than eds?

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ff1757e4910 (LWP 7439)]
0x00007ff17b4412e4 in e_gw_item_get_full_name (item=0xaf2180) at e-gw-item.c:909
909	{
(gdb) thread apply all bt

Thread 10 (Thread 0x7ff174fe3910 (LWP 7441))

  • #0 __memp_fput_eds
    at ../mp/mp_fput.c line 100
  • #1 __ham_next_cpage_eds
    at ../hash/hash_page.c line 1614
  • #2 __ham_item_eds
    at ../hash/hash_page.c line 133
  • #3 __ham_c_get
    at ../hash/hash.c line 467
  • #4 __db_c_get_eds
    at ../db/db_cam.c line 736
  • #5 e_book_backend_db_cache_get_contacts
    at e-book-backend-db-cache.c line 308
  • #6 book_view_thread
    at e-book-backend-groupwise.c line 2296
  • #7 ??
    from /usr/lib64/libglib-2.0.so.0
  • #8 start_thread
    from /lib64/libpthread.so.0
  • #9 clone
    from /lib64/libc.so.6
  • #10 ??

Thread 9 (Thread 0x7ff1757e4910 (LWP 7439))

  • #0 e_gw_item_get_full_name
    at e-gw-item.c line 909
  • #1 populate_full_name
    at e-book-backend-groupwise.c line 662
  • #2 fill_contact_from_gw_item
    at e-book-backend-groupwise.c line 1178
  • #3 update_address_book_deltas
    at e-book-backend-groupwise.c line 3059
  • #4 ??
    from /usr/lib64/libglib-2.0.so.0
  • #5 start_thread
    from /lib64/libpthread.so.0
  • #6 clone
    from /lib64/libc.so.6
  • #7 ??

Thread 7 (Thread 0x7ff179b83910 (LWP 7432))

  • #0 pthread_join
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgthread-2.0.so.0
  • #2 g_thread_join
    from /usr/lib64/libglib-2.0.so.0
  • #3 e_book_backend_groupwise_authenticate_user
    at e-book-backend-groupwise.c line 3338
  • #4 ORBit_small_invoke_adaptor
    from /usr/lib64/libORBit-2.so.0
  • #5 ??
    from /usr/lib64/libORBit-2.so.0
  • #6 ??
    from /usr/lib64/libORBit-2.so.0
  • #7 giop_thread_queue_process
    from /usr/lib64/libORBit-2.so.0
  • #8 ??
    from /usr/lib64/libORBit-2.so.0
  • #9 ??
    from /usr/lib64/libglib-2.0.so.0
  • #10 ??
    from /usr/lib64/libglib-2.0.so.0
  • #11 start_thread
    from /lib64/libpthread.so.0
  • #12 clone
    from /lib64/libc.so.6
  • #13 ??

Comment 3 Akhil Laddha 2009-10-05 11:53:28 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 bug 569329 ***