Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 217664 - Persistence of out of date NFS mounts causing startup delay
Persistence of out of date NFS mounts causing startup delay
Product: Fedora
Classification: Fedora
Component: gnome-session (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
Depends On:
  Show dependency treegraph
Reported: 2006-11-29 04:17 EST by Adam Huffman
Modified: 2008-03-18 14:33 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-03-18 14:33:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Adam Huffman 2006-11-29 04:17:58 EST
Description of problem:
Recently I have changed ISP, which has led to a change of network address at
home.  This means my NFS mounts are of course at different addresses than they
were before.

The problem is that at GNOME session startup gnome-terminal is starting up and
trying to open a tab with one of the old NFS mount locations.  This is causing
autofs to try and mount the old address, which doesn't work but takes a long
time to fail, causing nautilus to hang whilst this is going on.

The odd thing is that I have obviously not had a tab open at the old NFS address
for a week now, since the change to the new network.

I'm not sure whether this should be considered a bug in gnome-terminal or
gnome-session - please reassign if necessary.

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

How reproducible:
Every time

Steps to Reproduce:
1. Log in to GNOME
Actual results:
Nautilus and the initial terminal hang, waiting for the non-existing NFS mount

Expected results:
Nautilus and the terminal should start normally

Additional info:
Comment 1 Adam Huffman 2006-11-29 20:08:42 EST
Perhaps the component should be changed to gnome-terminal because this problem
seems to be caused by terminal wanting to open up 'obsolete' tabs i.e. from a
previous session, not the last one?

Though that might be caused by gnome-session.
Comment 2 Ray Strode [halfline] 2008-03-18 14:33:46 EDT

We no longer support Fedora Core 5 and I am currently trying to get my open bug
count down to a more manageable state.  I'm going to close this bug as WONTFIX.
 If this issue is still a concern for you, would you mind trying to reproduce on
a supported version of Fedora and reopening?

(this is a mass message)

Note You need to log in before you can comment on or make changes to this bug.