Bug 75050

Summary: long delay opening window from home icon
Product: [Retired] Red Hat Linux Reporter: tom georgoulias <tomg>
Component: nautilusAssignee: Havoc Pennington <hp>
Status: CLOSED NOTABUG QA Contact: Jay Turner <jturner>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: alexl, srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-10-20 22:31:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
strace output
strace of nautilus freeze/crash behavior for #75050
strace -tf gedit none

Description tom georgoulias 2002-10-03 23:52:53 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
The first time I double click the home icon on my desktop, nautilus will pause
for a long time, appear to crash, then open a file manager window.  While this
is happening, the icon is shaded and I am able to launch new applications from
the panel.  I am not able to start anything new using the workspace menu panel
(right mouse button).  This seems to occur only after I manually start ppp from
a terminal window (ifup ppp0).  I often have mozilla and/or evolution running at
the same time.  I was successful in capturing this behavior in an strace and the
output file is attached.  

BTW, I'm not completely sure that ppp has anything to do with it, but since it's
normally the first in a series of things (terminal, dial up, evolution,
mozilla...) I start everytime I log in I figured I'd mention it.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Log in.
2. manually start ppp from terminal with ifup ppp0
3. start evolution and/or mozilla
4. double click home icon on desktop.

Actual Results:  Nautilus will "freeze", no window will open for a long time,
and the application appears to crash and respawn.

Expected Results:  File manager window should open, with the contents of my home

Additional info:

[tomg@gemini tomg]$ rpm -q nautilus

Comment 1 tom georgoulias 2002-10-03 23:54:41 UTC
Created attachment 78484 [details]
strace output

Comment 2 tom georgoulias 2002-10-09 01:28:03 UTC
Created attachment 79546 [details]
strace of nautilus freeze/crash behavior for #75050

Comment 3 tom georgoulias 2002-10-09 01:34:58 UTC
I've attached a second strace of this problem, after having deleted the
following directories: .gnome*, .metacity/sessions/*, .gconf*, .nautilus and
letting the system recreate them.  I also formatted my disk and a did a fresh
install of 8.0 (I had previously gone from null to 8.0 by upgrading, not
reinstalling), just to be sure there wasn't any leftover stuff screwing me up. 
My /home was preserved when I installed 8.0, so I figured deleting the
directories mentioned above would do a decent job of wiping the slate clean. 
Other curious behavior I've noticed:  when nautilus takes a dive like this, I
cannot open gedit from the gnome menu nor from a terminal.

Comment 4 tom georgoulias 2002-10-16 22:20:55 UTC
I've confirmed that Nautilus only crashes/freezes/respawns like this when the
modem is up and running.  Nothing unusual happens until I dial in to my ISP, and
all problems go away after I disconnect and Nautilus respawns.

I'm guessing this bug is ultra-low priority simply because it hasn't been
scheduled yet, but if you have any fix suggestions or want more system info I'd
be glad to provide it.

Comment 5 Havoc Pennington 2002-10-17 20:51:28 UTC
nautilus is probably getting confused about some aspect of 
your network configuration; maybe reverse DNS lookup 
stops working, or the like. If you try connecting to the internet 
_before_ logging in, does gnome complain in a dialog as it starts up?

Comment 6 tom georgoulias 2002-10-18 04:11:41 UTC
Gnome doesn't even start up enough to display a dialog.  I connected my ISP in
run level 3, then used "startx" to start my gnome session.  The splash screen
image is displayed on a black background (instead of blue) and none of the icons
that appear as services are started ever showed up--everything just hung.  I
waited about 2 minutes for something to happen and nothing did, then switched to
another virtual terminal and disconnected the modem.  The splash image stayed
"frozen" for an additional 2-3 mins, then the blue background appeared and the
service icons started.  Once the gnome session was fully up, I still didn't see
any dialog at all about network problems.

I'm still confused about my inability to launch gedit from the gnome menu too. 
That happens as well (even now--just tried to open gedit while connected and
commenting on this bug report via mozilla and gedit won't display.  Disconnected
and gedit showed up about 1 minute later.)

Comment 7 Havoc Pennington 2002-10-18 06:16:47 UTC
I'm having trouble seeing where the hang is in the strace. 
Maybe strace with the "-t" option? Ideally one of the simpler apps 
instead of nautilus, something as simple as "gsearchtool" for example, 
if it hangs.

Comment 8 tom georgoulias 2002-10-18 23:30:04 UTC
OK, I've created a new strace with gedit.  Here's what I did:

1. Connected to my ISP with the modem.
2. strace -o /tmp/strace_gedit.out.tf -tf gedit
3. Disconnected the modem, then waited for gedit to start.
4. ^C after gedit was up and running.

Comment 9 tom georgoulias 2002-10-18 23:31:21 UTC
Created attachment 81045 [details]
strace -tf gedit

Comment 10 Havoc Pennington 2002-10-20 16:42:57 UTC
Looks like some kind of problem with the networking setup, see appended 
strace portion. Does "ping $(hostname)" work? "ping localhost"? 

1081  18:25:58 bind(16, {sin_family=AF_INET, sin_port=htons(833),
sin_addr=inet_addr("")}}, 16) = -1 EACCES (Permission denied)
1081  18:25:58 connect(16, {sin_family=AF_INET, sin_port=htons(111),
sin_addr=inet_addr("")}}, 16) = -1 EINVAL (Invalid argument)
1081  18:29:07 close(16)                = 0
1081  18:29:07 fstat64(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
1081  18:29:07 mmap2(NULL, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x4001b000
1081  18:29:07 write(1, "FAMOpen failed, FAMErrno=0\n", 27) = 27

Comment 11 Havoc Pennington 2002-10-20 16:43:20 UTC
(try the pings while net connection is active clearly)

Comment 12 tom georgoulias 2002-10-20 22:29:44 UTC
Got it resolved.  The network service daemon wasn't running because files from
the initscripts RPM were corrupted.  Reinstalled the initscripts RPM, verified
integrity of the RPM, and restarted the network service.  Everything is running
smoothly now.

Comment 13 tom georgoulias 2002-10-20 22:31:49 UTC
BTW, none of the pings worked before I reinstalled the RPM, but I'm sure that
doesn't really matter now since file corruption was the culprit.

Comment 14 Alexander Larsson 2002-10-21 08:59:45 UTC