Bug 128182

Summary: RFE: graceful recovery for system-config-network when files in /etc/sysconfig/ are unreadable
Product: [Fedora] Fedora Reporter: Keunwoo Lee <klee>
Component: system-config-networkAssignee: Harald Hoyer <harald>
Status: CLOSED UPSTREAM QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: mattdm
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-11-13 11:33:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
backtrace from crash none

Description Keunwoo Lee 2004-07-19 19:33:38 UTC
Description of problem: 
Whenever I execute system-config-network, the program crashes. 
 
Version-Release number of selected component (if applicable): 
system-config-network-1.3.17-0.FC2.1 
 
How reproducible: 
Run the program. 
 
Steps to Reproduce: 
1. Run the program. 
   
Actual results: 
Program crashes. 
 
Expected results: 
Program does not crash. 
 
Additional info: 
See attached Python backtrace.

Comment 1 Keunwoo Lee 2004-07-19 19:34:05 UTC
Created attachment 102051 [details]
backtrace from crash

Comment 2 Keunwoo Lee 2004-07-19 19:35:40 UTC

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

Comment 3 Keunwoo Lee 2004-07-19 19:40:04 UTC
Sorry about the rapid changes in status.  Upon further inspection 
this does not look like an exact duplicate of 98252, so I am 
reopening.  BTW my bug leads to a crash on application startup.  
Further information: 
 
$ ls -al /etc/sysconfig/hwconf 
b--xr-SrwT  65382 1718026086 4284900966 102, 102 Sep  6  
1969 /etc/sysconfig/hwconf 
 
Looks like something's wrong to me.  Running kudzu crashes with: 
 
# /usr/sbin/kudzu 
Traceback (most recent call last): 
  File "/usr/share/system-config-mouse/system-config-mouse.py", line 
56, in ? 
    useCliMode(mousetype, device, emulthree, help) 
  File "/usr/share/system-config-mouse/system-config-mouse.py", line 
32, in useCliMode 
    app = mouse_cli.childWindow(mousetype, device, emulthree, help) 
  File "/usr/share/system-config-mouse/mouse_cli.py", line 44, in 
__init__ 
    self.mouse.read() 
  File "/usr/lib/python2.3/site-packages/rhpl/mouse.py", line 230, in 
read 
    SimpleConfigFile.read(self, instPath + "/etc/sysconfig/mouse") 
  File "/usr/lib/python2.3/site-packages/rhpl/simpleconfig.py", line 
55, in read 
    f = open(file, "r") 
IOError: [Errno 6] No such device or address: '//etc/sysconfig/mouse' 
 
Let's look at /etc/sysconfig/mouse: 
 
s-ws--sr--  65484 3435986892 4291611852 4291611852 Nov 22  
1969 /etc/sysconfig/mouse 
 
Hmmm. 

Comment 4 Harald Hoyer 2004-07-20 09:23:40 UTC
errr... your filesystem looks completly broken!!! Really! Your may
have to reinstall! Did you play around with hdparm??

Comment 5 Keunwoo Lee 2004-07-22 02:31:26 UTC
My apologies.  It appears I had not run a full fsck after a recent 
unclean shutdown.  I still may have to reinstall but my system is 
mostly running better after a fsck. 
 
Nevertheless, there are any number of problems that can lead 
to /etc/sysconfig/* being unavailable.  It seems like a good idea to 
have system-config-network, which is end-user software, recover 
gracefully from errors reading these files instead of crashing with a 
backtrace.  I am reducing this bug's priority to enhancement and 
changing the title.  Thanks. 

Comment 6 Matthew Miller 2005-04-26 15:04:57 UTC
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.