Version: (using KDE 4.1.2) OS: Linux Installed from: Compiled From Sources I am chinese, so I want use chinese user name to login in my computer. I add a user "潘" through kuser(compiling from svn), and I set Language=zh_CN.UTF-8 in /etc/kde/kdm/kdmrc. Then restart X, kdm displays my name "潘" perfectly, but when I input my password, press enter, a message box appears "Could not start kstartupconfig4. Check your installation." Then It stops. Then I login in safe mode, run kdeinit4, got some error messages: trying to create local folder /home/.kde: Permission denied trying to create local folder /home/.kde: Permission denied Link points to "/tmp/ksocket-潘" trying to create local folder /home/.kde: Permission denied kdeinit4: Aborting. bind() failed: : No such file or directory Could not bind to socket '/home/.kde/socket-localhost.localdomain/kdeinit4__0' I infer that kdeinit4 doesn't get my "HOME" environment correctly, so it tries to create local folder in /home/.kde, of course Permission denied. I think it's necessary to support non ASCII user name to login in for our convenience.
Created attachment 27843 [details] supporting non ASCII user name to login in apply to kdelibs/kinit/
Created attachment 27844 [details] supporting non ASCII user name to login in apply to /kdebase/workspace/kstartupconfig
I don't see how those parches can help solve this bug.
The username should actually work fine. Please try setting the correct locale before launching kdm and check if your /etc/passwd file has the name with the right encoding as well.
hmm, this is actually a bit different than i gathered from skimming over it ... but at some place it *is* an encoding problem - somewhere in kdelibs or qt, possibly only due to some variable not being set, so the michael's comment might be relevant, even if not directly. anyway, chinese login names are no particularly good idea. these are system-level identifiers. non-ascii is almost as sensible as embedded spaces. you can expect more things to break when least expected.
Moving this bug to kdelibs, since it is a more appropriate place, so more likely to get attention there.
some patches related to charset conversion (iconv) initialization have gone into both qt and kde recently. thiago, could this problem be fixed now?
Yes, it's fixed. But this problem only existed in the Qt 4.5 pre-releases. This problem did not exist in Qt 4.4.
What is the status of this bug? Do the patches from comment #1 and comment #2 still need to be applied? Thanks.
i think this can be closed ...