GNOME Bugzilla – Bug 139900
Hangup in g_spawn_async
Last modified: 2005-05-23 08:05:23 UTC
Get Nautilus running, open the control center. Double-click on any item (Theme, in my case). Same goes for files in any Nautilus window. Instead of performing its due action, Nautilus freezes. Tracing the problem leads to a child process that suspends while performing an execve to launch the program. Some glibc-internal interaction with other Nautilus threads is suspected, but I have no idea what it could be. Here is the backtrace to the main Nautilus process/thread:
+ Trace 45979
Created attachment 26602 [details] strace of nautilus complete with child processes Nautilus was launched under strace, then the steps were performed as described in this bug report, resulting in a hangup. After that, the processes were terminated with 'killall nautilus'.
Seems likely to be a nautilus-specific problem (maybe it's trying to read off a closed FD and reads off the spawn pipe?) Reassigning to nautilus for now.
I disagree. As it seems from the code, the blocked read would return 0 had the spawned child (actually, a grandchild) get over with execve. But for some reason glibc's execve routine turns aside and suspends on signals instead of descending promptly to the system call.
Mikhail: Thanks for your bug report! Do you still see this behavior?
No, I don't observe this behavior for a long time. Don't know if the culprit has gone, or just not getting executed.
Closing for now. Feel free to reopen this bug report if it still happens.