Bug 139229 - Package Manager can't find files on FC3 DVD
Summary: Package Manager can't find files on FC3 DVD
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-packages   
(Show other bugs)
Version: 3
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-11-14 09:06 UTC by Richard Levitt
Modified: 2007-11-30 22:10 UTC (History)
0 users

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

Attachments (Terms of Use)

Description Richard Levitt 2004-11-14 09:06:00 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041111 Firefox/1.0

Description of problem:
When trying to add software components which would be located beyond
CD 1 (e.g. Development Tools), Package Manager prompts for the
relevant CD as follows:

"Fedora Core 3" disk 2 needed to install packages
Insert the disk and press OK

If the original install was from an FC3 DVD, there are no further
disks.  All files are on a single DVD.  With that DVD in the drive, if
you press OK, Package Manager prompts as follows:

Unable to access Disk.
The disk was unable to be accessed for reading.  Please confirm that
it is the drive and try again.

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

How reproducible:

Steps to Reproduce:
1. From Desktop: Click on "Applications" -> "System Settings" ->
"Add/Remove Applications"
2.  Check "Development Tools".  Click "Update"
3.  Click "Continue"

Actual Results:  See above.

Expected Results:  Development packages should have installed from the

Additional info:

Comment 1 Richard Levitt 2004-11-14 09:59:50 UTC
Sorry - not a bug after all.  Loading the NTFS module seemed to stop
access to the DVD drive.  Fine after reboot.

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