On Fri, Jul 12, 2002 at 08:52:05PM -0700, Joe Kelsey wrote:
> On Fri, 2002-07-12 at 19:15, Cyrille Lefevre wrote:
> > On Sun, Jul 07, 2002 at 11:28:29AM -0400, stan wrote:
> > > After last weekends cvsup & portupgrade I am unable to run Sawfish as the
> > > window manager fro Gnome on both machnes I track STABLE on
> > >
> > > Basicly Gnome starts up (after a _very long_ time) and there is no window
> >
> > I've this problem too. it seems to be `esd' startup which sleep for
> > a while but don't know why.
>
> In my experience, it really was Sawfish that was hanging. The problem
> (in may case) was that Swafish would hang for minutes, but would
> eventually continue.
>
> I'll bet you are running an X Font Server. I was running xfs-tt. As
no, I'm running XFree-4 which don't need xfs-tt to handle TT fonts.
just have `Load "freetype"' in the "Module" section of /etc/X11/XF86Config.
to be more precise, the problem is ...
...
62191 gnome-login-chec 1026646819.141317 CALL access(0x2848b060,0x6)
62191 gnome-login-chec 1026646819.141632 NAMI "/root/.esd/socket"
62191 gnome-login-chec 1026646819.141752 RET access -1 errno 2 No such file o
r directory
62191 gnome-login-chec 1026646819.142074 CALL socket(0x2,0x1,0)
62191 gnome-login-chec 1026646819.142184 RET socket 3
62191 gnome-login-chec 1026646819.142303 CALL fcntl(0x3,0x2,0x1)
62191 gnome-login-chec 1026646819.142353 RET fcntl 0
62191 gnome-login-chec 1026646819.142464 CALL setsockopt(0x3,0x,0x4,0xbfbf
b928,0x4)
62191 gnome-login-chec 1026646819.142520 RET setsockopt 0
62191 gnome-login-chec 1026646819.142639 CALL connect(0x3,0xbfbfb978,0x10)
* here *
62191 gnome-login-chec 1026646894.134824 RET connect -1 errno 60 Operation ti
med out
62191 gnome-login-chec 1026646894.135135 CALL close(0x3)
62191 gnome-login-chec 1026646894.135214 RET close 0
...
62208 sh 1026646894.224087 CALL execve(0x80d23ac,0x80cc720,0x80d2204)
62208 sh 1026646894.224133 NAMI "/usr/local/bin/esd"
62208 sh 1026646894.226061 NAMI "/usr/libexec/ld-elf.so.1"
62208 esd 1026646894.227562 RET execve 0
...
62208 esd 1026646894.249376 CALL write(0x2,0xbfbfb5bc,0x1b)
62208 esd 1026646894.249486 GIO fd 2 wrote 27 bytes
"- using device /dev/dsp0.1
"
...
62208 esd 1026646894.254407 CALL mkdir(0x28076c60,0x3ed)
62208 esd 1026646894.254463 NAMI "/root/.esd"
62208 esd 1026646894.254984 RET mkdir 0
62208 esd 1026646894.255090 CALL chmod(0x28076c60,0x3ed)
62208 esd 1026646894.255134 NAMI "/root/.esd"
62208 esd 1026646894.255271 RET chmod 0
62208 esd 1026646894.255356 CALL socket(0x1,0x1,0)
62208 esd 1026646894.255435 RET socket 5
62208 esd 1026646894.255501 CALL fcntl(0x5,0x2,0x1)
62208 esd 1026646894.255539 RET fcntl 0
62208 esd 1026646894.255596 CALL setsockopt(0x5,0x,0x4,0xbfbfbba4,0x4
)
62208 esd 1026646894.255646 RET setsockopt 0
62208 esd 1026646894.255894 CALL connect(0x5,0xbfbfbba8,0x13)
62208 esd 1026646894.255966 NAMI "/root/.esd/socket"
62208 esd 1026646894.256071 RET connect -1 errno 2 No such file or direc
tory
62208 esd 1026646894.256159 CALL unlink(0x28077060)
62208 esd 1026646894.256205 NAMI "/root/.esd/socket"
62208 esd 1026646894.256283 RET unlink -1 errno 2 No such file or direct
ory
62208 esd 1026646894.256324 CALL socket(0x1,0x1,0)
62208 esd 1026646894.256381 RET socket 6
62208 esd 1026646894.256419 CALL fcntl(0x6,0x4,0x4)
62208 esd 1026646894.256458 RET fcntl 0
62208 esd 1026646894.256492 CALL setsockopt(0x6,0x,0x80,0xbfbfbc40,0x
8)
62208 esd 1026646894.256530 RET setsockopt 0
62208 esd 1026646894.256563 CALL setsockopt(0x6,0x,0x4,0xbfbfbc3c,0x4
)
62208 esd 1026646894.256598 RET setsockopt 0
62208 esd 1026646894.256663 CALL umask(0)
62208 esd 1026646894.256699 RET umask 18/0x12
62208 esd 1026646894.256762 CALL bind(0x6,0xbfbfbc48,0x13)
62208 esd 1026646894.256808 NAMI "/root/.esd/socket"
62208 esd 1026646894.257049 RET bind 0
62208 esd 1026646894.257102 CALL umask(0x12)
62208 esd 1026646894.257138 RET umask 0
62208 esd 1026646894.257208 CALL listen(0x6,0x10)
62208 esd 1026646894.257258 RET listen 0
62208 esd 1026646894.257334 CALL open(0xbfbfbfc7,0x5,0)
62208 esd 1026646894.257384 NAMI "/dev/dsp0.1"
62191 gnome-login-chec 1026646894.313875 RET select 0
62191 gnome-login-chec 1026646894.313971 CALL close(0x3)
...
it looks that gnome-login-check try to connect to the esd server
which isn't started yet, then it sleep for a while (around 74 secs),
then start esd, then it is able to connect to esd.
CC -stable, -gnome
Cyrille.
--
Cyrille Lefevre mailto:[EMAIL PROTECTED]
To Unsubscribe: sen