Bug 47748 - /tmp/install.log corrupted.
Summary: /tmp/install.log corrupted.
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: ttfm
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Matt Wilson
QA Contact: Brock Organ
URL:
Whiteboard:
: 48423 50346 50506 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-07-06 18:58 UTC by Telsa Gwynne
Modified: 2007-04-18 16:34 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-08-01 19:07:10 UTC
Embargoed:


Attachments (Terms of Use)
/tmp/install.log with binary chars (108.75 KB, application/octet-stream)
2001-07-13 19:26 UTC, Brock Organ
no flags Details
install.log with weirdo characters (56.70 KB, application/octet-stream)
2001-07-15 10:56 UTC, Telsa Gwynne
no flags Details

Description Telsa Gwynne 2001-07-06 18:58:18 UTC
Description of Problem:

The start of /tmp/install.log is corrupt following a laptop install
in text mode which died at the final stage but otherwise appeared to
have worked.

In bug 47147 I described a laptop install which resulted in an anaconda
crash at the end but which otherwise appeared to have worked. Looking at
/tmp/install.log I see a top line of
    Module /usr/share/fonts/install/xttfm.ttfm doesn't exist, ignored!
Then I see ^@^@^@^@^@^@ for seven screens, then without a linebreak I
find "Installing umb-scheme." and then it appears normal.

upgrade logs tend to have "The following were available but not
upgraded" at the end. I can't remember whether install logs should
have the same. There wasn't anything those. The final lines were
  Installing xml-i18n-tools.
  /usr/share/xml-i18n-tools directory created with perms 0755.
'file' tells me that /tmp/install.log is a data file.

Is all this down to the failure to complete the installer, or something
else?

Comment 1 Matt Wilson 2001-07-09 16:10:49 UTC
installs don't print out the "following were available but not upgraded."  This
is almost certainly a packaging problem.  Please attach the full log.


Comment 2 Matt Wilson 2001-07-10 17:40:06 UTC
*** Bug 48423 has been marked as a duplicate of this bug. ***

Comment 3 Brock Organ 2001-07-13 19:26:01 UTC
Created attachment 23550 [details]
/tmp/install.log with binary chars

Comment 4 Glen Foster 2001-07-13 19:46:58 UTC
This defect considered MUST-FIX for Fairfax gold-release.

Comment 5 Telsa Gwynne 2001-07-15 10:56:04 UTC
Created attachment 23628 [details]
install.log with weirdo characters

Comment 6 Telsa Gwynne 2001-07-15 10:58:21 UTC
Someone beat me to it, but I can't see 48423. I don't know whether the
few differences are significant or not. I suspect not, but there you are.
Apologies for delay :(

Comment 7 Matt Wilson 2001-07-20 01:50:21 UTC
fixed in cvs


Comment 8 Matt Wilson 2001-08-01 19:06:29 UTC
*** Bug 50506 has been marked as a duplicate of this bug. ***

Comment 9 Matt Wilson 2001-08-01 19:06:36 UTC
*** Bug 50346 has been marked as a duplicate of this bug. ***

Comment 10 Matt Wilson 2001-08-01 19:07:05 UTC
the ttfm package isn't redirecting its output to /dev/null

Comment 11 Matt Wilson 2001-08-01 19:09:54 UTC
rebuilt ttfm package to redirect all %post script output to /dev/null



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