After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 599373 - Russian (cyrrilic) shares names display incorrectly
Russian (cyrrilic) shares names display incorrectly
Status: RESOLVED INVALID
Product: gvfs
Classification: Core
Component: smb backend
1.4.x
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2009-10-23 02:51 UTC by Nikolay Martynov
Modified: 2014-06-02 08:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Nikolay Martynov 2009-10-23 02:51:05 UTC
I have Russian Windows XP on my network and when I try to open shares in nautilus on it I see strange letters for shares with russian names (something like "䫬ҼѡÔÙ"). And I cannot open such shares.

OS: ubuntu 9.10

here is gvfsd -r output when I try to open such share:
kolya@kolya-laptop:~$ GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd -r
Added new job source 0x8363068 (GVfsBackendSmb)
Queued new job 0x8363c20 (GVfsJobMount)
send_reply, failed: 1
Comment 1 Yuri Sbitnev 2009-11-11 04:50:03 UTC
I have got a same problem with Ubuntu 9.10 & GNOME 2.28.1. Windows shares with cyrillic names not properly visible. (Strange symbols). Shares with latinic names - OK. Cyrillic directories within shares also OK.
Comment 2 Yuri Sbitnev 2009-11-11 06:22:15 UTC
Wow! It's not GNOME bug. It's SAMBA bug. 

Workaround: 

Add parameter "dos charset = CP866" to global section of smb.conf and reboot system.
After reboot everything will be OK.
Comment 3 Ross Lagerwall 2014-05-31 19:53:53 UTC
gvfs doesn't mess with the text encoding given by libsmbclient and AFAIK libsmbclient doesn't give any way of changing it.

If things aren't being displayed properly, then you probably need to set your charset as Yuri mentioned.
Comment 4 Bastien Nocera 2014-06-02 08:57:13 UTC
(In reply to comment #3)
> gvfs doesn't mess with the text encoding given by libsmbclient and AFAIK
> libsmbclient doesn't give any way of changing it.

Not programmatically, but it can use a user-wide smb.conf file (not necessarily a system-wide one).