From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.11) Gecko/20050815 Fedora/1.7.11-2 Description of problem: After today's updates, firefox fails to start for me. I'm running latest rawhide, targetted/enforcing, but this fails in both enforcing and permissive modes (and no messages in audit.log or messages). I also tried getting rid of my .mozilla directory to no avail. I installed the 'new' cairo package (so I have both cairo-0.6.0-2 and cairo-0.9.2-2 installed). Mozilla runs fine. output of 'strace /usr/bin/firefox' attached..... Version-Release number of selected component (if applicable): firefox-1.1-0.2.6.deerpark.alpha2 How reproducible: Always Steps to Reproduce: 1. Try to start firefox 2. 3. Additional info:
Created attachment 117853 [details] output of 'strace /usr/bin/firefox'
I can confirm the problem. Executing LD_LIBRARY_PATH=/usr/lib/firefox-1.1 ./firefox-bin results in the following error: ./firefox-bin: symbol lookup error: /usr/lib/firefox-1.1/components/libgfx_gtk.so: undefined symbol: pango_xft_get_font_map
Yes. I fixed this for 1.0.6 on rawhide using the latest cairo/pango. Some reason this particular so is not linking with libpangoxft. Something with pkgconfig. I added to one of /usr/lib/gdk-2.0.pc or /usr/lib/gdk-x11-2.0.pc the Requirement for pangoxft and recompiled. Something needs to be fixed in these dependencies.
Able to reproduce this.changing status to assigned
Same problem. I downloaded /pub/mozilla.org/firefox/releases/deerpark/alpha2/linux-i686/en-US/deerpark-alpha2.tar.gz which does work
Confirmed on my x86_64 box too. [sal@localhost ~]$ /usr/lib64/firefox-1.1/firefox-bin /usr/lib64/firefox-1.1/firefox-bin: error while loading shared libraries: libmozjs.so: cannot open shared object file: No such file or directory [sal@localhost ~]$ locate libmozjs /usr/local/firefox/libmozjs.so /usr/lib64/firefox-1.1/libmozjs.so
Confirmed on my x86 box. Starting firefox with this commandline works for me: LD_LIBRARY_PATH=/usr/lib/firefox-1.1 MOZ_DISABLE_PANGO=1 firefox
Fixed for me with today's update (0.2.7). Txs
The latest update fixed this for me too. Thanks!
Thanks for the bug report. This particular bug was fixed and a update package was published for download. Please feel free to report any further bugs you find.