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 314846 - EDS randomly crashes - with LDAP backend
EDS randomly crashes - with LDAP backend
Status: RESOLVED FIXED
Product: evolution-data-server
Classification: Platform
Component: Contacts
1.4.x (obsolete)
Other All
: High critical
: ---
Assigned To: Sushma Rai
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-08-30 15:41 UTC by Patrick OCallaghan
Modified: 2013-09-10 13:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Attachments
Stack trace after crash (4.34 KB, text/plain)
2005-09-03 00:08 UTC, Patrick OCallaghan
Details
Console log of e-d-s (14.68 KB, text/plain)
2005-09-03 00:09 UTC, Patrick OCallaghan
Details

Description Patrick OCallaghan 2005-08-30 15:41:19 UTC
Steps to reproduce:
1. Use Evo
2. After an hour or two, EDS crashes for no apparent reason
3. 


Stack trace:
Backtrace was generated from
'/opt/evolution/libexec/evolution-data-server-1.4'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208531264 (LWP 3762)]
[New Thread -1221391440 (LWP 3775)]
[New Thread -1210631248 (LWP 3768)]
0x0045b402 in ?? ()

Thread 1 (Thread -1208531264 (LWP 3762))

  • #0 ??
  • #1 __waitpid_nocancel
    from /lib/libc.so.6
  • #2 do_system
    from /lib/libc.so.6
  • #3 system
    from /lib/libc.so.6
  • #4 system
    from /lib/libpthread.so.0
  • #5 gnome_segv_handler
    at server.c line 109
  • #6 <signal handler called>
  • #7 e_data_book_view_notify_status_message
    at e-data-book-view.c line 343
  • #8 book_view_notify_status
    at e-book-backend-ldap.c line 403
  • #9 e_book_backend_ldap_reconnect
    at e-book-backend-ldap.c line 838



Other information:
Happens several times a day (I keep Evo open all the time). I only use Evo for
mail. I have 1 POP account and 1 IMAP account, both
refreshed every 10 minutes. The same thing has happened in most versions
of Evo I've used (2.0, 2.2, 2.3.7, 2.3.8). System is FC4 with all
updates applied, using KDE 3.2.
Comment 1 Patrick OCallaghan 2005-08-30 15:42:07 UTC
EDS version 1.4
Comment 2 Sushma Rai 2005-09-01 05:43:15 UTC
Looks like a memory corruption...
Can you start e-d-s in seperate console and see any related debug
message is printed before the crash?
Comment 3 Sushma Rai 2005-09-01 05:53:52 UTC
Does it happen on any specific operation?
Comment 4 Sushma Rai 2005-09-01 11:20:53 UTC
Not reproducible in our set up. Moving to 2.4.1.
Comment 5 Sushma Rai 2005-09-01 11:52:16 UTC
Can you go to frames 8 and 9 in gdb, and print the value od 
view and ldap_status?
And also was the LDAP server down, when it crashed?
Comment 6 Patrick OCallaghan 2005-09-01 18:59:55 UTC
No, it's not associated with any operation I'm aware of. It often happens when
I'm not even focussed on the Evo window.

The LDAP service was working when the crash happened AFAIK.

I no longer have the core file to look at with gdb. I'll try looking at if/when
it happens again.

I'm now running e-d-s via a console so as to check any error messages.
Comment 7 Sushma Rai 2005-09-02 05:38:49 UTC
Could be the time out issue?
Though the stack traces are different, the symptom looks 
similar to http://bugzilla.gnome.org/show_bug.cgi?id=300157.

If you build evolution from sources can you try the
attached patch there?
Comment 8 Patrick OCallaghan 2005-09-02 13:43:11 UTC
Comment #17 in http://bugzilla.gnome.org/show_bug.cgi?id=300157 suggests that
this patch doesn't clear the problem. I'll wait to see if there is further
progress before trying any patches.

Also, I never use "Copy book locally for offline operation" and in fact never
use Evo offline.
Comment 9 Patrick OCallaghan 2005-09-03 00:08:43 UTC
Created attachment 51747 [details]
Stack trace after crash
Comment 10 Patrick OCallaghan 2005-09-03 00:09:28 UTC
Created attachment 51748 [details]
Console log of e-d-s
Comment 11 Patrick OCallaghan 2005-09-03 00:10:03 UTC
OK, I ran e-d-s from a console and it crashed again. It's definitely something
in the LDAP code (this time it crashed while I was typing a To: address in a new
message). The LDAP server was up since it was matching entries when the crash
happened.

I attach:

1) Stack trace as produced by bug-buddy.
2) Console output.

I don't know where to find the core file so I can't include symbols, sorry. If
someone gives me detailed instructions I'll do it next time.
Comment 12 Sushma Rai 2005-09-14 04:59:34 UTC
Changed the summary.
Comment 13 Sushma Rai 2005-11-10 05:37:20 UTC
Can you try 2.5.1 and see if it is solved for you?
Comment 14 Patrick OCallaghan 2005-11-12 18:35:33 UTC
I've been trying to compile 2.5.1 (from the ftp.gnome.org tarfiles) but when I
try to configure evolution I get:

Package libsoup-2.4 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libsoup-2.4.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libsoup-2.4' found
checking for LIBSOUP_CFLAGS... -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I/opt/evolution/include/libsoup-2.2
-I/usr/include/libxml2
checking for LIBSOUP_LIBS... -L/opt/evolution/lib -lsoup-2.2 -lgnutls -lgcrypt
-lgpg-error -lxml2 -lpthread -lz -lm -lglib-2.0
checking for EVOLUTION_CALENDAR_CFLAGS...
checking for EVOLUTION_CALENDAR_LIBS...
Package hal was not found in the pkg-config search path.
Perhaps you should add the directory containing `hal.pc'
to the PKG_CONFIG_PATH environment variable
No package 'hal' found

I have libsoup-2.2.6.1 installed. I don't know where to get libsoup-2.4, or what
hal is.

I get this exact error on two different machines, both running Fedora FC4 with
all yum updates. I've previously compiled Evo 2.4.1 on both these machines with
no trouble.

The configure command I'm using is:

./configure --prefix=/opt/evolution --enable-imap4 --enable-nss --with-openldap
--with-nspr-include=/usr/include/mozilla-1.7.12/nspr

If someone can enlighten me I'll try again, but note that the README in the Evo
2.5.1 source directory is identical to that in the 2.4.1 version, and those are
the instructions I'm following.
Comment 15 Patrick OCallaghan 2005-11-21 16:46:00 UTC
Managed to compile 2.5.1 (a -devel RPM was missing), but now the LDAP backend
doesn't seem to do anything at all.

First of all, when I tried to modify pre-existing LDAP settings I couldn't save
the result -- the OK button would gray out as soon as I changed anything. So I
created a new address book under a different name, pointing at the same LDAP
server. Now I can change settings with no difficulty, but LDAP doesn't work. I
have it set as default address book and have configured autocompletion, but no
luck, i.e. 1) in the Contacts pane I can't do a search (the search box is grayed
out), and 2) when composing a message there's no autocompletion.
Comment 16 Patrick OCallaghan 2005-12-28 13:36:31 UTC
-- Just to bring Bugzilla up to date with some exchanges on the Evo mailing list

11 Dec 2005:

I tried starting e-d-s manually (this is a fresh session BTW):

<log>
[poc@shire ~]$ ps ax|grep evo
16767 ?        Sl
0:00 /opt/evolution/libexec/evolution/2.4/evolution-alarm-notify
--sm-config-prefix /evolution-alarm-notify-klwBoZ/ --sm-client-id
10d8686972000111715323700000050400009 --screen 0
16967 pts/3    S+     0:00 grep evo
[poc@shire ~]$ /opt/evolution/bin/evolution-2.4
evolution-shell-Message: Killing old version of evolution-data-server...
adding hook target 'source'

(evolution-2.4:16972): camel-WARNING **: camel_exception_get_id called
with NULL parameter.

(evolution-2.4:16972): camel-WARNING **: camel_exception_get_id called
with NULL parameter.

(evolution-2.4:16972): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion
`GDK_IS_GC (gc)' failed

(evolution-2.4:16972): libebook-WARNING **: Can't find installed
BookFactories

(evolution-2.4:16972): libebook-WARNING **: Can't find installed
BookFactories

(evolution-2.4:16972): libebook-WARNING **: Can't find installed
BookFactories
[poc@shire ~]$
</log>

So there are two things here:

1) Starting Evo doesn't start e-d-s.
2) e-d-s when started manually doesn't appear to communicate with Evo.

I've checked bonobo-activation-config.xml and it's correct (i.e. it
hasn't changed in several months).

However on my other machine, on an apparently identical config of Evo,
everything works correctly.

-- To which Sushma Rai <rsushma@novell.com> replied:

Error message 
"(evolution-2.4:16972): libebook-WARNING **: Can't find installed
BookFactories"
is indicates that it is not finding the book factories.
Verify your BONOBO_ACTIVATION_PATH ?

-- To which I replied:

How do I verify it? I've never consciously set it anywhere, and it
doesn't exist as an environment variable in my shell. It's also not set
in any of the config files or Makefiles I've used to compile Evo.

BTW I'm using KDE (on both machines), if it matters.

-- Finally, I've now been using 2.5.3 for a couple of weeks and the problem hasn't reappeared (so far).
Comment 17 Sushma Rai 2006-01-02 06:49:54 UTC
So I think the mutex lock patch, which has been committed to CVS also,
as been fixed your issue. 
I am closing the bug, please re-open if you see the similar crash.
Comment 18 Patrick OCallaghan 2006-01-02 12:29:15 UTC
Fine.