Bug 185243 - [patch] mozilla support does not work on x86_64
Summary: [patch] mozilla support does not work on x86_64
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: liferea
Version: rawhide
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-12 19:05 UTC by Scott Tsai
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-03-15 15:21:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
find lib64 mozilla/chrome/comm.jar (424 bytes, patch)
2006-03-12 19:05 UTC, Scott Tsai
no flags Details | Diff

Description Scott Tsai 2006-03-12 19:05:40 UTC
Description of problem:
The /usr/bin/liferea start up script contains a bug that prevents mozilla
support from working on platforms that install it under /usr/lib64.

Version-Release number of selected component (if applicable):
liferea-1.0.7-2.fc5

How reproducible:
always

Steps to Reproduce:
1.install mozilla and liferea
2.start liferea
  
Actual results:
Neither Mozilla nor Firefox is available...

Expected results:
Should not print the unavailable message

Additional info:
The /usr/bin/liferea script wants the path to $MOZILLA_HOME/chrome/comm.jar 
not the $MOZILLA_HOME path.
The one line patch below makes it work, also attached:
--- liferea.orig        2006-03-13 03:01:42.000000000 +0800
+++ liferea     2006-03-13 03:02:21.000000000 +0800
@@ -38,7 +38,7 @@
        run_with_mozilla $MOZILLA_FIVE_HOME
 fi

-look_for_mozilla "/usr/lib64/mozilla-1.7.12"
+look_for_mozilla "/usr/lib64/mozilla*/chrome/comm.jar

Comment 1 Scott Tsai 2006-03-12 19:05:40 UTC
Created attachment 126010 [details]
find lib64 mozilla/chrome/comm.jar

Comment 2 Brian Pepple 2006-03-15 15:21:27 UTC
This should be fixed in liferea-1.0.7-3 that should be pushed out in Rawhide
later today.


Note You need to log in before you can comment on or make changes to this bug.