Bug 134928 - redhat-config-printer not finding module
Summary: redhat-config-printer not finding module
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: redhat-config-printer (Show other bugs)
(Show other bugs)
Version: 1
Hardware: i386 Linux
medium
high
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-10-07 11:21 UTC by Nirmalya Bhattacharya
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-10-07 11:32:36 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Nirmalya Bhattacharya 2004-10-07 11:21:56 UTC
Description of problem:
I have installed python 2.3.4 in /usr/local/python. I have created a
symlink to that from /usr/bin/python. Now I'm not able to configure my
 network printer (smb) by using the redhat-config-printer tool. This
is  the error:
======================================================================
Traceback (most recent call last):
  File "/usr/sbin/redhat-config-printer", line 11, in ?
    import printconf_tui
  File "/usr/share/printconf/util/printconf_tui.py", line 45, in ?
    from rhpl.translate import _, N_, textdomain_codeset
ImportError: No module named rhpl.translate
======================================================================

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Tim Waugh 2004-10-07 11:32:36 UTC
You can't upgrade Python to a new major version and expect existing
Python applications to continue working as before.

For a newer version of Python (and working system tools to go with
it), upgrade to Fedora Core 2.


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