Bug 141217

Summary: Many KDE programs are crashing in Japanese locale
Product: [openSUSE] SUSE Linux 10.1 Reporter: Mike Fabian <mfabian>
Component: KDEAssignee: Mike Fabian <mfabian>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: sndirsch
Version: Alpha 1   
Target Milestone: ---   
Hardware: Other   
OS: Linux   
Whiteboard:
Found By: Development Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Mike Fabian 2006-01-03 11:23:36 UTC
Example:

    mfabian@shannon:~$ locale
    LANG=ja_JP.UTF-8
    LC_CTYPE="ja_JP.UTF-8"
    LC_NUMERIC="ja_JP.UTF-8"
    LC_TIME="ja_JP.UTF-8"
    LC_COLLATE="ja_JP.UTF-8"
    LC_MONETARY="ja_JP.UTF-8"
    LC_MESSAGES="ja_JP.UTF-8"
    LC_PAPER="ja_JP.UTF-8"
    LC_NAME="ja_JP.UTF-8"
    LC_ADDRESS="ja_JP.UTF-8"
    LC_TELEPHONE="ja_JP.UTF-8"
    LC_MEASUREMENT="ja_JP.UTF-8"
    LC_IDENTIFICATION="ja_JP.UTF-8"
    LC_ALL=
    mfabian@shannon:~$ konsole
    kbuildsycoca running...
			   Creating link /suse/mfabian/.kde/socket-shannon.
    Created link from "/suse/mfabian/.kde/socket-shannon" to "/tmp/ksocket-mfabian"
    Creating link /suse/mfabian/.kde/tmp-shannon.
    Created link from "/suse/mfabian/.kde/tmp-shannon" to "/tmp/kde-mfabian"
    kbuildsycoca running...
    Creating link /suse/mfabian/.kde/cache-shannon.
    Created link from "/suse/mfabian/.kde/cache-shannon" to "/var/tmp/kdecache-mfabian"
    *** glibc detected *** corrupted double-linked list: 0xb7f224d8 ***
    DCOP Cleaning up dead connections.
				      アラームクロック
    mfabian@shannon:~$

In German locale it works:

    mfabian@shannon:~$ LANG=de_DE.UTF-8 konsole
    kbuildsycoca running...
    mfabian@shannon:~$

The problem happens on i386 and x86_64, i.e it doesn't seem to be
architecture dependent.
Comment 1 Dirk Mueller 2006-01-03 11:57:15 UTC
is this after the libXft fix we did yesterday? Qt3 still uses libXft. 

Comment 2 Mike Fabian 2006-01-03 12:57:50 UTC
Happens before *and* after the libXft fix we did yesterday.
Comment 3 Lubos Lunak 2006-01-03 13:53:28 UTC
That's very likely this: http://lists.freedesktop.org/archives/fontconfig/2006-January/001848.html . Either apply the patch or simply update whole fontconfig, that should take care of it.
Comment 4 Mike Fabian 2006-01-03 15:00:59 UTC
Yes, indeed, updating fontconfig to the latest CVS (2.4 branch)
helps. Thank you!

Submitted to STABLE.

Closing as FIXED.