Bug 6822 - Clients failed to browse shares if share comments contain multi-bytes char
Summary: Clients failed to browse shares if share comments contain multi-bytes char
Status: RESOLVED WORKSFORME
Alias: None
Product: Samba 3.3
Classification: Unclassified
Component: Config Files (show other bugs)
Version: 3.3.8
Hardware: x86 Linux
: P3 normal
Target Milestone: ---
Assignee: Karolin Seeger
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-17 02:15 UTC by Philippe L
Modified: 2009-11-23 01:57 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe L 2009-10-17 02:15:12 UTC 
I'm using regular Mandriva 2009.1 updated with samba 3.3.8 (all plateforme is UTF-8).
I'm using the same smb.conf file for years.
I noticed, since the last upgrade, that clients can no longer browse server shares.
Activating detailed log, I noticed the following lignes :
****
[2009/10/17 09:05:05,  3] lib/charcnv.c:convert_string_internal(263)
  convert_string_internal: Conversion error: Illegal multibyte sequence(épertoire prive de philippe)
****
I had this message when enumerating each share that have french "accents" in the comment properties.
Removing the accents in the comments eliminate the issue and reenable clients to browse shares.
Restablishing the accents reproduce the problem immediately. Not a big issue as the workaround is easy but this can be disturbing production systems until the workaround is applied.
Hope this may help
Thanks
Comment 1 Karolin Seeger 2009-10-19 05:24:54 UTC 
Hmm, I am not able to reproduce this with 3.3.8.
smbclient and Windows display the comment containing the accents properly.
All shares are listed in the network environment.
Can you tell me what exactly fails for you, please?

Thanks!
Comment 2 Karolin Seeger 2009-11-23 01:57:44 UTC 
Cannot reproduce and no feedback from reporter.
Closing out bug report.

Please feel free to reopen if it's still an issue.

Thanks!