Эта тема была архивирована. Если вам нужна помощь, задайте новый вопрос.
After update to 49.0, firefox won't start.
My browser re-started itself, to upgrade to version 49.0 (version 48 was very unstable and crashed a lot indeed). But unlike previous updates, this one won't start (although update.status says 'succeeded'). I am getting an error message: Gtk-Message: Failed to load module "pk-gtk-module" firefox: symbol lookup error: firefox/libxul.so: undefined symbol: gtk_widget_path_append_for_widget
Все ответы (4)
Two questions to eliminate some of the issues we are seeing today:
- Do you have Norton Antivirus installed?
- Are crash reports being generated in this folder:
- On the keyboard, press [Windows] + [R]. This should bring up a Run window that contains a text field.
- In that text field, type %APPDATA% and press Enter. An explorer window should open.
- From that explorer window, double-click on the Mozilla folder, then double-click on Firefox and then on Crash reports. Double-click on submitted.
- Now, you should see a list of files that contain reports. Go to View > Arrange Icons by > Modified to get the most recent files at the top of the window.
- Open the most recent 5 files with a text editor and copy the IDs.
- Paste each ID with bp- into the reply window on the forums.
Thanks in advance!
You can find more information and troubleshooting steps in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.
I apologize, I should have mentioned that I'm running firefox on Linux Fedora 15. I found the 'Crash reports' directory in my home-directory/.mozzila and three files were generated after the update. The names of the files are 261bd8a8-0c26-6cbd-4268b996-1105c2fa-browser.dmp 261bd8a8-0c26-6cbd-4268b996-1105c2fa.dmp 261bd8a8-0c26-6cbd-4268b996-1105c2fa.extra
The first two files are binaries and the third file is text.
What information should I provide to help figure out why firefox won't start?
That would do it, unfortunately we have to submit the crash reports in order to detect if its a crash signature of a bug that might be already filed. However I do not know how to do that in linux. We can try to do this manually.
I do also know, however that there is a start up issue if you have Websense installed, just to clarify you do not have an antivirus installed?
I don't have Websense installed. I downgraded to version 47 (version 48 was very unstable), and its working. So I'll stick to it,