Closed Bug 1224610 Opened 10 years ago Closed 10 years ago

Beta 43.x: libgtk-3.so.0: cannot open shared object file

Categories

(Firefox :: Installer, defect)

43 Branch
Unspecified
Linux
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: tkevans, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0 Build ID: 20151022152545 Steps to reproduce: Started FireFox Beta 43.x (all releases up to .3 are same). CentOS 6.7 Linux osprey 2.6.32-573.8.1.el6.x86_64 #1 SMP Tue Nov 10 18:01:38 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Actual results: XPCOMGlueLoad error for file /usr/local/firefox/libmozgtk.so: libgtk-3.so.0: cannot open shared object file: No such file or directory Couldn't load XPCOM. FireFox did not start Expected results: FireFox should start FireFox 42 has no such problem.
Hi, I have tested this on Ubuntu 14.04 and I could't reproduce this. Also you can download the Firefox Nightly from here: https://nightly.mozilla.org/ and retest the problem. Did this work OK with Firefox 42? If so, would you be willing to help try to narrow down a more-specific culprit? Given the application, it could be very difficult to track down on our end. If you're willing, we have a tool called mozregression that will automate the process of downloading various builds from during the Firefox 41 development cycle to narrow down the change that's causing problems. Information on the tool is available at http://mozilla.github.io/mozregression/. A command like |mozregression --good-release 40 --bad-release 41| should be enough to get started (assuming Fx40 was OK). Thanks!
Component: Untriaged → Installer
Flags: needinfo?(tkevans)
Keywords: regression
OS: Unspecified → Linux
Yes, this worked fine with FireFox 42. Still same error with both the latest 43 beta *and* the latest nightly.
Version: 42 Branch → 43 Branch
Hi, Thank for your time. Unfortunately I don't have CentOS 6.7 to test this, I try only on Ubuntu 14.04 and everything works ok. If you're willing, we have a tool called mozregression that will automate the process of downloading various builds from during the Firefox 42 development cycle to narrow down the change that's causing problems. Information on the tool is available at http://mozilla.github.io/mozregression/quickstart.html. A command like ex: mozregression --good=2015-11-03 --bad=2015-11-18 should be enough to get started (assuming Fx42 was OK). Also can you give us more clear steps to reproduce this? Thanks!
This is FireFox 43, not 42, as I keep saying; 42 works fine. Isn't the reference to libgtk3 key here? CentOS 6.x (and RedHat 6.x) doesn't include version 3 of gtk.
Flags: needinfo?(tkevans)
Hi, I have tested this on Firefox43.0b3 and I can't reproduce the issue. It can be a problem regarding libgtk 3 but I'm note 100% sure.
The system requirements for beta 43 [1] state that GTK+ version 3 is required. This is a change that was made for version 43; compare to the release 42 system requirements [2] and see bug 1186003. CentOS 6 provides only GTK+ version 2, so the error message you received is expected behavior. GTK+ 3 is officially supported by CentOS only in CentOS 7, so unfortunately I don't have a solution for you except to upgrade your OS. It may be possible to compile your own build of Firefox from newer code, but this may be difficult because of older versions of other packages (e.g. Python) in CentOS 6; I don't know Linux well enough to be able to help with that. [1] https://www.mozilla.org/en-US/firefox/43.0beta/system-requirements/ [2] https://www.mozilla.org/en-US/firefox/42.0/system-requirements/
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Keywords: regression
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.