Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 70513 - Nautilus hangs when switching to list view
Nautilus hangs when switching to list view
Status: CLOSED DUPLICATE of bug 70060
Product: Red Hat Public Beta
Classification: Retired
Component: nautilus (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Havoc Pennington
Jay Turner
Depends On:
  Show dependency treegraph
Reported: 2002-08-01 18:54 EDT by richard van kessel
Modified: 2015-01-07 18:58 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-08-01 18:54:16 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 richard van kessel 2002-08-01 18:54:12 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020724

Description of problem:
I just installed Limbo on an Athlon system. My desktop is drawn by Nautilus and
that works fine. When I use the Nautilus file manager, it works fine in ICON
view, but hangs permanently in LIST view.

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

How reproducible:

Steps to Reproduce:
1.Open Nautilus file manager window
2.Switch from ICON view (the default) to LIST view

Actual Results:  Nautilus hangs. Must kill app to close the hanging window. When
I do this it keeps trying to repaint the desktop, but crashes each time.

Expected Results:  See files in the selected directory in a LIST format.

Additional info:

I have also submitted a GNOME application bug report.
Comment 1 richard van kessel 2002-08-01 18:59:51 EDT
Sorry, I see that this was already reported in bug 70060 and has been resolved -
I will follow the suggestion and try version 2.0.2-1.


*** This bug has been marked as a duplicate of 70060 ***

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