Look at upstream bug report and patch at
http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb . The PR
number is 1576.
The synopsis is that the /proc format for thread status has changed,
and needs an update. I've proposed a patch that works on 2.6.
Something along these lines needs to get into Fedora, I think.
See follow up post to patch list at:
There's a minor tweak to the patch, and hopefully a maintainer'll look
OK - it was followed up with a note that the change to the kernel
would be reverted. My patch apparently wouldn't work in all
circumstances, so it ought not be applied - waiting on the kernel
reversion would seem like the way to go.
Reassigning to kernel.
Is this better with newer kernels?
No, it's still present. I'll post a reproducible test case this weekend.
Hmm, rather than try to go for the simplest test case, I'll tell you
what I've been seeing the problem with. Hopefully it or something
similar is easy enough to duplicate.
1. ssh-add a passhprase for some computer with ssh enabled (localhost
will probably do?)
2. Create an ssh connection to the computer in nautilus
("File->Connect to Server ("ssh://localhost/home/me" or something
similar for the syntax).
3. Wait for the target window to open up (can be slow). See that you
can open up folders or files with no difficulties.
4. Start nautilus up in your debugger (ddd for me, but I've seen it in
gdb). Attach to the current process and continue.
4. Again try to open folders or files on the ssh folder via nautilus.
5. The debugger will print "waiting for new child: No child
processes." and halt. Upon continuation, nautilus finds itself waiting
for the operation to complete forever, since ddd/gdb isn't able to
correctly figure out how to get the parent process an indication of
the status of the child (or so I presume).
6. If you close ddd/gdb and close the "Opening xxx" dialog, and let
nautilus resume, you can again begin accessing files and folders on
This should be fixed in the latest FC2 update.
Cool. My linux development boxen are currently in storage, but I'll test this out when I get
them unpacked in a few weeks.
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat. The Fedora legacy project will be producing further kernel
updates for security problems only.
If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.