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 448432 - Crash in Evolution Data Server
Crash in Evolution Data Server
Status: RESOLVED DUPLICATE of bug 452812
Product: evolution-data-server
Classification: Platform
Component: Contacts
1.10.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-17 09:27 UTC by Allan Engelhardt
Modified: 2008-07-30 13:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Allan Engelhardt 2007-06-17 09:27:33 UTC
Steps to reproduce:
I had just started Evolution as

$ evolution --force-shutdown
$ evolution --debug=/tmp/evolution.debug

when I got a bug-buddy on the data server.

The Contacts view on a local address book was the open view in Evolution.

I have no idea why there is a e_contact_new_from_vcard in the stack trace: I hadn't done anything....  (personal data slightly erased with XXX markings)

Stack trace:
System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 603320320 vsize: 603320320 resident: 23969792 share: 5267456 rss: 23969792 rss_rlim: 18446744073709551615
CPU usage: start_time: 1182071852 rtime: 16 utime: 12 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912496293424 (LWP 10349)]
[New Thread 1126455632 (LWP 10388)]
[New Thread 1094986064 (LWP 10383)]
[New Thread 1074006352 (LWP 10350)]
0x0000003471c9643f in __libc_waitpid (pid=10400, stat_loc=0x7fffe4f2c1fc, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

Thread 3 (Thread 1094986064 (LWP 10383))

  • #0 __lll_mutex_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_mutex_lock_103
    from /lib64/libpthread.so.0
  • #2 __pthread_mutex_lock
    at pthread_mutex_lock.c line 81
  • #3 gnome_segv_handler
    at server.c line 97
  • #4 <signal handler called>
  • #5 strcmp
    from /lib64/libc.so.6
  • #6 _nl_find_msg
    at dcigettext.c line 862
  • #7 __dcigettext
    at dcigettext.c line 639
  • #8 e_contact_class_init
    at e-contact.c line 323
  • #9 IA__g_type_class_ref
    at gtype.c line 1874
  • #10 IA__g_object_newv
    at gobject.c line 853
  • #11 IA__g_object_new_valist
    at gobject.c line 981
  • #12 IA__g_object_new
    at gobject.c line 795
  • #13 e_contact_new_from_vcard
  • #14 e_book_view_listener_queue_sequence_event
    at e-book-view-listener.c line 166
  • #15 ORBit_small_invoke_adaptor
    at orbit-small.c line 844
  • #16 ORBit_POAObject_handle_request
    at poa.c line 1351
  • #17 ORBit_POAObject_invoke_incoming_request
    at poa.c line 1421
  • #18 giop_thread_queue_process
    at giop.c line 771
  • #19 giop_request_handler_thread
    at giop.c line 481
  • #20 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #21 g_thread_create_proxy
    at gthread.c line 591
  • #22 start_thread
    at pthread_create.c line 296
  • #23 clone
    from /lib64/libc.so.6


----------- .xsession-errors (711 sec old) ---------------------
Trying to dispose element fakesink, but it is not in the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
(rhythmbox:3092): GStreamer-CRITICAL **: 
Trying to dispose element fakesink, but it is not in the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
--- Hash table keys for warning below:
--> file:///home/allane
(nautilus:9710): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
--------------------------------------------------

Other information:
--------
evolution-data-server-1.10.2-3.fc7 on Fedora 7 x86_64.  The --debug file from the client has a long list of

(evolution:10345): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922

lines at the end
Comment 1 Allan Engelhardt 2007-06-17 10:15:12 UTC
This appears to be repeatable: If I do

$ evolution --force-shutdown
$ evolution --debug=/tmp/evolution.debug --offline
(exit from the Evolution client)

a few times (3-10) in rapid order then I get the crash.  (I'm pretty sure it is the same one - one more attached here to get the wonderful Bugzilla color highlights.  And yes, it is always Frank in the backtrace but I  don't know what is special about Frank.)

--------
System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 603320320 vsize: 603320320 resident: 23969792 share: 5267456 rss: 23969792 rss_rlim: 18446744073709551615
CPU usage: start_time: 1182071852 rtime: 16 utime: 12 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912496293424 (LWP 10349)]
[New Thread 1126455632 (LWP 10388)]
[New Thread 1094986064 (LWP 10383)]
[New Thread 1074006352 (LWP 10350)]
0x0000003471c9643f in __libc_waitpid (pid=10400, stat_loc=0x7fffe4f2c1fc, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

Thread 3 (Thread 1094986064 (LWP 10383))

  • #0 __lll_mutex_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_mutex_lock_103
    from /lib64/libpthread.so.0
  • #2 __pthread_mutex_lock
    at pthread_mutex_lock.c line 81
  • #3 gnome_segv_handler
    at server.c line 97
  • #4 <signal handler called>
  • #5 strcmp
    from /lib64/libc.so.6
  • #6 _nl_find_msg
    at dcigettext.c line 862
  • #7 __dcigettext
    at dcigettext.c line 639
  • #8 e_contact_class_init
    at e-contact.c line 323
  • #9 IA__g_type_class_ref
    at gtype.c line 1874
  • #10 IA__g_object_newv
    at gobject.c line 853
  • #11 IA__g_object_new_valist
    at gobject.c line 981
  • #12 IA__g_object_new
    at gobject.c line 795
  • #13 e_contact_new_from_vcard
  • #14 e_book_view_listener_queue_sequence_event
    at e-book-view-listener.c line 166
  • #15 ORBit_small_invoke_adaptor
    at orbit-small.c line 844
  • #16 ORBit_POAObject_handle_request
    at poa.c line 1351
  • #17 ORBit_POAObject_invoke_incoming_request
    at poa.c line 1421
  • #18 giop_thread_queue_process
    at giop.c line 771
  • #19 giop_request_handler_thread
    at giop.c line 481
  • #20 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #21 g_thread_create_proxy
    at gthread.c line 591
  • #22 start_thread
    at pthread_create.c line 296
  • #23 clone
    from /lib64/libc.so.6


----------- .xsession-errors (711 sec old) ---------------------
Trying to dispose element fakesink, but it is not in the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
(rhythmbox:3092): GStreamer-CRITICAL **: 
Trying to dispose element fakesink, but it is not in the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
--- Hash table keys for warning below:
--> file:///home/allane
(nautilus:9710): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
--------------------------------------------------
Comment 2 Allan Engelhardt 2007-06-17 10:26:02 UTC
(Yeah, I realize I pasted the same traceback in the second time.  Who's idea is it for Bug Buddy to drop the files on your desktop anyhow? :( Trust me: the version on my desktop is the same, apart from some thread identifiers.  I won't bore you with another cut-and-paste job.)

To reproduce: as above, noting that the application starts with the contacts view and that the --offline option appears to make it easier to crash.
Comment 3 Milan Crha 2008-02-20 18:43:33 UTC
Hello, can you still reproduce it, please?

I tried with --offline option and starting in address book (but without Frank), and nothing like this happened. I think that Frank is just first person it found when reading your contacts from the store.

From the stack trace, it crashed in gettext rutine, when it was trying to localize first token of contact, "Unique ID". Because it crashed in gettext, I guess you had something broken with that library.
Comment 4 Kandepu Prasad 2008-07-30 13:24:06 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 452812 ***