Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 917004

Summary: convert_string_talloc: Conversion error: Illegal multibyte sequence trying to list users with pdbedit
Product: Red Hat Enterprise Linux 6 Reporter: Javier Coscia <jcoscia>
Component: sambaAssignee: Andreas Schneider <asn>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: high Docs Contact:
Priority: high    
Version: 6.3CC: asn, gdeschner, jcoscia
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-24 09:08:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
smb.conf none

Description Javier Coscia 2013-03-01 12:28:42 UTC
Description of problem:

When customer tries to list users with Spanish characters, under full name, with the command pdbedit he gets the mentioned error message.

Version-Release number of selected component (if applicable):

Samba version:

samba-3.5.10-125.el6.x86_64                                 Thu 14 Feb 2013 03:42:16 PM ART
samba-client-3.5.10-125.el6.x86_64                          Thu 14 Feb 2013 03:43:36 PM ART
samba-common-3.5.10-125.el6.x86_64                          Thu 14 Feb 2013 03:42:15 PM ART
samba-winbind-clients-3.5.10-125.el6.x86_64                 Thu 14 Feb 2013 03:42:12 PM ART

How reproducible:
Always


Steps to Reproduce:
1. Have users with Spanish characters (ñ, é, á, etc) under full name, i.e. José Alejandro
2. pdbedit -v -u joscap_minplan

  
Actual results:
convert_string_talloc: Conversion error: Illegal multibyte sequence(� Alejandro Caputo)

Expected results:
User's information without convert_string_talloc error message.

Comment 2 Andreas Schneider 2013-03-01 13:02:37 UTC
Which backend is the customer using to store the users? Could you perhaps post the smb.conf?

Comment 3 Javier Coscia 2013-03-01 13:10:05 UTC
Created attachment 704155 [details]
smb.conf

Hi Andreas, I'm attaching the smb.conf file requested,
Customer is using ldap backend (openldap)
I've requested him to upload the ldif file as well, will attach it to the case as soon as I have it.

Cheers
jcoscia

Comment 4 Andreas Schneider 2013-03-01 15:37:47 UTC
What is the type of the full name?

A LDAPString is per RFC4511 needs to be utf8 encoded. If you write (modify) an entry and you don't use utf8 openldap will give you an error.

The only possibility that this is not UTF8 is that they use a data binary type (octet) or filled these data in 10 years ago.

If you dump this database and then load it with a current openldap version for sure it will fail to parse these entries (or maybe it will convert them).

IIRC with OpenLDAP 2.1 (LDAPv3) came the utf8 requirement which was in 2002.

Comment 6 Andreas Schneider 2013-04-24 09:08:19 UTC
This is really a case where the customer should dump the data, re-encode it to UTF-8 and push it back to the LDAP server.

Closing the bug.