Version: (using KDE KDE 3.0.4) Installed from: SuSE RPMs OS: Linux if I try to open a share on a windows-pc which contains a german umlaut, i get the message: Die Datei oder das Verzeichnis smb://something/with/german/umlaut/ existiert nicht the file or the directory smb://.... does not exist I use Samba 2.2.6-SuSE. the linux-pc is connected to a domain and i already tried to change the character settings in smb.conf to different values, but it didn't help If you need more info, contact me
It happens with 3.0.3 and/or Samba 2.2.5-SuSE as well. I have this problem with WinNT (Service Pack 6) and Windows XP. With WinME the problem does not arise though the Umlauts are displayed as spaces (' '). This bug is deadly for productivity within (company) networks!!!
I have the same problem here with scandic chars. It makes our Linux migration a bit hard, because we have lot information in NT domains.
More info: starting Konquerer creates the file ~/.smb/smb.conf which contains only the (samba) workgroup. The system samba config (/etc/samba/smb.conf) seems to be ignored by Konquerer (or libsmbclient?). Workaround: replace ~/.smb/smb.conf by /etc/samba/smb.conf (copy over or symlink to it). restart Konquerer and see it working. You also should replace SuSE Samba 2.2.5 by samba 2.2.6 that you can find on www.samba.org (SuSE rpm package). 2.2.5 (lib)smbclient has problems with WinME and Win98. Maybe the whole thing is not a KDE/Konquerer problem... but who finds out?
*** Bug 34715 has been marked as a duplicate of this bug. ***
if you do a smbclient call on this host, you'll see that it will display it incorrect too. (also the smbclient doesn't read ~/.smb btw) The umlauts are transfered as code page 850 and I wasn't able to change smb.conf to make smbclient show it correctly. Too bad ;(
this is supposed to be fixed with samba 3 (to be released soon)
I don't have a windows machine at hand to test. I tried with samba 2.2.0 (both server and client) to access files containing umlaute and stuff, and it works for me. Alex
This is not an SMB but a KDE framework problem. The way KDE stats and accesses files is based on the curren $LANG (usually UTF-8). If you are trying to access files that have other encoded chars (like ISO-8859-*, used by MS) in their filenames, their names will be readen (incorrectly) as UTF-8, leading to unaccessible filenames. To workaround, change your system $LANG setting to the one you have your legacy data. I'm in Brazil, so I have to set: export LANG=pt_BR.ISO-8859-15, and then run KDE. You can't set it from inside a running KDE, and then run a uniq app. It will disconsider the last set, falling back to the one set on KDE startup.
If that is so, this is the same problem as found in bug #56197, except that case is over FTP and this is SMB. It is a general to all ioslaves, except those few that transmit filenames in Unicode already. We need to specify some sort of configuration to the ioslaves as to what charset to use to interpret remote filenames, much like the way we do now specify the charset KHTML is to use when reading a webpage. In the specific case of SMB, Samba 3.0 will support Unicode over the wire, which means it will be the remote site's fault if the encoding is broken. Until that happens, Samba 2.2 transmits filenames over 8-bit encoding, never UTF-8.
it can't be fixed with samba 2 and it _is_ fixed with samba 3 (for smb-libsmb - as samba 3 finally installs libsmb per default, this is less than theoretically :).