[Xfce-bugs] [XFCE 0000202]: taskbar crashes when window title contains incorrect UTF-8

[xfce-bugs at xfce.org]

A BUGNOTE has been added to this bug.
=======================================================================
http://bugs.xfce.org/view_bug_page.php?f_id=0000202
=======================================================================
Reporter:                   Flammie
Handler:                    
=======================================================================
Project:                    XFCE
Bug ID:                     0000202
Category:                   panel
Reproducibility:            sometimes
Severity:                   major
Priority:                   normal
Status:                     new
=======================================================================
Date Submitted:             2004-05-22 13:15 GMT
Last Modified:              2004-05-25 20:17 GMT
=======================================================================
Summary:                    taskbar crashes when window title contains incorrect UTF-8
Description: 
Some applications that handle files (most often jEdit) do not check if the
filename of opened file is encoded using proper utf-8 while utf-8 locale
is used. When they try to display the filename in application titlebar,
xftaskbar will crash. Some applications, even though they do duplicate
incorrect filenames in title, do not crash the titlebar, I believe this is
caused by these applications checking the validity beforehands.

Distribution is gentoo. XFCE version is 4.0.5. Locale is fi_FI.UTF-8.
=======================================================================

-----------------------------------------------------------------------
 olivier - 2004-05-23 19:39 GMT 
-----------------------------------------------------------------------
do you have a backtrace?

-----------------------------------------------------------------------
 Flammie - 2004-05-24 00:15 GMT 
-----------------------------------------------------------------------
Is there a simple way to get a proper backtrace. The thing has been
compiled using gentoo's portage apparently without debug information so
gdb won't help much. Strace would indicate that the problem lies in
pango-hangul-fc.so, which I think has been an open bug for quite some time
and most projects have somehow patched around it.

Digging more about the problem it would seem that the bug is same as one
reported in Gnome's Bugzilla:
http://bugs.gnome.org/show_bug.cgi?id=138446, and it might actually relate
to some specific broken sequences: those which appear at hangul jamo plane

-----------------------------------------------------------------------
 kelnos - 2004-05-24 03:29 GMT 
-----------------------------------------------------------------------
well, you could turn of binary/library stripping in portage and recompile.

either way, a stripped binary should give a semi-useful stacktrace, at
least it should have function names even if the line numbers won't be
there.

-----------------------------------------------------------------------
 Flammie - 2004-05-24 18:30 GMT 
-----------------------------------------------------------------------
So, this would be sufficient:
(gdb) backtrace
http://bugs.xfce.org/view_bug_page.php?f_id=0  0x40c9f443 in ?? () from
/usr/lib/pango/1.4.0/modules/pango-hangul-fc.so
http://bugs.xfce.org/view_bug_page.php?f_id=1  0x080ca378 in ?? ()
http://bugs.xfce.org/view_bug_page.php?f_id=2  0x0000ffc3 in ?? ()
http://bugs.xfce.org/view_bug_page.php?f_id=3  0xbfffbee8 in ?? ()
http://bugs.xfce.org/view_bug_page.php?f_id=4  0x4067d258 in g_utf8_strlen
() from /usr/lib/libglib-2.0.so.0
http://bugs.xfce.org/view_bug_page.php?f_id=5  0x40c9f9c4 in ?? () from
/usr/lib/pango/1.4.0/modules/pango-hangul-fc.so
http://bugs.xfce.org/view_bug_page.php?f_id=6  0x080ca378 in ?? ()
http://bugs.xfce.org/view_bug_page.php?f_id=7  0xbfffbf30 in ?? ()
http://bugs.xfce.org/view_bug_page.php?f_id=8  0x00000003 in ?? ()
http://bugs.xfce.org/view_bug_page.php?f_id=9  0x080f64b8 in ?? ()
http://bugs.xfce.org/view_bug_page.php?f_id=10 0xbfffbf68 in ?? ()

Right?

-----------------------------------------------------------------------
 kelnos - 2004-05-24 19:02 GMT 
-----------------------------------------------------------------------
no need for sarcasm - sometimes they're useful, sometimes not.  this is
obviously the latter case.

-----------------------------------------------------------------------
 Flammie - 2004-05-24 19:25 GMT 
-----------------------------------------------------------------------
No, sorry if it came out a bit harsh, it wasn't intended. It does give you
the impression on how g_utf8_strlen() might also use the string in
offending way and thus suggest that you must validate the string even
before any other glib function might get called.

-----------------------------------------------------------------------
 olivier - 2004-05-24 19:34 GMT 
-----------------------------------------------------------------------
Frankly, it looks like a bug in pango or glib to me.

-----------------------------------------------------------------------
 olivier - 2004-05-25 19:14 GMT 
-----------------------------------------------------------------------
can you tar an offending file (so I can get the exact sequence of caracters
taht cause the crash) and attach it to this report?

TIA
Olivier.

-----------------------------------------------------------------------
 Flammie - 2004-05-25 19:30 GMT 
-----------------------------------------------------------------------
Attached file contains one file from my java project which causes the
crash, the supposed name of file is EiJärkevääToteuttaaPoikkeus.java, the
borked version has ä's replaced with something strange.

-----------------------------------------------------------------------
 olivier - 2004-05-25 20:17 GMT 
-----------------------------------------------------------------------
The crash doesn't occur here, all I get is "?" in place of the accentuated
characters.

I did try with LANG set to fi_FI.UTF-8 and "jedit 4.1final". I've also
tried with LANG set to C and also fi_FI but I could not reproduce the
crash in any case.