Bug 158966 - nautilus will hang when browsing /proc
nautilus will hang when browsing /proc
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: nautilus (Show other bugs)
4.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tomáš Bžatek
desktop-bugs@redhat.com
:
: 187456 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-27 03:44 EDT by kai.bader
Modified: 2015-03-03 17:27 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 09:17:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description kai.bader 2005-05-27 03:44:46 EDT
Description of problem:

When using Nautilus to browse files, nautilus (nautilus 2.5.8) will
hang the window when browsing /proc.  Nautilus itself does _not_ hang,
but the the window that should show /proc hangs.

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


How reproducible:
always


Steps to Reproduce:
1.start nautilus
2.go to /proc
3.an wait :-)
  
Actual results:


Expected results:


Additional info:
same prob with Fedora C3
Comment 1 Alexander Larsson 2006-09-04 12:21:07 EDT
*** Bug 187456 has been marked as a duplicate of this bug. ***
Comment 2 Alexander Larsson 2006-09-04 12:21:59 EDT
Also seen in FC5. (See dup:ed bug.)
Comment 3 Jiri Pallich 2012-06-20 09:17:25 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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