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 315831 - Can't write to LDAP-Server
Can't write to LDAP-Server
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Contacts
2.2.x (obsolete)
Other other
: Normal normal
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
: 315824 316522 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-08-25 07:43 UTC by lorentz
Modified: 2006-02-23 11:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Attachments
Patch (35.49 KB, text/plain)
2005-09-20 05:26 UTC, Sushma Rai
  Details
new patch (34.60 KB, patch)
2005-09-20 08:52 UTC, Sushma Rai
none Details | Review

Description lorentz 2005-09-09 16:29:46 UTC
Distribution: Fedora Core release 4 (Stentz)
Package: Evolution
Severity: normal
Version: GNOME2.10.0 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: Can't write to LDAP-Server
Bugzilla-Product: Evolution
Bugzilla-Component: Contacts [was: Addressbook]
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
Error Message PopUp come to tell you, "The Application
"/usr/libexec/evolution-data-server-1.2" has quit unexpectedly"


Steps to reproduce the crash:
1. Get information from Admin about login for ldapServer
2. create new LDAP-Addressbook
3. all right till now, but if you want to edit and save you get error
message

Expected Results:


How often does this happen?
Always

Additional Information:
it will be nice to edit LDAP server entries.


Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209088320 (LWP 29029)]
[New Thread -1234175056 (LWP 29046)]
[Thread debugging using libthread_db enabled]
[New Thread -1209088320 (LWP 29029)]
[New Thread -1234175056 (LWP 29046)]
[Thread debugging using libthread_db enabled]
[New Thread -1209088320 (LWP 29029)]
[New Thread -1234175056 (LWP 29046)]
[New Thread -1211188304 (LWP 29030)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x00b1b402 in ?? ()

Thread 1 (Thread -1209088320 (LWP 29029))

  • #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 server_logging_register_domain
  • #6 <signal handler called>
  • #7 ??
    from /usr/lib/evolution-data-server-1.2/extensions/libebookbackendldap.so
  • #8 e_book_backend_ldap_get_type
    from /usr/lib/evolution-data-server-1.2/extensions/libebookbackendldap.so
  • #9 ??
    from /usr/lib/evolution-data-server-1.2/extensions/libebookbackendldap.so
  • #10 g_main_context_wakeup
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #14 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #15 main
  • #0 ??




------- Bug moved to this database by unknown@gnome.bugs 2005-09-09 16:29 UTC -------


The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@gnome.bugs.
   Previous reporter was lorentz@friendship-systems.com.

Comment 1 Sushma Rai 2005-09-12 05:44:17 UTC
same problem as in 300157

If you see this problem always can you get the traces with 
debugging information?
Also if you are building Evolution from source, can you try the
patch attached ti the bug 300157?
Comment 2 Sushma Rai 2005-09-12 05:45:52 UTC
http://live.gnome.org/GettingTraces says how to get traces with debug symbols.
Comment 3 Sushma Rai 2005-09-19 06:33:13 UTC
*** Bug 316522 has been marked as a duplicate of this bug. ***
Comment 4 Jean-Paul POZZI 2005-09-19 18:09:14 UTC
Hello,

What info could I give to help ?
Comment 5 Sushma Rai 2005-09-20 05:25:35 UTC
gdb traces with debug symbols would help.

Also you can give a try to attached patch below.
Comment 6 Sushma Rai 2005-09-20 05:26:27 UTC
Created attachment 52418 [details]
Patch
Comment 7 Sushma Rai 2005-09-20 06:18:13 UTC
*** Bug 315824 has been marked as a duplicate of this bug. ***
Comment 8 Sushma Rai 2005-09-20 08:52:06 UTC
Created attachment 52425 [details] [review]
new patch
Comment 9 André Klapper 2006-01-21 22:50:49 UTC
sush: is the patch in?
Comment 10 Sushma Rai 2006-01-23 05:42:27 UTC
Yes. 2.4.2 and 2.5.1 and later releases has this fix.
lorentz, Jean-Paul POZZI:
Can any of you test this with with the newer versions?
Comment 11 Devashish Sharma 2006-02-23 11:21:15 UTC
The patch is already in, closing the bug, as nobody responding.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!