Description of problem:I have two main desktop machines, both running Mageia 5 and both fully patched. On one of these upgrade to Furefox 45 broke Firefox. Originally it would crash on startup, reporting an XDR error. Removing some obsolete extensions, changed this -- the application now starts and its X window comes up, but is not usable (see the screenshot at https://forums.mageia.org/en/viewtopic.php?f=7&t=11139&p=64744#p64702) In addition to bad bar display, the URL field is completely unresponsive -- nothing can be typed into it. Removing and re-installing Firefox has no effect. The problem is cured by downgrading to Firefox 38.8.0. On the other machine the upgrade to 45 caused no problems.Please let me know what information re the two machines in question you would find useful. Version-Release number of selected component (if applicable): 45.2.0 How reproducible: 100% Steps to Reproduce: 1.Start firefox 2. 3.
Did you try to run it with add-ons disabled (the option under help menu)?
CC: (none) => mageia
(In reply to Sander Lepik from comment #1) > Did you try to run it with add-ons disabled (the option under help menu)? There was no way to access the help menu. See the snapshot I referred to.
I should have added... Firefox on both machines uses the same .mozilla directory (mounted over NFS). I tried taking a local copy of .mozilla, but this had no effect. The upshot is: the same add-ons are used in both cases.
(In reply to Mike Arnautov from comment #2) > (In reply to Sander Lepik from comment #1) > > Did you try to run it with add-ons disabled (the option under help menu)? > > There was no way to access the help menu. See the snapshot I referred to. So open up a terminal window and start firefox from there in safe mode with: firefox --safe-mode
CC: (none) => tmb
CC: (none) => doktor5000
OK... Have re-updated to 45.2.0 and used --safe-mode. Makes no difference. The resulting display is still the same as in that screenshot.
On the machine where it's broken, is Firefox there also broken for a newly created user?
CC: (none) => marja11
Good question! Given that I tried moving .local and .kde4 out of the way, I would expect the answer to be yes. In fact, for a new account Firefox 45 works just fine. Indeed, copying .mozilla, .local and .kde4 from an account where it is broken, makes no difference -- it still works fine. Another likely culprit is GTK, so I have also zapped .gtk-bookmarks, .gtkrc-2.0-kde4 on the account wehere Firefox is broken (there being nothing else clearly associated with GTK). No effect. So there is something else lurking somewhere else. Any ideas?
Ah... I've just spotted .config! (OK... go ahead, laugh! :-)) And it is .config/gtk-3.0/settings.ini that is doing the damage. Specifically, commenting out the line gtk-font-name=Liberation Sans Regular cures the problem. Why is that line there? I have no idea. But, surely, a GTK app should not become unusable just because of a font specification!
NB: On the other machines .config/gtk-3.0 exists, but settings.ini is absent.
(In reply to Mike Arnautov from comment #8) > Ah... I've just spotted .config! (OK... go ahead, laugh! :-)) And it is > .config/gtk-3.0/settings.ini that is doing the damage. Specifically, > commenting out the line > > gtk-font-name=Liberation Sans Regular > > cures the problem. Why is that line there? I have no idea. But, surely, a > GTK app should not become unusable just because of a font specification! (In reply to Mike Arnautov from comment #9) > NB: On the other machines .config/gtk-3.0 exists, but settings.ini is absent. Assigning to all packagers collectively
Assignee: bugsquad => pkg-bugsSummary: Firefox broken after upgrade to version 45 => FF broken after upgrade to v.45 when ~/ .config/gtk-3.0/settings.ini contains "gtk-font-name=Liberation Sans Regular"Source RPM: http://firefox-45.2.0-1.mga5.src.rpm => firefox-45.2.0-1.mga5, gtk+3.0
Not much we can do to preventively "fix" every possible user-added setting, and in any case this should be reported upstream at https://bugzilla.mozilla.org/ Apart from that, you're the only one who reported such a thing thus far.
Status: NEW => RESOLVEDResolution: (none) => WONTFIX