Firefox profile corruption

[Thomas Majewski]

Third time in a week... Firefox 12.0 launches with a dialog box warning that "some security elements could not be installed and that this is probably a problem with the application's profile....
I can delete the profile and restore Firefox but the problem repeats itself on this new install of 12.04 LTS.
When I try to access it from the terminal with "firefox --profile [dir]" I get a dialog box that says that the profile is unavailable or missing. When this failure occurs the firefox browser does launch however it will not connect with the internet.

When I launched firefox with the profile command it did print out some information however am not savvy enough to figure out what it implies regarding this problem; output follows:

tm@tm-Satellite-Pro-L300D:~$ firefox --profile .mozilla/f05l3vta.default
tm@tm-Satellite-Pro-L300D:~$ firefox --profile .mozilla/firefox/f05l3vta.default[ConvertMgr] !!! constructor: [Exception... "Component returned failure code: 0x80570015 (NS_ERROR_XPC_CI_RETURNED_FAILURE) [nsIJSCID.createInstance]" nsresult: "0x80570015 (NS_ERROR_XPC_CI_RETURNED_FAILURE)" location: "JS frame :: resource://dwhelper/conversion-manager.jsm :: <TOP_LEVEL> :: line 1004" data: no]

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Description: Ubuntu 12.04 LTS
Release: 12.04
Firefox V 12.0
DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-24-generic-pae 3.2.0-24.37
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
  Uname: Linux 3.2.0-24-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0: tm 1853 F.... pulseaudio
   /dev/snd/controlC1: tm 1853 F.... pulseaudio
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xce400000 irq 16'
     Mixer name : 'Realtek ALC268'
     Components : 'HDA:11c11040,11790001,00100200 HDA:10ec0268,1179ff68,00100003'
     Controls : 16
     Simple ctrls : 9
  Card1.Amixer.info:
   Card hw:1 'Device'/'USB VoIP Device at usb-0000:00:13.5-1.4.3, full speed'
     Mixer name : 'USB Mixer'
     Components : 'USB05e1:2010'
     Controls : 4
     Simple ctrls : 2
  Date: Wed May 9 22:44:37 2012
  HibernationDevice: RESUME=UUID=1af056aa-3617-4a31-9712-78ddb1d4c21e
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
  MachineType: TOSHIBA Satellite Pro L300D
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic-pae root=UUID=6d4cc680-4f99-49aa-af35-6316cbf98c33 ro quiet splash acpi_osi= vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic-pae N/A
   linux-backports-modules-3.2.0-24-generic-pae N/A
   linux-firmware 1.79
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2008
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.vendor: ATI Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: dmi:bvnInsydeCorp.:bvr1.40:bd03/16/2008:svnTOSHIBA:pnSatelliteProL300D:pvrPSLC1U-00C002:rvnATICorp.:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Satellite Pro L300D
  dmi.product.version: PSLC1U-00C002
  dmi.sys.vendor: TOSHIBA

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Thomas Majewski (thomasjmajewski)]

This problem was eliminated when Firefox was upgraded to version 13 and has not recurred. Given the tiny impact to the community I think it should be closed.

[Paul White (paulw2u)]

Closing as fixed with next release as per reporter's comment in #2.