Firefox crashes when typing in Unity HUD
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
firefox (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Steps to reproduce:
1. Open firefox
2. Press [alt] to open HUD
3. Type something into the HUD textbox
4. Firefox crashes
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: firefox 14.0.1+
ProcVersionSign
Uname: Linux 3.2.0-29-generic x86_64
AddonCompatChec
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
BuildID: 20120713224749
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xfe420000 irq 50'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:10ec0662,
Controls : 30
Simple ctrls : 13
Channel: Unavailable
CurrentDmesg:
Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
dmesg: write failed: Broken pipe
Date: Mon Aug 27 10:03:39 2012
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
IpRoute:
default via 192.168.0.254 dev eth0 proto static
169.254.0.0/16 dev eth0 scope link metric 1000
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.138 metric 1
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
MostRecentCrashID: bp-5658de4d-
PrefSources:
prefs.js
[Profile]/<email address hidden>
ProcEnviron:
LANGUAGE=en_AU:en
PATH=(custom, no user)
LANG=en_AU.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=
RelatedPackageV
rhythmbox-mozilla 2.96-0ubuntu4.1
djview-plugin 4.9-1
totem-mozilla 3.0.1-0ubuntu21
RfKill:
RunningIncompat
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
dmi.bios.date: 07/01/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: J01 v02.09
dmi.board.
dmi.board.name: 1495
dmi.board.vendor: Hewlett-Packard
dmi.chassis.
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Compaq 8200 Elite SFF PC
dmi.sys.vendor: Hewlett-Packard
Tomas Cassidy, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo apt-get -y install firefox-dbg && sudo service apport start force_start=1
If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.
Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. _my_crash_ report. crash' where _my_crash_ report. crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/ _my_crash_ report. crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https:/ /bugs.launchpad .net/ubuntu/ +source/ apport/ +bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line: crashdb. conf
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/
gksudo gedit /etc/apport/
and comment out the line:
'problem_types': ['Bug', 'Package'],
by changing it to:
# 'problem_types': ['Bug', 'Package'],
Save, close, and try to file the crash report again via: _my_crash_ report. crash
ubuntu-bug /var/crash/
Please follow https:/ /wiki.ubuntu. com/MozillaTeam /Bugs when you file this crash report so the necessary information is provided.
I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.
Thank you for your understanding.
Helpful bug reporting tips: /wiki.ubuntu. com/ReportingBu gs
https:/