Description of problem: Installing mozilla-1.0.2-2.7.1 rpm's causes galeon to fail with message: Cannot find mozilla installation directory. Please set MOZILLA_FIVE_HOME to your mozilla directory Version-Release number of selected component (if applicable): 1.0.2-2.7.1 How reproducible: every time Steps to Reproduce: 1. Install mozilla-1.0.2-2.7.1 rpm's 2. galeon 3. Actual results: Cannot find mozilla installation directory. Please set MOZILLA_FIVE_HOME to your mozilla directory Expected results: galeon runs Additional info:
I have rh 8, and just uploaded the new fixed moz rpms (mozilla-1.0.2-1.8.0 etc) using up2date. I have galeon-1.2.6-0.8.0. I have same problem, but I'm also getting crashes. When I go to http://linuxtoday.com/ today, mozilla starts to connect and then disappears. EVERY time. Ryan
I don't have the crashing problem with linuxtoday.com, so these effects may have different causes.
I am using RH 7.3 and Galeon would not start as the bug reporter described. My workaround was to remove the /usr/lib/mozilla directory and create a symbolic link at /usr/lib/mozilla to /usr/lib/mozilla-1.0.2. Galeon displayed a warning when run, but this seemed to work well and I have not found crashes so far (and I am now in Galeon). I think a better way is to release a new Galeon version compatible with Mozilla 1.0.2.
I tried both the symbolic link work-around (/usr/lib/mozilla -> /usr/lib/mozilla-1.0.2) and setting MOZILLA_FIVE_HOME to /usr/lib/mozilla-1.0.2. Both resulted in the error: /usr/bin/galeon-bin: relocation error: /usr/bin/galeon-bin: undefined symbol: begin_assignment__13nsCOMPtr_base System - RedHat 8 Galeon - 1.2.6
See also bug #99460 which is somewhat related.
Installing mozilla*-1.0.2-2.8.0 and galeon-1.2.11-1.8.0 fixes this for me. I suggest closing this bug.
Yes, this should be fixed now.