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 338732 - evolution-data-server crashes
evolution-data-server crashes
Status: RESOLVED DUPLICATE of bug 335961
Product: evolution-data-server
Classification: Platform
Component: Contacts
1.6.x (obsolete)
Other other
: High critical
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-04-16 20:07 UTC by klafd
Modified: 2006-04-19 09:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description klafd 2006-04-16 20:08:07 UTC 
Distribution: Ubuntu 6.06 (dapper)
Package: Evolution
Severity: Normal
Version: GNOME2.14.1 unspecified
Gnome-Distributor: Ubuntu
Synopsis: evolution-data-server crashes
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
dialog says evolution-data-server has closed unexpectedly

Steps to reproduce the crash:
1. Start evolution
2.. dialog says evolution-data-server has closed unexpectedly

Expected Results:
Just start evolution

How often does this happen?
Every time evolution starts

Additional Information:
The error apeared when upgrading the distribution (upgrade to evolution
2.6.1). A previous version of evolution had been used and data/settings from the previous version were not removed.



Debugging Information:

Backtrace was generated from '/usr/libexec/evolution-data-server-1.6'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1220057408 (LWP 11641)]
[New Thread -1282569296 (LWP 11655)]
[New Thread -1265783888 (LWP 11653)]
[New Thread -1223423056 (LWP 11643)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 67650

Thread 2 (Thread -1282569296 (LWP 11655))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 _L_mutex_lock_33
    from /lib/tls/i686/cmov/libpthread.so.0
  • #3 ??
  • #4 ??
  • #5 ??
    from /lib/tls/i686/cmov/libpthread.so.0
  • #6 ??
  • #7 ??
  • #8 ??
    from /lib/tls/i686/cmov/libc.so.6
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 pthread_mutex_lock
    from /lib/tls/i686/cmov/libc.so.6
  • #13 pthread_mutex_lock
    from /lib/tls/i686/cmov/libc.so.6
  • #14 ??
  • #15 Bonobo_EventSource__classid
  • #16 ??
  • #17 __malloc_initialize_hook
    from /lib/tls/i686/cmov/libc.so.6
  • #18 pthread_getspecific
    from /lib/tls/i686/cmov/libpthread.so.0
  • #19 <signal handler called>
  • #20 g_str_hash
    from /usr/lib/libglib-2.0.so.0
  • #21 g_hash_table_lookup
    from /usr/lib/libglib-2.0.so.0
  • #22 e_data_book_view_notify_update_vcard
    from /usr/lib/libedata-book-1.2.so.2
  • #23 ??
    from /usr/lib/evolution-data-server-1.2/extensions/libebookbackendfile.so
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
  • #28 ?? 




------- Bug created by bug-buddy at 2006-04-16 20:08 -------
Comment 1 André Klapper 2006-04-17 11:48:58 UTC 
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? 

Please start evolution-data-server seperately from a terminal window (evolution-data-server should be located in /usr/libexec or something similar like that) within gdb (this means: run "gdb /usr/libexec/evolution-data-server"), after that, start evolution, and if evolution-data-server crashes, please type "thread apply all bt" and post the output here. Thanks very much.

Perhaps starting evolution with another view could also help, e.g. run "evolution -c mail" or "evolution -c calendar". just guessing, though. :-/

Also see http://live.gnome.org/GettingTraces for more information.
Comment 2 klafd 2006-04-19 05:09:53 UTC 
I ran the data-server with the debugger. At first it wouldn't crash, but when I changed the view it did. The other day I clicked on the clock on the panel and it crashed too.

This is the output:

+ Trace 67714

Thread 5 (Thread -1233036368 (LWP 20391))

  • #0 g_str_hash
    from /usr/lib/libglib-2.0.so.0
  • #1 g_hash_table_lookup
    from /usr/lib/libglib-2.0.so.0
  • #2 e_data_book_view_notify_update_vcard
    from /usr/lib/libedata-book-1.2.so.2
  • #3 ??
    from /usr/lib/evolution-data-server-1.2/extensions/libebookbackendfile.so
  • #4 ??
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ?? 






Comment 3


André Klapper





          2006-04-19 07:20:37 UTC
        



hmm. there is only one call in this stacktrace which refers to evolution-data-server, one cannot find out much. :-(






Comment 4


Harish Krishnaswamy





          2006-04-19 08:12:47 UTC
        



Assigning this to the Contacts component






Comment 5


Sushma Rai





          2006-04-19 09:11:00 UTC
        



Looks like some data is corrupted.
Can you test running Evolution as some new linux user?

If it works, a workaround for this problem could be,
exporting the contacts using evolution-addressbook-export tool, into VCF
(--format=vcard) file, backup your .evolution/addressbook folder and
then import the exported list of contacts into it.


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