Bug 246654

Can you explain in detail how to reproduce this please?

Just simply copy and paste the text in the original comment into an xterm, then
try to do it with konsole or gnome-terminal.  You will discover the text is only
properly displayed in the xterm console.

This is reproducible also in Fedora 8.

At this point, we're going to only be taking security fixes and major stability
fixes into this release of Fedora.  However, we still want to ensure the bug is
fixed in the next version.  We'd appreciate if you could test Firefox 3,
available at http://www.mozilla.com/en-US/firefox/all-beta.html or now shipping
as the default in Fedora rawhide and provide feedback as to whether it still
exists so we can file a ticket upstream to try to fix it in Firefox 3 before it
is released.

At this point, we're going to only be taking security fixes and major stability
fixes into this release of Fedora.  However, we still want to ensure the bug is
fixed in the next version.  We'd appreciate if you could test Firefox 3,
available at http://www.mozilla.com/en-US/firefox/all-beta.html or now shipping
as the default in Fedora rawhide and provide feedback as to whether it still
exists so we can file a ticket upstream to try to fix it in Firefox 3 before it
is released.

Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
information.

Closing as INSUFFICIENT_DATA.

[This is a mass-closing request, if you think that this bug shouldn't be closed,
please, reopen with additional information.]

What total bull crap.  I cannot test firefox 3 until it is available in a stable
release of fedora.

I like your plan of action, "please test something which is not available", oh
since you cannot test this, I'm closing the bug.

Using a 3rd party repo (remi) I tested minefield and it appears the bug still exits.

OK, I screwed up on this bug. I am sorry.

However, this is really not firefox fault. When testing with gnome-terminal and
xterm, it works well with xterm (will attach screenshots for both), but not with
gnome-terminal. Which leads directly to the possible candidate for this issue,
which is pango (used by all Gnome apps & firefox, but not by xterm). Reassigning.

And it is well reproducible with Rawhide.

Created attachment 302030 [details]
reproducing the bug with Rawhide gnome-terminal

Created attachment 302031 [details]
not reproducible with xterm

Using
xterm-234-1.fc9.i386
gnome-terminal-2.22.1-1.fc9.i386
pango-1.20.1-1.fc9.i386

xterm probably still uses the old legacy so-called core X11 support. Pretty much
everything else uses the new (for more-than-five-years-old values of new)
fontconfig font system. The core X11 font backend and the fontconfig backend do
not have access to the same fonts (in particular we do not install old fonts in
weird formats in fontconfig, and we do not install modern complex fonts in core
X11).

Install a modern font package instead of the one you're using in xterm and
you'll be fine.

gnome-terminal by default uses vte's xft backend, not pango.

It will definitely be a pango bug if you can reproduce it in gedit.  Otherwise,
it may be someone else at fault.

Created attachment 302865 [details]
reproduction in gedit (compating with xterm)

(In reply to comment #12)
> gnome-terminal by default uses vte's xft backend, not pango.
> 
> It will definitely be a pango bug if you can reproduce it in gedit.
> Otherwise, it may be someone else at fault.

Well, did you try? ;-)

Ah, so by doesn't show up the reporter means hexboxes are drawn.  Easy one. 
Install a proper font.  xterm works because you have a bitmap X font installed
that covers those chars.  Anything using client-side fonts doesn't work.