From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Description of problem:
While connecting to session manager: Could not open network socket.
I get this error running gnome or kde apps in X. If I restart X, it
goes away for a while, then it returns. When it returns, programs
start far slower, and some do not start at all.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.Wait or run gnome/kde apps a few times.
My assumption is that your hostname is changing via DHCP while
your X server is running. That will prevent applications from
starting, and is a hard limitation in the way X authorization
works. If you use DHCP to obtain IP address and your X server
is using your IP address for authentication purposes, you'll have
to restart the X server in order to run X apps.
Since no other reports of this nature have been reported to us
in bugzilla, and I'm unable to reproduce this in Fedora Core 2
or 3, my assumption is that this is the DHCP related limitation
of X mentioned above, or some other local configuration or
If the problem persists, please upgrade to Fedora Core 3 to
see if that changes anything. You may also seek troubleshooting
and configuration assistance on the Red Hat public mailing
lists, which may help narrow down the source of your problem.
If the problem does persist, once you've narrowed it down to
a specific cause, should that turn out to be an X bug, please
file a new bug report detailing the problem.
Setting status to "WORKSFORME", unable to reproduce.