On 2/1/06, Ignacio Vazquez-Abrams <ivazquez(a)ivazquez.net> wrote:
On Tue, 2006-01-31 at 23:54 -0800, Miles Lane wrote:
> 23:44:28.679226 read(12, "\7\0GnomeSM\0001.\7\0002.13.90779", 24) = 24
> 23:44:28.679444 write(12, "\1\1\1\0\1\0\0\0\0\0\0\0\0\0\0\0", 16) = 16
> 23:44:28.680102 read(12, "\1\2\0\1\6\0\0\0", 8) = 8
> 23:45:08.673703 read(12, "%\0\0\000105efac86c000113877990800000"..., 48) =
48
> 23:45:08.674175 write(12,
> "\1\f\1\0\t\0\0\0\1\0\0\0\0\0\0\0\20\0\0\0CurrentDirec"..., 80) = 80
> 23:45:08.674567 write(12,
> "\1\f\1\0\10\0\0\0\1\0\0\0\0\0\0\0\t\0\0\0ProcessIDrec"..., 72) = 72
This part strikes me as interesting. It seems that for 40 seconds it
sits there twiddling its thumbs.
It looks like it's hanging on a read from this socket.
23:44:28.668172 connect(12, {sa_family=AF_FILE,
path="/tmp/.ICE-unix/2199"}, 21) = 0
Miles, does this behaviour still occur after you restart? If you've
updated things and it hasn't left the system in a stable state then
that might help. If it still happens, during the hang, try attaching
gdb to the process and get a backtrace. (You may need debuginfo
packages.)
n0dalus.