Bug 604726

Summary:	[abrt] crash in system-config-firewall-1.2.25-1.fc13: etc_services.py:74:load:IOError: [Errno 2] Aucun fichier ou dossier de ce type: '/etc/services'
Product:	Red Hat Enterprise Linux 6	Reporter:	Thomas Woerner <twoerner>
Component:	system-config-firewall	Assignee:	Thomas Woerner <twoerner>
Status:	CLOSED CURRENTRELEASE	QA Contact:	qe-baseos-daemons
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.0	CC:	atodorov, azelinka, pknirsch, twoerner
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	abrt_hash:4b62c7ba
Fixed In Version:	system-config-firewall-1.2.26-1.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	603099	Environment:
Last Closed:	2010-11-10 21:41:15 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:
Bug Depends On:	603099
Bug Blocks:

Description Thomas Woerner 2010-06-16 15:24:20 UTC

+++ This bug was initially created as a clone of Bug #603099 +++

abrt 1.1.1 detected a crash.

architecture: x86_64
cmdline: /usr/bin/python /usr/bin/system-config-firewall
component: system-config-firewall
executable: /usr/bin/system-config-firewall
kernel: 2.6.33.5-112.fc13.x86_64
package: system-config-firewall-1.2.25-1.fc13
reason: etc_services.py:74:load:IOError: [Errno 2] Aucun fichier ou dossier de ce type: '/etc/services'
release: Fedora release 13 (Goddard)

backtrace
-----
etc_services.py:74:load:IOError: [Errno 2] Aucun fichier ou dossier de ce type: '/etc/services'

Traceback (most recent call last):
  File "/usr/bin/system-config-firewall", line 36, in <module>
    import fw_gui
  File "/usr/share/system-config-firewall/fw_gui.py", line 31, in <module>
    import etc_services
  File "/usr/share/system-config-firewall/etc_services.py", line 123, in <module>
    services = _Services()
  File "/usr/share/system-config-firewall/etc_services.py", line 71, in __init__
    self.load()
  File "/usr/share/system-config-firewall/etc_services.py", line 74, in load
    fd = open(ETC_SERVICES, "r")
IOError: [Errno 2] Aucun fichier ou dossier de ce type: '/etc/services'

Local variables in innermost frame:
self: []

--- Additional comment from zbechir on 2010-06-11 10:30:08 EDT ---

Created an attachment (id=423299)
File: backtrace

--- Additional comment from twoerner on 2010-06-15 12:46:24 EDT ---

/etc/services is missing on your system according to the error message. Can you please add the output of "ls -laZ /etc/services".

--- Additional comment from zbechir on 2010-06-16 09:41:48 EDT ---

ls -laZ /etc/services
ls: impossible d'accéder à /etc/services: Aucun fichier ou dossier de ce type

--- Additional comment from twoerner on 2010-06-16 11:23:17 EDT ---

Your installation is broken. /etc/services is part of the setup package, which is a core component.

Please verify your system integrity with "rpm -Va" and reinstall failing packages with "yum reinstall <package>". Use "yum groupinstall core" to install missing core packages.

I have fixed system-config-firewall not to fail if /etc/services does not exist or is not readable. Fixed upstream: http://git.fedorahosted.org/git/?p=system-config-firewall.git;a=commit;h=ccd9052a513da3987d35dc516539863c343fc105

Will be part of next package release.

Comment 1 RHEL Program Management 2010-06-16 15:35:32 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 4 Alexander Todorov 2010-08-23 12:23:30 UTC

system-config-firewall-1.2.27-1.el6 prints on the console:
[Errno 2] No such file or directory: '/etc/services'

and doesn't crash in case of missing file. Moving to VERIFIED.

Comment 5 releng-rhel@redhat.com 2010-11-10 21:41:15 UTC

Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.