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 118458 - redhat-logviewer sh: line 1: /usr/sbin/tux2w3c: No such file or directory
Summary: redhat-logviewer sh: line 1: /usr/sbin/tux2w3c: No such file or directory
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: redhat-logviewer
Version: 1
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Tammy Fox
QA Contact:
URL:
Whiteboard:
: 119627 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-03-16 20:28 UTC by Clive Long
Modified: 2007-11-30 22:10 UTC (History)
2 users (show)

Fixed In Version: 0.9.7-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-04-15 21:16:24 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Clive Long 2004-03-16 20:28:37 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031114

Description of problem:
Just updated Fedora Core 1 to XFree86 4.4 using XFree86 binaries from
XFree site - to try and solve X crash.

The active kernel is 2.4.22-1.2174.nptl 
When I run redhat-logviewer with the 4.4 version of X and kernel 2.4
end up with following error messages. The problem did NOT occur with
XFree 4.3 downloaded from Fedora mirror

********************************
Log view Start error messages follow
********************************
[clive_long@localhost sbin]$ redhat-logviewer
sh: line 1: /usr/sbin/tux2w3c: No such file or directory
Traceback (most recent call last):
  File "/usr/share/redhat-logviewer/redhat-logviewer.py", line 80, in ?
    LogViewerGui.LogViewerGui(width,height, allowConfigChanges,
configFile,initialView)
  File "/usr/share/redhat-logviewer/LogViewerGui.py", line 162, in
__init__
    self.initial_read_of_file()
  File "/usr/share/redhat-logviewer/LogViewerGui.py", line 343, in
initial_read_of_file
    logClassInstance = LogFileClass.LogFileClass(key)
  File "/usr/share/redhat-logviewer/LogFileClass.py", line 74, in __init__
    self.read_log(self.prefName)
  File "/usr/share/redhat-logviewer/LogFileClass.py", line 140, in
read_log
    self.buffer.insert_into_buffer_at_offset(iter, line)
  File "/usr/share/redhat-logviewer/LogBuffer.py", line 71, in
insert_into_buffer_at_offset
    langEnVar = os.environ["LANG"]
  File "/usr/lib/python2.2/UserDict.py", line 14, in __getitem__
    def __getitem__(self, key): return self.data[key]
KeyError: LANG


Version-Release number of selected component (if applicable):
redhat-logviewer-0.9.3-6

How reproducible:
Always

Steps to Reproduce:
1. run command redhat-logviewer

Actual Results:  See error messages above

Expected Results:  Log viewer starts correctly under Xfree86 4.4 as
under Xfree86 4.3

Additional info:
Comment 1 Tammy Fox 2004-03-16 20:39:32 UTC 
/usr/sbin/tux2w3c only gets executed if redhat-logviewer finds a Red
Hat Content Accelerator log file (/var/log/tux) to convert it to text.
Do you have a /var/log/tux file? Do you have the tux package installed?
Comment 2 Clive Long 2004-03-16 21:56:17 UTC 
1. Do you have a /var/log/tux file?
NO

2. Do you have the tux package installed?
[clive_long@localhost clive_long]$ rpm -q tux
package tux is not installed
Comment 3 Eric Lawson 2004-04-01 19:04:08 UTC 
I have the same bug using Redhat EL WS 3, and am also lacking a
/var/log/tux file, with no tux package installed (rpm -qa | grep tux)
returns nothing.
Comment 4 Tammy Fox 2004-04-15 15:55:05 UTC 
*** Bug 119627 has been marked as a duplicate of this bug. ***
Comment 5 Tammy Fox 2004-04-15 19:28:10 UTC 
I wan't able to reproduce the 
redhat-logviewer sh: line 1: /usr/sbin/tux2w3c: No such file or directory
error message on an FC1 system, but I am able to on an FC2 test2 machine.

I am looking at it now.
Comment 6 Tammy Fox 2004-04-15 21:16:24 UTC 
Fixed in version 0.9.7-1.
Note You need to log in before you can comment on or make changes to this bug.