Closed
Bug 267344
Opened 20 years ago
Closed 20 years ago
LDAP - Addressbook details not shown (Linux only)
Categories
(Thunderbird :: Address Book, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mozilla, Assigned: mscott)
Details
(Keywords: intl)
Attachments
(2 files)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040114 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040114 We use LDAP for contacts. TB on GNU/Linux doesn't show the details of the selected LDAP entry. The same works on Windows. See attached screenshots. Reproducible: Always Steps to Reproduce: 1. Search for someone in LDAP 2. Click on the entry Actual Results: Details of the LDAP entry are not shown Expected Results: The LDAP entry details should be shown (as on Windows) - see attached screeshot.
| Reporter | ||
Comment 1•20 years ago
|
||
Thunderbird on Windows shows the complete info about selected entry.
| Reporter | ||
Comment 2•20 years ago
|
||
TB doesn't reveal details about the chosen entry from LDAP.
Comment 3•20 years ago
|
||
Pavel, if you display dialog with Contact properties - is it filled correctly? There were problems with some contacts with non-ASCII characters (e.g. bug #151448) can you test it on some contact with only ASCII characters?
Comment 4•20 years ago
|
||
I'm wondering if there's any public LDAP server with which I can test this problem.
Keywords: intl
| Reporter | ||
Comment 5•20 years ago
|
||
We tested it: it does not matter on the actual contents of the LDAP database. The card is displayed in Windows with only ASCII letters and is not displayed *at all* in GNU/Linux. On both systems, Contact properties are displayed correctly.
Comment 6•20 years ago
|
||
> I'm wondering if there's any public LDAP server with which I can test this
problem.
Found LDAP server with public read-only access.
Shin> Sending server adress to you.Summary: Addressbook details not shown (Linux only) → LDAP - Addressbook details not shown (Linux only)
| Reporter | ||
Comment 7•20 years ago
|
||
Even unconfirmed, this bug is now fixed in Thunderbird 1.0. Thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•