Bug 12229 - drakdisk incorrectly displays samba shares with non-latin names
Summary: drakdisk incorrectly displays samba shares with non-latin names
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-07 12:20 CET by Oleg Bosis
Modified: 2016-10-17 22:23 CEST (History)
3 users (show)

See Also:
Source RPM: drakxtools-16.18-2.mga4.src.rpm
CVE:
Status comment:


Attachments
Screenshot that shows coorupt shares names in diskdrake and normal names in dolphin (208.06 KB, image/png)
2014-01-07 12:22 CET, Oleg Bosis
Details

Description Oleg Bosis 2014-01-07 12:20:11 CET
Description of problem:
I had already reported this problem in 2010 in mandriva bugzilla (https://qa.mandriva.com/show_bug.cgi?id=59290 ) but the bug is still here: if I try to find and mount existing samba shares using Mageia Control Center I see all non-latin names of the shares corrupted.

Version-Release number of selected component (if applicable):
drakxtools-16.18-2.mga4.src.rpm

How reproducible:
always

Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Oleg Bosis 2014-01-07 12:22:49 CET
Created attachment 4733 [details]
Screenshot that shows coorupt shares names in diskdrake and normal names in dolphin

This is a fresh screenshot with corrupt non-latin samba shares names done in current Mageia Cauldron installation in virtual machine.

CC: (none) => olegbosis

Comment 2 Thierry Vignaud 2014-01-08 00:02:33 CET
This is why Unicode was promoted...

CC: (none) => thierry.vignaud
Summary: drakdisk incorrectly displays sabma shares with non-latin names => drakdisk incorrectly displays sama shares with non-latin names

Comment 3 Oleg Bosis 2014-01-08 09:46:34 CET
(In reply to Thierry Vignaud from comment #2)
> This is why Unicode was promoted...

Why you've changed 'samba' with 'sama' in summary? And what your comment means?
Comment 4 Thierry Vignaud 2014-01-08 14:12:58 CET
Uh? I removed a comma (",") and set it to "Samba".
This is why I see when looking at this page, however I see "sama" in history.
I don't understand????

As for UTF-8, this mean we should try to use UTF-8 everywhere instead of legacy encoding.
However there're still environments not using Unicode, like the one where is your computer

Summary: drakdisk incorrectly displays sama shares with non-latin names => drakdisk incorrectly displays samba shares with non-latin names

Comment 5 Oleg Bosis 2014-01-08 16:31:12 CET
No, I do use UTF-8, and I do use it for many years:

$ locale
LANG=ru_RU.UTF-8
LC_CTYPE=ru_RU.UTF-8
LC_NUMERIC=ru_RU.UTF-8
LC_TIME=ru_RU.UTF-8
LC_COLLATE=ru_RU.UTF-8
LC_MONETARY=ru_RU.UTF-8
LC_MESSAGES=ru_RU.UTF-8
LC_PAPER=ru_RU.UTF-8
LC_NAME=ru_RU.UTF-8
LC_ADDRESS=ru_RU.UTF-8
LC_TELEPHONE=ru_RU.UTF-8
LC_MEASUREMENT=ru_RU.UTF-8
LC_IDENTIFICATION=ru_RU.UTF-8
LC_ALL=

So it seems like diskdrake does not understand Unicode names...
Comment 6 Rémi Verschelde 2015-09-10 16:50:33 CEST
Is this bug still valid in Mageia 5 or cauldron?
Comment 7 Marja Van Waes 2016-10-15 23:48:15 CEST
(In reply to Rémi Verschelde from comment #6)
> Is this bug still valid in Mageia 5 or cauldron?

@ Oleg

Is it?

Keywords: (none) => NEEDINFO
CC: (none) => marja11
Assignee: bugsquad => mageiatools

Comment 8 Oleg Bosis 2016-10-17 19:59:14 CEST
I don't know about cauldron but it is still valid for Mageia 5.

Additional info: if I add some new folder with Russian words in its name to share then Russian folder name is displayed correctly. But only until I close drakdisk and reopen it. Then all previously created shares with Russian names (including the new one) are corrupted. It seems like drakdisk uses wrong encoding when reading smb.conf (should be UTF-8)...

BTW 'comment' should *not* be mandatory field when creating new samba share...
Samuel Verschelde 2016-10-17 22:23:22 CEST

Keywords: NEEDINFO => (none)


Note You need to log in before you can comment on or make changes to this bug.