I recently started seeing this behavior on up to date hardy. strace of various application (in this case, xterm) shows:
connect(4, {sa_family=AF_FILE, path="/tmp/.ICE-unix/9709"}, 21) = 0
fcntl(4, F_SETFD, FD_CLOEXEC) = 0
write(4, "\0\1\0\0\0\0\0\0", 8) = 8
read(4,
Then hangs forever. If I strace x-session-manager (in this case, gnome-session), I see:
$ strace -p 9709
Process 9709 attached - interrupt to quit
restart_syscall(<... resuming interrupted call ...>
Tried launching stuff, but nothing. The I tried strace with '-f', and got this extra information:
[pid 9790] read(24,
and it hangs there. I don't have a pig 9790 (a thread maybe?). I do also have /usr/bin/seahorse-agent --execute x-session-manager, but this has been enabled for sometime, and I only within the last couple of weeks started to have this problem.
This is somewhat disturbing, as I wasn't actively fiddling with anything-- just 'working'. At the time of the hangs, I have in my logs:
Mar 21 10:41:43 severus dnsmasq[6127]: DHCPREQUEST(vnet0) 192.168.122.155 52:54:00:6b:39:72
Mar 21 10:41:43 severus dnsmasq[6127]: DHCPACK(vnet0) 192.168.122.155 52:54:00:6b:39:72 hardy-amd64-bind9
Mar 21 10:42:29 severus avahi-daemon[6009]: Withdrawing address record for fe80::2ff:c1ff:fe00:f992 on vnet1.
I *do* have ipv6 enabled. I have seen other bugs with avahi, and wonder if it is avahi related (eg bug #193432, but there are others).
I recently started seeing this behavior on up to date hardy. strace of various application (in this case, xterm) shows: tmp/.ICE- unix/9709" }, 21) = 0
connect(4, {sa_family=AF_FILE, path="/
fcntl(4, F_SETFD, FD_CLOEXEC) = 0
write(4, "\0\1\0\0\0\0\0\0", 8) = 8
read(4,
Then hangs forever. If I strace x-session-manager (in this case, gnome-session), I see:
$ strace -p 9709 syscall( <... resuming interrupted call ...>
Process 9709 attached - interrupt to quit
restart_
Tried launching stuff, but nothing. The I tried strace with '-f', and got this extra information:
[pid 9790] read(24,
and it hangs there. I don't have a pig 9790 (a thread maybe?). I do also have /usr/bin/ seahorse- agent --execute x-session-manager, but this has been enabled for sometime, and I only within the last couple of weeks started to have this problem.
This is somewhat disturbing, as I wasn't actively fiddling with anything-- just 'working'. At the time of the hangs, I have in my logs: c1ff:fe00: f992 on vnet1.
Mar 21 10:41:43 severus dnsmasq[6127]: DHCPREQUEST(vnet0) 192.168.122.155 52:54:00:6b:39:72
Mar 21 10:41:43 severus dnsmasq[6127]: DHCPACK(vnet0) 192.168.122.155 52:54:00:6b:39:72 hardy-amd64-bind9
Mar 21 10:42:29 severus avahi-daemon[6009]: Withdrawing address record for fe80::2ff:
I *do* have ipv6 enabled. I have seen other bugs with avahi, and wonder if it is avahi related (eg bug #193432, but there are others).