abrt version: 1.1.14 architecture: i686 Attached file: backtrace cmdline: /usr/lib/firefox-4/firefox comment: I was talking to my future wife via the messenger application in my Hotmail account,I downloaded a couple of files,one was in .doc,and the other one was in .pdf format.I think the one in .pdf format crashed Firefox,when I chose to open it directly in Okular. component: firefox executable: /usr/lib/firefox-4/firefox kernel: 2.6.36-5.fc15.i686 package: firefox-4.0-0.5b7.fc15 reason: Process /usr/lib/firefox-4/firefox was killed by signal 11 (SIGSEGV) release: Fedora release 15 (Rawhide) time: 1290132978 uid: 0 How to reproduce ----- 1.Boot into latest Fedora Kernel. 2.Log into KDE 3.Launch Firefox
Created attachment 461431 [details] File: backtrace
Package: firefox-4.0-0.5b7.fc15 Architecture: i686 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1.Log into lastest Fedora Kernel 2.Log into KDE 3.Startup Firefox Comment ----- I was trying to look into my Hotmail account.The problem is I can't see my hotamil account through my linux version of Firefox. The message kept saying "the server was reset"or something like that. I can see my Hotmail account through my windows version of Firefox.
Package: firefox-4.0-0.5b7.fc15 Architecture: i686 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1.Log into my latest compiled 2.6.37-rc3 kernel. 2. 3. Comment ----- I keep getting this bug when I try to view my Hotmail account in the linux version of firefox.
Package: firefox-4.0-0.5b7.fc15 Architecture: i686 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1. Downloaded a pdf with some graphic, open it in okular. 2. Firefox crashes in the background. 3.
Package: firefox-4.0-0.5b7.fc15 Architecture: i686 OS Release: Fedora release 15 (Rawhide) How to reproduce ----- 1.Log into latest Fedora Rawhide Kernel 2.log into KDE 3.Run Firefox Comment ----- I was basically downloading the latest kernel from kernel.org.Firefox crashed when I was going to download the patch.
*** This bug has been marked as a duplicate of bug 654628 ***