firefox crashes while visiting facebook
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
firefox (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I am using firefox 12.0 for ubuntu.
ubuntu 12.04 is installed.
while I`m trying to post a photo on facebook firefox crashes.
on my pc is a 64 bit version of ubuntu 12.04 installed.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: firefox 12.0+build1-
ProcVersionSign
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelMo
AddonCompatChec
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
BuildID: 20120423122928
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
Card0.Amixer.info:
Card hw:0 'IXP'/'ATI IXP rev 2 with ALC658D at 0xfe02a000, irq 17'
Mixer name : 'Realtek ALC658D'
Components : 'AC97a:414c4781'
Controls : 38
Simple ctrls : 24
Card1.Amixer.info:
Card hw:1 'Audio'/'USB Audio at usb-0000:
Mixer name : 'USB Mixer'
Components : 'USB0c45:16be'
Controls : 13
Simple ctrls : 6
Channel: release
Date: Sun May 6 15:40:47 2012
ForcedLayersAccel: False
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
IpRoute:
default via 192.168.1.1 dev eth0 proto static
169.254.0.0/16 dev eth0 scope link metric 1000
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.100 metric 1
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
Plugins:
iTunes Application Detector - Lib=librhythmbo
VLC Multimedia Plugin (compatible Totem 3.0.1) - Lib=libtotem-
DivX® Web Player - Lib=libtotem-
QuickTime Plug-in 7.6.6 - Lib=libtotem-
Windows Media Player Plug-in 10 (compatible; Totem) - Lib=libtotem-
ProcEnviron:
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=
RfKill:
RunningIncompat
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/17/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 3.33
dmi.board.name: AMETHYST-M
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: EG686AA-ABD t3181.de
dmi.product.
dmi.sys.vendor: HP Pavilion 061
Oliver Dicklhuber, 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 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/
sudo nano /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/
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.
Please do not attach your crash report manually to this report and reopen it.
Thank you for your understanding.
Helpful bug reporting tips: /wiki.ubuntu. com/ReportingBu gs
https:/