errors on ubuntu-bug firefox

[Thomas]

Binary package hint: firefox

I get some error messages when I enter

ubuntu-bug firefox
hook /usr/share/apport/package-hooks//firefox.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/apport/report.py", line 619, in add_hooks_info
    symb['add_info'](self)
  File "/usr/share/apport/package-hooks//firefox.py", line 184, in add_info
    extension_summary += extension_summary_helper(extensions_dict['local_extensions'], 'Local Extensions')
  File "/usr/share/apport/package-hooks//firefox.py", line 80, in extension_summary_helper
    summary += ''' %s\n''' % install_ini_parser(extension)
  File "/usr/share/apport/package-hooks//firefox.py", line 52, in install_ini_parser
    dom_doc = minidom.parse(rdf_file)
  File "/usr/lib/python2.6/xml/dom/minidom.py", line 1918, in parse
    return expatbuilder.parse(file)
  File "/usr/lib/python2.6/xml/dom/expatbuilder.py", line 924, in parse
    result = builder.parseFile(fp)
  File "/usr/lib/python2.6/xml/dom/expatbuilder.py", line 207, in parseFile
    parser.Parse(buffer, 0)
ExpatError: not well-formed (invalid token): line 48, column 28

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: firefox 3.6.8+build1+nobinonly-0ubuntu0.10.04.1
Uname: Linux 2.6.35-020635rc6-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Wed Jul 28 10:10:17 2010
EcryptfsInUse: Yes
FirefoxPackages:
 firefox 3.6.8+build1+nobinonly-0ubuntu0.10.04.1
 firefox-gnome-support 3.6.8+build1+nobinonly-0ubuntu0.10.04.1
 firefox-branding 3.6.8+build1+nobinonly-0ubuntu0.10.04.1
 abroswer N/A
 abrowser-branding N/A
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.utf8
 SHELL=/bin/bash
SourcePackage: firefox

[papukaija (papukaija)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 603396, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.