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 273290 - Evolution doesn't apply new configuration of ldap server, only after restart evolution.
Evolution doesn't apply new configuration of ldap server, only after restart ...
Status: RESOLVED DUPLICATE of bug 261783
Product: evolution
Classification: Applications
Component: Contacts
2.0.x (obsolete)
Other All
: Normal major
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
: 271817 (view as bug list)
Depends on:
Blocks: 271193 271958
 
 
Reported: 2005-03-03 16:49 UTC by erbano
Modified: 2013-09-10 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description erbano 2005-03-03 16:49:21 UTC
Description of Problem:
New configuration in ldap server are only applied after all daemons like,
evolution-data-server-1.0 died and close evolution. If I change the
configuration of my ldap server, this configuration will apply only when I
close evolution and kill process  and evolution-alarm-notify. I noticed
this because my ldap server doesn't accept ssl connections. At my first
configuration I configure using ssl connection. After this I changed it,
ldap configuration form but this configuration not applied. I think the
same problem will occur with other ldap parameters.

Steps to reproduce the problem:
1. Configure ldap server using ssl connection for example
2. Close and apply this configuration in the main form
3. Listen the connection, you will see evolution using ssl
4. In the same form change connection to does not use ssl connection
5. Listen the connection, you will see evolution using ssl but the expect
is not use ssl because the user change it in form.
6. Close evolution and kill process evolution-data-server-1.0 and
evolution-alarm-notify
7. Start again evolution
8. Listen the connection again, you will see evolution not using ssl, as
expect.
Comment 1 Sivaiah 2005-03-28 17:36:46 UTC
this is true. Once backend is loaded in e-d-s , changes happen to
e-source of the corresponding book are not propagated to e-d-s.I
believe this could be the cause of the many bugs on ldap
backend.bumping the priority 
Comment 2 Sivaiah 2005-04-25 05:36:27 UTC
*** Bug 271817 has been marked as a duplicate of this bug. ***
Comment 3 Sushma Rai 2005-08-26 06:36:00 UTC

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