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 327746 - Crash Immediately After Selecting New-->Mail
Crash Immediately After Selecting New-->Mail
Status: RESOLVED DUPLICATE of bug 334545
Product: evolution-data-server
Classification: Platform
Component: Contacts
1.6.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
: 327368 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-01-19 19:47 UTC by David Richards
Modified: 2013-09-14 16:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description David Richards 2006-01-19 19:47:41 UTC 
Please describe the problem:
Backtrace was generated from '/opt/gnome/libexec/evolution-data-server-1.6'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1219766592 (LWP 13866)]
[New Thread -1232462928 (LWP 14011)]
[Thread debugging using libthread_db enabled]
[New Thread -1219766592 (LWP 13866)]
[New Thread -1232462928 (LWP 14011)]
[Thread debugging using libthread_db enabled]
[New Thread -1219766592 (LWP 13866)]
[New Thread -1232462928 (LWP 14011)]
[New Thread -1296049232 (LWP 14010)]
[New Thread -1287656528 (LWP 14008)]
[New Thread -1252185168 (LWP 13890)]
[New Thread -1224066128 (LWP 13868)]
0xffffe410 in ?? ()

+ Trace 65373

Thread 3 (Thread -1296049232 (LWP 14010))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __lll_mutex_lock_wait
    from /lib/tls/libpthread.so.0
  • #5 _L_mutex_lock_33
    from /lib/tls/libpthread.so.0
  • #6 ??
  • #7 ??
  • #8 ??
    from /opt/gnome/lib/libedataserver-1.2.so.7
  • #9 g_thread_use_default_impl
  • #10 ??
  • #11 ??
  • #12 gnome_segv_handler
    at server.c line 97
  • #13 gnome_segv_handler
    at server.c line 97
  • #14 <signal handler called>
  • #15 e_list_iterator_new
    at e-list-iterator.c line 74
  • #16 e_list_get_iterator
    at e-list.c line 79
  • #17 find_book_view
    at e-book-backend-groupwise.c line 2333
  • #18 update_cache
    at e-book-backend-groupwise.c line 2598
  • #19 g_thread_create_full
    from /opt/gnome/lib/libglib-2.0.so.0
  • #20 start_thread
    from /lib/tls/libpthread.so.0
  • #21 clone
    from /lib/tls/libc.so.6 


Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 parthasarathi susarla 2006-01-30 10:03:23 UTC 
Address book crash. Reassigning component.
Comment 2 Sushma Rai 2006-01-30 13:07:29 UTC 
Does it happen every time?
Comment 3 David Richards 2006-01-30 14:38:46 UTC 
No it does not.  When I get these random type bugs I just try and get the dump into a bug report in case it's useful by itself.
Comment 4 Sushma Rai 2006-01-31 07:52:39 UTC 
*** Bug 327368 has been marked as a duplicate of this bug. ***
Comment 5 Christian Kirbach 2006-02-01 21:13:41 UTC 
good trace, duplicate -> confirming
Comment 6 Devashish Sharma 2006-03-15 05:43:53 UTC 

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