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, press the > enter key a couple of times when it hangs, and analyze the output at these > positions later. Or send these parts to the list, maybe someone here will > spot what's going on. > > Wonko >
I did that earlier just for fun. The output is huge :-) 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 If anyone feels like trawling through strace output, I can post what happens here. xterm is now taking 4 seconds to start whereas before it was almost instant -- alan dot mckinnon at gmail dot com
