On Tuesday 17 November 2009 23:56:00 Philip Webb wrote: > 091112 Alan McKinnon wrote: > > On Thursday 12 November 2009 00:40:16 Alex Schuster wrote: > >> Philip Webb writes: > >>> There is a problem somewhere & it mb a small fix for my machine > >>> & it wb nice to track it down if others are not experiencing it. > >> > >> Try 'strace xterm' in a terminal with long scrollback history, ... > > Or better, use the '-o outputfile' option. > > >> ... press Enter a couple of times when it hangs > >> and analyze the output at these positions later. > > > > I did that earlier just for fun. The output is huge :-) > > > > 2400 lines when I did it with the same result as yours. > > > > I see here that while xterm is starting, the output stutters quite a lot > > and each time there is a "resource unavailable" message just before. > > It's trying to read fd3 which turns out to be the Unix socket in /tmp . > > Yes, there are 3 lock file/dirs there : > > root:527 tmp> ls -la > total 5 > drwxrwxrwt 7 root root 200 2009-11-17 16:41 . > drwxr-xr-x 23 root root 560 2009-07-04 05:53 .. > drwxrwxrwt 2 root root 88 2009-11-17 12:50 .ICE-unix > drwx------ 3 purslow purslow 192 2009-11-17 16:30 kde-purslow > drwx------ 2 purslow purslow 240 2009-11-17 16:32 ksocket-purslow > -r--r--r-- 1 root purslow 11 2009-11-17 12:47 .X0-lock > drwxrwxrwt 2 root root 72 2009-11-17 12:47 .X11-unix > > Are you using Nvidia ? -- someone else mentioned that as a possible cause.
Yes, nvidia-190.42-r3 I've noticed recently that kdm takes looooooong to start - more than 30 seconds, and xterm is still taking over 3 seconds to load. I'll try downgrade nvidia tomorrow when I have a chance and see what happens > > Otherwise, does anyone have further suggestions ? > -- alan dot mckinnon at gmail dot com
