Bug 66502 - Installer crashes mozilla package
Summary: Installer crashes mozilla package
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 7.3
Hardware: athlon
OS: Linux
high
high
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-06-11 15:13 UTC by Andre Marais
Modified: 2006-02-21 18:49 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:49:04 UTC
Embargoed:


Attachments (Terms of Use)

Description Andre Marais 2002-06-11 15:13:07 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.0 (X11; Linux i686; U;) Gecko/20020408

Description of problem:
On _really_ fast machines (XP 1800+) with 333MHZ bus, promise IDE controller,
and 56x CDROM causes race conditions in the installer to come through.
Mozilla package is still running pre-install scripts when the installer tries to
unmount the CD-ROM. This causes a crash due to "Device busy" being returned
(Some files are still open on the device).

Version-Release number of selected component (if applicable):
Default on installation CD of RedHat 7.3

How reproducible:
Sometimes

Steps to Reproduce:
1. Select packages (Specifically Mozilla libs and mozilla packages).
2. Start installation
3. Soon before the prompt for next CD (and after unmount of CDROM) the race
condition might (or might not on slow machines) occur.
	

Actual Results:  - Installer crashes completely (Debugging the Python code shows
it crashes on umount().

Additional info:

Comment 1 Jeremy Katz 2002-06-11 15:40:33 UTC
Could you please attach the traceback?  Also, have you run mediacheck on your cds?

Comment 2 Michael Fulbright 2002-07-15 16:55:27 UTC
Closing due to inactivty, please reopen if you have additional information to add.

Comment 3 Red Hat Bugzilla 2006-02-21 18:49:04 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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