After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 92611 - setup with proxy fails behind firewall when no external dns resolving available
setup with proxy fails behind firewall when no external dns resolving available
Status: RESOLVED DUPLICATE of bug 85392
Product: galeon
Classification: Deprecated
Component: general
1.2.5
Other Linux
: High normal
: ---
Assigned To: galeon-maint
Yanko Kaneti
Depends on:
Blocks:
 
 
Reported: 2002-09-05 22:25 UTC by Olaf Schulz
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Olaf Schulz 2002-09-05 22:25:25 UTC 
in an environment where the DNS only resolves internal names
and all other DNS resolving is done by the outermost of a chain of
proxy servers
- galeon blocks (timeout) when trying to access external web sites via proxy
- mozilla with the same proxy configuration does not time out on the
  same web sites.
As other browsers (like Konquerror, Netscape 4, MSIE) can cope with this
situation galeon should as well.
Comment 1 Yanko Kaneti 2002-09-05 22:38:37 UTC 
I find it hard to believe the problem is with galeon and not mozilla.

Galeon itself has zero resolve/network related code.

Please compare the running configurations of mozilla and galeon more
closely. you might be observing  symptoms of bug 85392, or who knows
what else...
Comment 2 Olaf Schulz 2002-09-06 09:58:48 UTC 
erased config with galeon-config-tool --clean
and reproduced the bug:
set up proxies as necessary, then
galeon then tries to load 
http://www.gnome.org/ or http://galeon.gnome.org/

and times out with "www.gnome.org could not be found, pls. check name..."

I guess the reason, look at the Menu at
"settings, Proxy" and see:
flickering between "Disabled" and "Manual"!

Now I'm leaving galeon by closing its window via my window manager's control
(actually KDE)
immediately restarting will bring up http://www.gnome.org/ again
and tells me that /usr/bin/galeon-bin has crashed with segmentation fault.
nevertheless I experience the known dns resolving timeout as above.
Settings, Proxy shows "Disabled" now, so far ok for dns timeout.

after enabling proxies everything is ok, galeon remembers it's 
configuration as expected.

So we should change the bug's status to "galeon setup problem"
could you classify the correct component now, please?
(user interface? mozilla interaction?)
Comment 3 Yanko Kaneti 2002-09-12 08:42:14 UTC 

*** This bug has been marked as a duplicate of 85392 ***