Red Hat Bugzilla – Bug 173117
Gnome panel hangs for a few minutes when trying to logout
Last modified: 2012-06-20 09:26:02 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050923 CentOS/1.0.7-1.4.1.centos4 Firefox/1.0.7 Description of problem: When issuing Actions->Log out, the gnome-panel freezes for a few minutes. This is before showing any confirmation dialog. The setup is the following: - Windows 2000 PC running cygwin 'XWin -indirect linuxhost' - RHEL4 Linux machine running default gnome desktop - Sound Server is disabled in gnome After researching the problem, it appears that the panel hangs because it is trying to contact the gnome sound server (esd) on the Windows 2000 host, even although the sound server in the gnome prefs is disabled. Since the windows 2000 host is running with Windows Firewall enabled, the esd connection is dropped (not rejected) causing the esound library to wait for a timeout. Solution: - starting 'esd -tcp -public' on the windows 2000 host and allowing incoming connections to esd.exe in the Windows Firewall, resolves the long hang at logout. So it appears that gnome-panel doesn't strictly follow the 'Sound Server' settings of the session. Version-Release number of selected component (if applicable): gnome-panel-2.8.1-3.3E How reproducible: Always Steps to Reproduce: Login from a remote X11 server using XDMCP and block (drop, not reject) incoming connections to the esd daemon port (16001). Additional info:
Correction: The XWin commandline should read: XWin -query linuxhost Possible the Fedora Core 3 Bug #151076 is related.
I have the same problem on my RHEL 3 and 4 machines. My solution had been to rebuild gdm with the XDMCP patch removed. Unfortunately, this no longer works in RHEL 4 update 3.
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. Please See https://access.redhat.com/support/policy/updates/errata/ If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.