Bug 73606 - Error using gettext in /usr/share/printconf/util/printconf_backend.py
Summary: Error using gettext in /usr/share/printconf/util/printconf_backend.py
Status: CLOSED DUPLICATE of bug 72177
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: printconf   
(Show other bugs)
Version: null
Hardware: i686 Linux
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2002-09-06 16:46 UTC by berto
Modified: 2007-04-18 16:46 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-09-06 16:46:53 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description berto 2002-09-06 16:46:47 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826

Description of problem:
the file printconf_backend.py would die with an error ( see below ).  After
adding the line:

import gettext

on line 26, everything worked fine.

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

How reproducible:

Steps to Reproduce:
1. run /etc/rc.d/init.d/lpd restart
2. see the error

Actual Results:  lpd dies not being able to setup any printers.

Expected Results:  lpd to gracefully start.

Additional info:

# /etc/rc.d/init.d/lpd restart
Stopping lpd:                                              [  OK  ]
Starting lpd: Traceback (most recent call last):
  File "/usr/sbin/printconf-backend", line 7, in ?
    import printconf_backend
  File "/usr/share/printconf/util/printconf_backend.py", line 32, in ?
NameError: name 'gettext' is not defined
No Printers Defined                                        [  OK  ]

Comment 1 Tim Waugh 2002-09-06 16:51:12 UTC
This has been fixed since redhat-config-printer-0.4.22-1B7 

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

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