Summary: | plasma crashes when LANG is set to ja_JP.* and a window pops up | ||
---|---|---|---|
Product: | [Unmaintained] kdelibs | Reporter: | Koji Yokota <yokota> |
Component: | general | Assignee: | kdelibs bugs <kdelibs-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | cfeck, generatorglukoff, mpyne, yokota |
Priority: | NOR | Keywords: | triaged |
Version: | 4.1 | ||
Target Milestone: | --- | ||
Platform: | FreeBSD Ports | ||
OS: | FreeBSD | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Koji Yokota
2008-08-27 06:15:12 UTC
This bug is still persistent in KDE 4.1.1, not only for FreeBSD but also other Linux systems. Is there any additional information I can provide for this bug? Judging from comments on web, this seems a well-known bug among Japanese users, making them hesitate to move toward KDE4. Well I've installed the Japanese language translation and have even gone so far as to run Plasma completely in Japanese (using KDE_LANG=ja, not LANG or LC* however). Unable to reproduce with /trunk (and presumably from KDE 4.2) As far as things that would help, a reproducable testcase. Given that this only happens with some windows and it has something to do with translation I would assume it occurs from an i18n() call, and specifically one that uses the "scripted translation" feature (which is the klocalizedstring.cpp:296 part). Somehow the scripted translation is causing the crash, so to troubleshoot the crash it would help to find out what the translated version of the crashing message is. OK, thank you. I'm going to identify the source of the problem. I tried only with KDE_LANG=ja, without setting LANG or LC*, but the problem didn't go away. Same here (using LANG=ru_RU.UTF-8). I made valgrind log and it shows problem in KLocalizedString. OS: Gentoo Linux KDE compiled with debug info. Here the valgrind log: http://omploader.org/vMThtaw/plasma.log It's 8Mb in size, so bugzilla refused to upload it. it seems fixed in trunk: http://websvn.kde.org/?view=rev&revision=918505 Yes, that part seems to be fixed. However, it doesn't seem to be the only source of the problem. Crash still continues with KDE 4.2.1 at my place. What is the status of this bug in recent KDE versions, such as 4.6.5 or 4.7? Please add a comment. If you can provide the information requested in comment #8, please add it. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |