Bug 130463 - Unable to access "Computer"
Summary: Unable to access "Computer"
Keywords:
Status: CLOSED DUPLICATE of bug 130220
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Alexander Larsson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: FC3Target
TreeView+ depends on / blocked
 
Reported: 2004-08-20 17:12 UTC by Daniel Malmgren
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:05:11 UTC


Attachments (Terms of Use)

Description Daniel Malmgren 2004-08-20 17:12:03 UTC
Description of problem:
Double clicking on "Computer" on my desktop gives me a requester
saying "The collection view got an error in startup. The place cannot
be showed with this view." (My translation from Swedish)

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

How reproducible:
100%

Steps to Reproduce:
1. Double click "Computer" on the desktop
  
Actual results:
Abovementioned requester plus the following line in .xsession-errors:
** (nautilus:2234): WARNING **: A view failed. The UI will handle this
with a dialog but this should be debugged.

Expected results:
I'd like to see the contents of "Computer"

Additional info:

Comment 1 Daniel Malmgren 2004-08-20 17:18:05 UTC
Hmmmm... Removing gthumb from the system solved the problem. Seems the
computer has opened all folders in gthumb's collection view no matter
what I say in the settings and that this view didn't work with "Computer".

I guess this is still a bug though...

Comment 2 Daniel Malmgren 2004-08-21 11:47:10 UTC
I guess this is related:

http://bugzilla.gnome.org/show_bug.cgi?id=150357

Comment 3 Douglas Furlong 2004-08-23 13:01:55 UTC
This is a duplicate of Bug #: 130220  

Comment 4 Daniel Malmgren 2004-08-23 15:19:42 UTC

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

Comment 5 Red Hat Bugzilla 2006-02-21 19:05:11 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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