Bug 76781
Summary: | Installer crashes after customized selection | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Petri T. Koistinen <thoron> | ||||
Component: | anaconda | Assignee: | Michael Fulbright <msf> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Brock Organ <borgan> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 8.0 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2002-11-02 22:59:14 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: | |||||||
Attachments: |
|
Description
Petri T. Koistinen
2002-10-26 12:46:17 UTC
Created attachment 82207 [details]
output of dmesg command on my system (textmode install)
*** This bug has been marked as a duplicate of 75008 *** My media is OK, your software is buggy. I have seen this error message on more than one machine with diffrent CD's. Fix GNOME canvas. These errors in the log you attached are due to read errors from the CD: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } hda: drive_cmd: error=0x04 { DriveStatusError } hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error } hda: drive_cmd: error=0x04 { DriveStatusError } If you purchased this product you can talk to customer care about a refund for the bad media. *** This bug has been marked as a duplicate of 75008 *** Dmesg.txt is after installation. hda: MAXTOR 6L080J4, ATA DISK drive And those errors are from smartd. How do you explain this: (gnome_canvas_path_any_closed): assertion 'path != NULL' failed It is a warning from the gtk+ python bindings that occurs when you go to the timezone screen with the world map on it. The gtk+ people were consulted and told us it was not a problem, just a warning. I would recommend if you have not already to mediacheck the CDs on the exact system you're installing from. Also I would recommend trying a smaller install set than everything. Well, I did not select "Everything" in first install. I did the installation again, now with fewer partitions. It went OK, I did mediacheck: all CDs are OK. When installation was ready, I saw these messages repeated on text-mode screen: XsetInputFocus()failed What are these? How about the defaults partitions and LVM missing from text-mode Disk Druid? How about saying sorry if installer crashes? People use lot of time to install Red Hat. Your paying customers might get annoyed if they experience problems with installation. Say sorry if installer crashes, it does not cost you anything, but makes people less angry. You can do this only if you are willing to admit that your software is not perfect. You can't prevent all installer crashes, but you should detect them all. Text mode installations do not support LVM. CD drives and media are not 100% robust, and it is quite common from reading these thousands of bug reports (over 75% are due to bad media) to see cases where repeated attempts to read marginal media will work. Because the mediacheck sequentially reads the CD it does not exactly simulate what happens during an install where filed are being accessed from different parts of the CD over time. We certainly care about our customers and users who download Red Hat for free. Our bug tracking system is open to anyone w/o a fee to use it, and you don't even have to buy our product to report a bug. However this bugtracking system is not a support mechanism, it is solely for tracking defects in the software. Issues like you have reported are due to media issues and our Customer Support will work with you to get replacement media. I would recommend openning a bug report against the XFree86 package with details about the XSetInputFocus() errors you are now seeing. *** This bug has been marked as a duplicate of 75008 *** |