I get the same.  It worked again after I deleted the Galeon-configs
with galeon-config-tool --clean.

I looked at it once again. my solution is: 1. remove all lines
containing 'proxy' from .galeon/mozilla/galeon/prefs.js 2. remove file
.gconf/apps/galeon/Advanced/Network/%gconf.xml 3. start galeon and
setup proxy once again in preferences.

Same for me.  I managed to set the proxy parameters and Galeon used
them for a while, but after a crash (which was because some other
reason) it simply ignored them.  Switching them off and on, restarting
etc did not help.  Based on a hint in bug #80345, I removed the
~/.galeon/mozilla/galeon/prefs.js file (while Galeon not running) and
Galeon started to respect proxy settings again.

By the way, storing settings twice (in gconf and in prefs.js) sucks,
as there will be inconsistencies.

*** Bug 93085 has been marked as a duplicate of this bug. ***

*** Bug 92611 has been marked as a duplicate of this bug. ***

*** Bug 80345 has been marked as a duplicate of this bug. ***

Clearly there is some problem with the proxy settings and the
appropriate time to set them see also bug 78940

I have applied a fix to cvs which should solve this problem. I need
confirmation that it is indeed fixed.

*** Bug 101391 has been marked as a duplicate of this bug. ***

I am using trunk, and the proxy also do not work.

-York

This works for me in galeon 1.3.8, if you can reproduce with this
version, then please re-open, or file a new bug detailing the steps to
reproduce.