flathub / flathub/org.gnome.Evolution
Cannot connect to LDAP anymore
- Dominant language
- No language data
- Stars
- 8
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
After updating my system to Fedora Silverblue 32 I cannot connect to my LDAP server anymore.
I removed ~/.var/app/org.gnome.Evolution to start from scratch but this did also not help.
1.
When I add an addressbook I cannot remove it anymore. I always get the error message: The name ist not activatable".
2.
When click on "Find possible Search Bases" I get an error message (see screenshot) and when I check the logs from my LDAP server I see that the dn is missing. Since anonymous access is not allowed this fails (I am not sure whether this search worked before, I only used this here for debuging).
```
5e922250 slap_listener_activate(6):
5e922250 >>> slap_listener(ldap:///)
5e922250 connection_get(12): got connid=1062
5e922250 connection_read(12): checking for input on id=1062
ber_get_next
ber_get_next: tag 0x30 len 12 contents:
5e922250 op tag 0x60, time 1586635344
ber_get_next
5e922250 conn=1062 op=0 do_bind
ber_scanf fmt ({imt) ber:
ber_scanf fmt (m}) ber:
5e922250 >>> dnPrettyNormal: <>
5e922250 <<< dnPrettyNormal: <>, <>
5e922250 do_bind: version=3 dn="" method=128
5e922250 send_ldap_result: conn=1062 op=0 p=3
5e922250 send_ldap_response: msgid=1 tag=97 err=48
ber_flush2: 39 bytes to sd 12
5e922250 do_bind: v3 anonymous bind
5e922250 connection_get(12): got connid=1062
5e922250 connection_read(12): checking for input on id=1062
ber_get_next
ber_get_next: tag 0x30 len 5 contents:
5e922250 op tag 0x42, time 1586635344
ber_get_next
5e922250 ber_get_next on fd 12 failed errno=0 (Success)
5e922250 conn=1062 op=1 do_unbind
5e922250 connection_close: conn=1062 sd=12
```
3.
When I click on "OK" I again get the message "The name is not activatable".
4.
The address book does not work. If I search something nothing is found. Also I don't see any activities in the LDAP logs.
I use version 3.36.1. Before the upgrade everything was working.
When I do LDAP request on the command line with ldapsearch it is also working as before.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.