Rodd Clarkson wrote:
On Thu, 2007-10-25 at 16:53 +0800, John Summerfield wrote:
Rodd Clarkson wrote:
On Thu, 2007-10-25 at 08:50 +0100, Caolan McNamara wrote:
On Thu, 2007-10-25 at 16:56 +1000, Rodd Clarkson wrote:
I've noticed two annoying issues in f8t3.
1. Applications seems to take quite a while to 'appear' on the desktop.
After clicking an application on the panel (gedit, gnome-terminal, etc)
it takes about 10 secs for them to appear on the desktop.
2. Evolution (particularly compose) seems to 'pause' for 10 seconds or
so every now and then and it becomes unresponsive. Makes typing emails
a pain in the bum (and I've seen it three times in this short email.)
I'm going to bz these, but we wondering if others have seen this too.
I've sometimes seen stuff like that happen with slightly busted
networking or something, i.e. strace -f gedit from a terminal and see if
it is blocking a long time on /tmp/.ICE-unix/XXXX and compare startup
time of apps before after after deleting /tmp/.ICE-unix/XXXX
<snip>
access("/home/rodd/.ICEauthority", R_OK) = 0
open("/home/rodd/.ICEauthority", O_RDONLY) = 11
fstat64(11, {st_mode=S_IFREG|0600, st_size=65366, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb7cb6000
read(11, "\0\4XSMP\0\0\0\35unix/unix:/tmp/.ICE-un"..., 4096) = 4096
close(11) = 0
munmap(0xb7cb6000, 4096) = 0
write(10, "\0\4\1\0\3\0\0\0\20\0\0\0\0\0\0\0\f+v($c\347x\204R\351\236
\02689\351", 32) = 32
read(10, "\0\10\0\1\3\0\0\0", 8) = 8
read(10, "\7\0GnomeSM\0001.\6\0002.20.13301", 24) = 24
write(10, "\1\1\1\0\1\0\0\0\0\0\0\0\0\0\0\0", 16) = 16
read(10, <snip>
There's a big pause at this point. Is this what you expect?
What's 10 pointing at? Go back to the open/connect.
Possibly something's trying to do a DNS lookup, and timing out (that
would give ten seconds, or a higher multiple).
Okay, here's more of the output. I've left a gap where I think it opens
10.
open("/etc/gnome-vfs-2.0/modules/mapping-modules.conf", O_RDONLY|O_LARGEFILE) = 10
fstat64(10, {st_mode=S_IFREG|0644, st_size=151, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7cab000
read(10, "#\n# Module configuration file fo"..., 4096) = 151
read(10, "", 4096) = 0
close(10) = 0
munmap(0xb7cab000, 4096) = 0
rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0
time(NULL) = 1193303788
mkdir("/home/rodd/.gnome2", 0700) = -1 EEXIST (File exists)
mkdir("/home/rodd/.gnome2_private", 0700) = -1 EEXIST (File exists)
stat64("/home/rodd/.gnome2_private/", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0
mkdir("/home/rodd/.gnome2/accels", 0700) = -1 EEXIST (File exists)
open("/usr/share/locale/en_US.UTF-8/LC_MESSAGES/libbonobo-2.0.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en_US.utf8/LC_MESSAGES/libbonobo-2.0.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en_US/LC_MESSAGES/libbonobo-2.0.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en.UTF-8/LC_MESSAGES/libbonobo-2.0.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en.utf8/LC_MESSAGES/libbonobo-2.0.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/share/locale/en/LC_MESSAGES/libbonobo-2.0.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
gettimeofday({1193303788, 369260}, NULL) = 0
gettimeofday({1193303788, 369335}, NULL) = 0
gettimeofday({1193303788, 369382}, NULL) = 0
socket(PF_FILE, SOCK_STREAM, 0) = 10
connect(10, {sa_family=AF_FILE, path=@/tmp/.ICE-unix/2546}, 22) = -1 ECONNREFUSED (Connection refused)
close(10) = 0
socket(PF_FILE, SOCK_STREAM, 0) = 10
connect(10, {sa_family=AF_FILE, path="/tmp/.ICE-unix/2546"}, 21) = 0
That's (almost certainly) so fifo - a named pipe, It's used to talk to
something else on the same host (even it a fifo is on a network
filesystem, it doesn't go over the wire).
Something's reading it, and if evolution's blocking for long on this,
then whatever's listening isn't being very responsive.
The lsof command (as root) should tell you who's reading it.
I still think it's nameserver timeouts.
Note that you can trace whatever's reading the pipe, you might need to
be root.
And it's about time I went home, the sun's low in the sky and food will
be offered rsn.
--
Cheers
John
-- spambait
1aaaaaaa@xxxxxxxxxxxxxxxx Z1aaaaaaa@xxxxxxxxxxxxxxxx
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
Please do not reply off-list
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
