Hey all!

I did a search on the forum but could not find any other post about this problem.

When i try to start Galeon on any other user I have added to my system except root i get the following error message:

-----------------------------------------------------------------------------------------------
Galeon failed to start.
Ensure the "MOZILLA_FIVE_HOME" enviroment variable is set to the
correct Mozilla installation directory.
-----------------------------------------------------------------------------------------------

So then I tried to see if Mozilla would work but it wont even start and I do not get any error messages at all.

They both work when login in with root but no on my other accounts.
I have reinstalled 2 times just to check if that would solve the problem but to no avail. The same error occurs every time.



./eonix

Have you got write permissions in $HOME?

Check where mozilla is installed (/usr/lib/mozilla? ..?) and set MOZILLA_FIVE_HOME

Well this sadly is a known problem in Slack 10, the easier (and for most of us, better) way to solve it is to use FireFox.

Does anyone know the root cause though? I am using mozilla and galeon fine on a fresh install of Slack 10. Might it be some option chosen at install time?

if it is a slackware 10.0 bug, that is just about the stupidest thing i've seen recently.

i'm having the same problem, though. here's my question: did you log into a graphical environment as root and use mozilla? that's what i did. when i log in as root, mozilla still works. it is just any other, non-root user that experiences this problem.

it has to be something to do with permissions. anyone have an idea?

The solution is here:
http://www.linuxquestions.org/questi...zilla+perm+600

the only possible suggestion i saw in that thread was the chown command, and that didn't work for me. anyone else have a suggestion?

What is your output for :
(replace 1.7 by your mozilla version)

find /usr/lib/mozilla-1.7 -perm 600 -print
find /usr/lib/mozilla-1.7 -perm 700 -print

I've got the same symptoms.

So that keefaz can have the answer to the last question,... As I was unsure how you wanted the info, I generated the output as both root and a regular user.

bash-2.05b# find /usr/lib/mozilla-1.7 -perm 600
/usr/lib/mozilla-1.7/components/xpti.dat
/usr/lib/mozilla-1.7/components/compreg.dat
/usr/lib/mozilla-1.7/chrome/chrome.rdf
/usr/lib/mozilla-1.7/chrome/overlayinfo/communicator/content/overlays.rdf
/usr/lib/mozilla-1.7/chrome/overlayinfo/navigator/content/overlays.rdf
/usr/lib/mozilla-1.7/chrome/overlayinfo/cookie/content/overlays.rdf
/usr/lib/mozilla-1.7/chrome/overlayinfo/editor/content/overlays.rdf
/usr/lib/mozilla-1.7/chrome/overlayinfo/global/skin/stylesheets.rdf
/usr/lib/mozilla-1.7/chrome/overlayinfo/messenger/content/overlays.rdf
/usr/lib/mozilla-1.7/chrome/overlayinfo/inspector/content/overlays.rdf
/usr/lib/mozilla-1.7/chrome/overlayinfo/browser/skin/stylesheets.rdf
/usr/lib/mozilla-1.7/chrome/overlayinfo/browser/content/overlays.rdf

bash-2.05b$ find /usr/lib/mozilla-1.7 -perm 600
/usr/lib/mozilla-1.7/components/xpti.dat
/usr/lib/mozilla-1.7/components/compreg.dat
/usr/lib/mozilla-1.7/chrome/chrome.rdf
find: /usr/lib/mozilla-1.7/chrome/overlayinfo: Permission denied

bash-2.05b# find /usr/lib/mozilla-1.7 -perm 700
/usr/lib/mozilla-1.7/chrome/overlayinfo
/usr/lib/mozilla-1.7/chrome/overlayinfo/communicator
/usr/lib/mozilla-1.7/chrome/overlayinfo/communicator/content
/usr/lib/mozilla-1.7/chrome/overlayinfo/navigator
/usr/lib/mozilla-1.7/chrome/overlayinfo/navigator/content
/usr/lib/mozilla-1.7/chrome/overlayinfo/cookie
/usr/lib/mozilla-1.7/chrome/overlayinfo/cookie/content
/usr/lib/mozilla-1.7/chrome/overlayinfo/editor
/usr/lib/mozilla-1.7/chrome/overlayinfo/editor/content
/usr/lib/mozilla-1.7/chrome/overlayinfo/global
/usr/lib/mozilla-1.7/chrome/overlayinfo/global/skin
/usr/lib/mozilla-1.7/chrome/overlayinfo/messenger
/usr/lib/mozilla-1.7/chrome/overlayinfo/messenger/content
/usr/lib/mozilla-1.7/chrome/overlayinfo/inspector
/usr/lib/mozilla-1.7/chrome/overlayinfo/inspector/content
/usr/lib/mozilla-1.7/chrome/overlayinfo/browser
/usr/lib/mozilla-1.7/chrome/overlayinfo/browser/skin
/usr/lib/mozilla-1.7/chrome/overlayinfo/browser/content


bash-2.05b$ find /usr/lib/mozilla-1.7 -perm 700
/usr/lib/mozilla-1.7/chrome/overlayinfo
find: /usr/lib/mozilla-1.7/chrome/overlayinfo: Permission denied


I get the feeling I'm missing something obvious...

(the following is a copy/paste from another thread)

After trying so many things I pretty much screwed up Mozilla beyond recognition. So I completely uninstalled it, then reinstalled it from the Slackware installation disk #1. I read instructions on the Mozilla website for installing it on Linux. One thing they said was to do everything from root, not su(do) root. They also said to run Mozilla from root first before running it as a user.
Reading another thread in this forum on this problem, I learned that the /usr/lib/mozilla-1.7/chrome directory has to be changed to "chmod 777". I tried that but it still didn't work.

So I looked at the properties of that directory. In KDE (as root- dangerous, I know) I right-clicked on the /chrome directory, then clicked Properties, Permissions. Everybody, i.e. Owner, Group, and Others had full permissions. But it said Owner was root and Group was root. I changed the Group to "users". Ran Mozilla and Galeon once each as root. Logged out and logged in as a user. They both work now. I do not get a screen to create a new profile.

This isn't a great solution from a security standpoint, but nobody besides myself using this computer will ever mess with the files.

HTH,

Siri Amrit

I had already read that post, and did not think that this was the correct way to solve the problem, as the author suggests toward the end and I'm inclined to agree.

Am I wrong to assume this?.

I had the same problem as described above. I tried it and it worked for me.

For me the problem was caused by installing mozilla-js-debugger. After removing it, the problem was solved.

rpm -e mozilla-js-debugger

The symptoms were the following: galeon shows the error dialog mentioned above, mozilla fails silently, epiphany is unable to access a .htpasswd protected site.