Red Hat Bugzilla – Bug 110280
rhn-applet blocks logging out in GNOME for 1 minute
Last modified: 2007-11-30 17:10:33 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5)
Description of problem:
I have a lapto with Fedora core 1, which I use with a direct
connection to the Internet (at home) or with a proxy (at work). I have
rhn-applet configured without a proxy. With a direct connection at
home everything is working fine.
However if I use my laptop at work and then want to log out of GNOME,
the logging out hangs for about 1 minute. I guess some time out in
rhn-applet is causing this, because when I first stop rhn-applet
manually logging out goes fast. When the logging out is hanging I saw
in another terminal that rhn-applet was still running and when I
killed it my Gnome Session immediately logged out.
NOTE with this behaviour behind a proxy I still have the applet
configured with a direct connection to the internet. I works fine if I
select the appropriate proxy. However I'm to lazy to change this (and
also forget this ) every time.
A suggestion which would make life more easy for me would be to use an
automatic configuration script. I do this with mozilla. When mozilla
does not find this script it just assumes it has a direct connection.
That way it automagically works at home and at work.
Furthermore isn't there a way such that applications can get the proxy
settings from the Network Proxy settings in the Gnome Preferences
menu. (I guess KDE has something similar). This would save a lot of
setting proxies in different programs.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Choose no proxy in rhn_applet
2. Connect your PC to a network with a proxy
3. Start up gnome
4. Log out of gnome
Actual Results: It hangs for about a minute
Expected Results: Immediate logout
Can you upgrade to the latest rhn-applet and see if that stil occurs?
You can get it here:
Also, check your proxy settings. There seems to be issues with
rhn-applet an proxy servers. See bug 107315 and bug 114085.
If it works after the upgrade let us know.
Still exactly the same behaviour