Bug 172567

Summary:	Can't we support non ASCII user name to login in ?
Product:	[Unmaintained] kdelibs	Reporter:	潘卫平 <wppan>
Component:	general	Assignee:	kdelibs bugs <kdelibs-bugs>
Status:	RESOLVED FIXED
Severity:	crash	CC:	cfeck, grundleborg, lemma, mumismo, thiago
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	supporting non ASCII user name to login in supporting non ASCII user name to login in

Description 潘卫平 2008-10-11 07:05:41 UTC

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.

Comment 1 潘卫平 2008-10-13 06:57:26 UTC

Created attachment 27843 [details]
supporting non ASCII user name to login in

apply to kdelibs/kinit/

Comment 2 潘卫平 2008-10-13 07:00:37 UTC

Created attachment 27844 [details]
supporting non ASCII user name to login in

apply to /kdebase/workspace/kstartupconfig

Comment 3 Jordi Polo 2008-11-29 13:34:20 UTC

I don't see how those parches can help solve this bug.

Comment 4 Michael Leupold 2008-12-08 00:29:38 UTC

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.

Comment 5 Oswald Buddenhagen 2008-12-08 21:50:00 UTC

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.

Comment 6 George Goldberg 2009-04-07 22:59:10 UTC

Moving this bug to kdelibs, since it is a more appropriate place, so more likely to get attention there.

Comment 7 Oswald Buddenhagen 2009-04-11 14:14:28 UTC

some patches related to charset conversion (iconv) initialization have gone into both qt and kde recently. thiago, could this problem be fixed now?

Comment 8 Thiago Macieira 2009-04-11 15:21:22 UTC

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.

Comment 9 Christoph Feck 2009-06-01 04:38:18 UTC

What is the status of this bug? Do the patches from comment #1 and comment #2 still need to be applied? Thanks.

Comment 10 Oswald Buddenhagen 2009-06-20 14:36:48 UTC

i think this can be closed ...