Bugzilla – Bug 990376
Firefox no longer starts after latest update
Last modified: 2016-07-24 18:04:39 UTC
after install of updates on 2016Jun26 MozillaFirefox-47.0-1.2.i586 no longer starts NB1: no problems found with update on 64bit os NB2: also no problems found with Konqueror attempting to start from a terminal gives, [code]tosh-sm60<2016Jun26@22:18><~/Updates/13.3/packets/2016-06>... firefox (firefox:5554): Gtk-WARNING **: Theme directory actions/48 of theme breeze has no size field (firefox:5554): Gtk-WARNING **: Theme directory categories/16 of theme breeze has no size field (firefox:5554): Gtk-WARNING **: Theme directory categories/22 of theme breeze has no size field (firefox:5554): Gtk-WARNING **: Theme directory categories/48 of theme breeze has no size field (firefox:5554): Gtk-WARNING **: Theme directory devices/48 of theme breeze has no size field (firefox:5554): Gtk-WARNING **: Theme directory of theme oxygen has no size field ExceptionHandler::GenerateDump cloned child 5598 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... tosh-sm60<2016Jun26@22:32><~/Updates/13.3/packets/2016-06>... [/code] downloaded firefox-47.0.tar.bz2 from the mozilla web site and it runs without problems from /home, all bookmarks and settings retained from yast installed version situation still the same after latest update, os [code]So 24. Jul 16:17:48 CEST 2016 Kernel: 4.6.3-1-default i686 (32 bit) Desktop: KDE Plasma 5.7.0 Distro: openSUSE Tumbleweed (20160720) TOSHIBA (portable) product: Satellite M60 v: PSM60E-0C801GGR Mobo: TOSHIBA model: EBQ10 v: Null Bios: TOSHIBA v: V1.60 date: 03/16/2006 Single core Intel Pentium M (-UP-) cache: 2048 KB speed: 1867 MHz (max) Advanced Micro Devices [AMD/ATI] RV410/M26 [Mobility Radeon X700] Display Server: X.Org 1.18.3 drivers: ati,radeon (unloaded: fbdev,vesa) Resolution: 1680x1050@60.11hz GLX Renderer: Gallium 0.4 on ATI RV410 GLX Version: 2.1 Mesa 12.0.1 Direct Rendering: Yes[/code]
Duplicate of 986541 *** This bug has been marked as a duplicate of bug 986541 ***