1 |
091112 Alan McKinnon wrote: |
2 |
> On Thursday 12 November 2009 00:40:16 Alex Schuster wrote: |
3 |
>> Philip Webb writes: |
4 |
>>> There is a problem somewhere & it mb a small fix for my machine |
5 |
>>> & it wb nice to track it down if others are not experiencing it. |
6 |
>> Try 'strace xterm' in a terminal with long scrollback history, ... |
7 |
|
8 |
Or better, use the '-o outputfile' option. |
9 |
|
10 |
>> ... press Enter a couple of times when it hangs |
11 |
>> and analyze the output at these positions later. |
12 |
> I did that earlier just for fun. The output is huge :-) |
13 |
|
14 |
> 2400 lines when I did it with the same result as yours. |
15 |
|
16 |
> I see here that while xterm is starting, the output stutters quite a lot |
17 |
> and each time there is a "resource unavailable" message just before. |
18 |
> It's trying to read fd3 which turns out to be the Unix socket in /tmp . |
19 |
|
20 |
Yes, there are 3 lock file/dirs there : |
21 |
|
22 |
root:527 tmp> ls -la |
23 |
total 5 |
24 |
drwxrwxrwt 7 root root 200 2009-11-17 16:41 . |
25 |
drwxr-xr-x 23 root root 560 2009-07-04 05:53 .. |
26 |
drwxrwxrwt 2 root root 88 2009-11-17 12:50 .ICE-unix |
27 |
drwx------ 3 purslow purslow 192 2009-11-17 16:30 kde-purslow |
28 |
drwx------ 2 purslow purslow 240 2009-11-17 16:32 ksocket-purslow |
29 |
-r--r--r-- 1 root purslow 11 2009-11-17 12:47 .X0-lock |
30 |
drwxrwxrwt 2 root root 72 2009-11-17 12:47 .X11-unix |
31 |
|
32 |
Are you using Nvidia ? -- someone else mentioned that as a possible cause. |
33 |
|
34 |
Otherwise, does anyone have further suggestions ? |
35 |
|
36 |
-- |
37 |
========================,,============================================ |
38 |
SUPPORT ___________//___, Philip Webb |
39 |
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto |
40 |
TRANSIT `-O----------O---' purslowatchassdotutorontodotca |