257831 - pango UTF8 warnings during custom install on Linux, Red Hat 8.0

Status: VERIFIED DUPLICATE of bug 280740

(Firefox :: Installer, defect)

Description

[Jeremy M. Dolan]

In the Linux installer (today's aviary nightly), selecting a Custom install
type, and hitting next creates six identical pango warnings:

** (firefox-installer-bin:10059): WARNING **: Invalid UTF8 string passed to
pango_layout_set_text()

** (firefox-installer-bin:10092): WARNING **: Invalid UTF8 string passed to
pango_layout_set_text()

etc


Presumably related to those three component select boxes, as that seems to be
the only widget not elsewhere in the installer. Going forward or back in the
installer, and returning to this part of the process does not cause any further
warnings to be printed.

Comment 1

[Jeremy M. Dolan]

Sorry, going through a ton of installer issues to report, meant to include the
following:

Red Hat Linux release 8.0 (with all RPM updates applied)
gtk2-2.0.6-8
gtk2-engines-1.9.0-4
pango-1.1.1-1

Comment 2

[Aaron C. de Bruyn]

I can confirm this on Fedore Core 2 as well after running the installer
downloaded from the home page (v1.0PR I believe).

# ./firefox-installer
 
** (firefox-installer-bin:25495): WARNING **: Invalid UTF8 string passed to
pango_layout_set_text()
 
** (firefox-installer-bin:25495): WARNING **: Invalid UTF8 string passed to
pango_layout_set_text()
 
** (firefox-installer-bin:25495): WARNING **: Invalid UTF8 string passed to
pango_layout_set_text()
 
** (firefox-installer-bin:25495): WARNING **: Invalid UTF8 string passed to
pango_layout_set_text()
[root@elorg firefox-installer]# ***
nsExtensionManager::_disableObsoleteExtensions - failure, catching exception so
finalize window can close
*** loading the extensions datasource
*** loading the extensions datasource
 
Unfortunately I wasn't paying too much attention and I did not see what step in
the installer generated the messages.

Comment 3

[Scott Gifford]

I see this in RC2 on Fedora Core 2.

Comment 4

[Neil Paris]

*** Bug 267668 has been marked as a duplicate of this bug. ***

Comment 5

[Andrew Schultz]

*** Bug 270969 has been marked as a duplicate of this bug. ***

Comment 6

[Andrew Schultz]

this was fixed by the patch in bug 280740

*** This bug has been marked as a duplicate of 280740 ***