Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 152113 - system-config-network won't start: could not import gnomevfs
Summary: system-config-network won't start: could not import gnomevfs
Keywords:
Status: CLOSED DUPLICATE of bug 151577
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-network
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-03-24 23:02 UTC by Ricky Ng-Adam
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-03-25 07:09:04 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Ricky Ng-Adam 2005-03-24 23:02:48 UTC 
Description of problem:

system-config-network won't start, both at the command-line and from the GNOME
menus.

[ngadamri@localhost ~]$ system-config-network
Fatal Python error: could not import gnomevfs

Need to do 'yum install gnome-python2-gnomevfs' to make it work

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

1.3.23-1

How reproducible:

always

Steps to Reproduce:
1. Default workstation install
2. try to start system-config-network
3. 
  
Actual results:

At the GUI: no feedback, no app started

At the command-line: "Fatal Python error: could not import gnomevfs"

Expected results:

system network config application available without installing any additional
package.

Additional info:
Comment 1 Ricky Ng-Adam 2005-03-25 07:09:04 UTC 

*** This bug has been marked as a duplicate of 151577 ***
Note You need to log in before you can comment on or make changes to this bug.