Bug 201987 - KDE crashes when a non-latin username is used on Windows
Summary: KDE crashes when a non-latin username is used on Windows
Status: RESOLVED UPSTREAM
Alias: None
Product: kde-windows
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: KDE-Windows
URL:
Keywords:
: 201972 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-07-30 12:14 UTC by Casper van Donderen
Modified: 2011-05-11 13:16 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Casper van Donderen 2009-07-30 12:14:39 UTC
Version:            (using Devel)
Compiler:          MSVC 2008 Express 
OS:                MS Windows
Installed from:    Compiled sources

When using a non-latin username and starting Dolphin kded4.exe crashes after giving a warning: "could not open file:///C:/<non-latin username>

We found out about this problem from bug 201972. Where Amarok can not open it's settings file.

It looks like the characters are not converted to unicode properly and the path's cannot be properly translated.

This seems to be a global problem in KDE-Windows.
Comment 1 Casper van Donderen 2009-07-30 12:17:54 UTC
Tested on a US Windows Vista Home Premium with a Japanese username.
Comment 2 Bernhard E. Reiter 2009-10-16 12:59:31 UTC
Andrius da Costa Ribas was so kind to take a comment of Christian Ehrlicher
and create an upstream QT problem report (and followup until it was in there):
http://qt.nokia.com/developer/task-tracker/index_html?method=entry&id=261944
Comment 3 Bernhard E. Reiter 2009-10-27 12:14:43 UTC
The qt problem report I've mentioned was transfered to the new tracker.
So hey, we can vote for it now, which I just did. ;)
http://bugreports.qt.nokia.com/browse/QTBUG-4796
Comment 4 Christian Ehrlicher 2010-01-08 19:33:38 UTC
*** Bug 201972 has been marked as a duplicate of this bug. ***
Comment 5 Casper van Donderen 2011-05-11 13:16:27 UTC
This will be fixed in Qt 4.8 (Have seen it working)