Firefox dependency broken?

BlueJayofEvil · #1 2nd September 2010, 07:12 AM

I just did a fresh install of Rawhide (from the 14 alpha KDE version) and noticed Firefox can't install. Here's my output:

Code:

# yum install firefox
Loaded plugins: langpacks, presto, refresh-packagekit
Adding en_US to language list
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package firefox.x86_64 0:3.6.4-2.fc14 set to be installed
--> Processing Dependency: xulrunner >= 1.9.2.4-1 for package: firefox-3.6.4-2.fc14.x86_64
--> Processing Dependency: system-bookmarks for package: firefox-3.6.4-2.fc14.x86_64
--> Processing Dependency: libxul.so()(64bit) for package: firefox-3.6.4-2.fc14.x86_64
--> Running transaction check
---> Package fedora-bookmarks.noarch 0:13-1 set to be installed
---> Package xulrunner.x86_64 0:1.9.3.0-0.1b4.fc15 set to be installed
--> Processing Conflict: firefox-3.6.4-2.fc14.x86_64 conflicts xulrunner >= 1.9.2.5
--> Finished Dependency Resolution
Error: firefox conflicts with xulrunner
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

I tried the --skip-broken option but to no avail. Is anyone else having this issue?

smr54 · #2 2nd September 2010, 11:55 AM

If I remember correctly, I dealt with this by doing

rpm -e --nodeps xulrunner

then installing firefox.

I don't use Gnome, and I do a lot of work in console, that is, without X running. I don't know what non-mozilla apps require gecko, so not sure what would happen, if anything, if you do that in X while running Gnome. (It's quite possible nothing would happen, but xulrunner is the gecko runtime environment, so always best to do something like that while X isn't running.)

andrewthomas · #3 2nd September 2010, 05:18 PM

The problem is that xulrunner<1.9.2.8 provides libmozjs.so()(64bit) which is required by gnome-shell and gjs, however xulrunner-1.9.3.0 does not provide libmozjs.so()(64bit). Basically if you upgrade xulrunner in order to update firefox javascript probably won't work.

EDIT: firefox will update if you download xulrunner-1.9.2.7-2 from koji and do a yum update /path/to/xulrunner....rpm --nogpgcheck

BlueJayofEvil · #4 2nd September 2010, 07:57 PM

Quote:

Originally Posted by andrewthomas

The problem is that xulrunner<1.9.2.8 provides libmozjs.so()(64bit) which is required by gnome-shell and gjs, however xulrunner-1.9.3.0 does not provide libmozjs.so()(64bit). Basically if you upgrade xulrunner in order to update firefox javascript probably won't work.

EDIT: firefox will update if you download xulrunner-1.9.2.7-2 from koji and do a yum update /path/to/xulrunner....rpm --nogpgcheck

Thank you. That solved my issue.

R3353 · #5 3rd September 2010, 12:15 AM

seems like a lot of work to run firefox in safe-mode....

BlueJayofEvil · #6 6th September 2010, 07:09 PM

Just a small update tip for anyone else having this issue:
If you've installed xulrunner-1.9.2.7-2 from koji, yum will try to update it and it will always fail with dependency issues. Until firefox/xulrunner are updated in Rawhide, you will need to type --exclude=xulrunner when using yum.

EDIT: You can also put exclude=*xulrunner* in /etc/yum.conf

jvillain · #7 6th September 2010, 08:39 PM

My solution was to remove firefox and xulrunner then pull down a nightly development tar ball from mozilla and run that from the command line. Enjoy the goodness of firefox 4 now. Raw Hide is way to conservative.

RahulSundaram · #8 6th September 2010, 10:07 PM

Hi,

If you want Firefox 4 in a repo, refer to http://fedoraproject.org/wiki/Firefox_4

jvillain · #9 7th September 2010, 09:18 PM

Thanks for the link but that really isn't useful for people running rawhide as there is no 15 repository. You can hack the file to point to the repository by doing some thing like this

baseurl=http://repos.fedorapeople.org/repos/spot/firefox4/fedora-14/x86_64

or you can just go get the packages directly here

http://repos.fedorapeople.org/repos/...ox4/fedora-14/

But the dependency issues start getting ugly pretty fast. We need to wait for raw hide to catch up to F13.

RahulSundaram · #10 7th September 2010, 10:13 PM

Hi,

Rawhide is NOT Fedora 15. Rawhide is a permanent development branch. Fedora 15 will be a separate branch in the future. You did find it useful and it is in fact useful since I am running Rawhide with that repo. Rawhide is getting Firefox 4 independently anyway. I have no idea what rawhide catching up to Fedora 13 means. Rawhide has much newer packages.

andrewthomas · #11 8th September 2010, 03:31 PM

Information for build firefox-4.0-0.2b4.fc15

http://koji.fedoraproject.org/koji/b...buildID=194085

---------- Post added 2010-09-08 at 09:31 AM CDT ---------- Previous post was 2010-09-07 at 10:22 PM CDT ----------

After installing build firefox-4.0-0.2b4.fc15 you may have to do

Code:

# setsebool -P allow_execmem 1

to prevent
https://bugzilla.redhat.com/show_bug.cgi?id=597858

R3353 · #12 9th September 2010, 12:37 AM

I've seen you post this suggestion a few times. However, I have details in my notes where sealert has advised against running the command, both in reference to firefox and other apps. Did you ignore similar warnings? If so, how do you justify this?

RahulSundaram · #13 9th September 2010, 03:38 AM

Hi,

Red Hat developers are working with Firefox upstream to remove the need for the boolean to be set. It is a fairly large change and taking time. Meanwhile this is a temporary workaround to get things running.

R3353 · #14 9th September 2010, 04:20 AM

Quote:

Originally Posted by RahulSundaram

Hi,

Red Hat developers are working with Firefox upstream to remove the need for the boolean to be set. It is a fairly large change and taking time. Meanwhile this is a temporary workaround to get things running.

Thanks for keeping us informed, amidst all the other work you guys do. Much appreciated.

andrewthomas · #15 9th September 2010, 03:10 PM

Quote:

Originally Posted by R3353

I've seen you post this suggestion a few times. However, I have details in my notes where sealert has advised against running the command, both in reference to firefox and other apps. Did you ignore similar warnings? If so, how do you justify this?

Do you read the changelogs?

Code:

* Tue Aug 03 2010 Dan Walsh <dwalsh@redhat.com> 3.8.8-9
- Apply Miroslav munin patch
- Turn back on allow_execmem and allow_execmod booleans

Code:

Daniel Walsh      2010-08-10 08:00:49 EDT	Comment 46
This will not fix the problem on an update, only on a fresh install.

You can fix it on an existing machine by executing

# setsebool -P allow_execmem 1

https://bugzilla.redhat.com/show_bug.cgi?id=597858#c46