Bug 1004878 - GNOME desktop cannot be installed from netinstall iso
Summary: GNOME desktop cannot be installed from netinstall iso
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 20
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-05 16:06 UTC by Mukundan Ragavan
Modified: 2013-09-05 17:45 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-05 17:45:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Screenshot showing the errror screen. (124.65 KB, image/png)
2013-09-05 16:06 UTC, Mukundan Ragavan
no flags Details

Description Mukundan Ragavan 2013-09-05 16:06:55 UTC
Created attachment 794351 [details]
Screenshot showing the errror screen.

Description of problem:
When GNOME desktop is chosen in anaconda for installation, an error appears which does not allow installation to proceed.

The error is

"The following software marked for installation has errors. This is likely caused by an error with your installation source. You can change you installation source or quit the installer"

The attached screenshot shows the error.

KDE Plasma workspaces can be chosen without problems.

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

anaconda-20.10-1

How reproducible:
Always

Steps to Reproduce:
1. Choose GNOME Desktop and click done.

Actual results:
Error as shown in screenshot and as mentioned above.

Expected results:
Installation should proceed.

Additional info:
I tested only x86_64 on Virtualbox. KDE, XFCE and minimal installation can proceed with the installation.

Comment 1 David Shea 2013-09-05 16:48:15 UTC
What installation source are you using? Does this occur if you use a different mirror? Can you post the logs from /tmp, in particular packaging.log?

Comment 2 Mukundan Ragavan 2013-09-05 17:45:36 UTC
Well, I do not get that error anymore and I have changed nothing. I guess it was a network issue?

I will close this now and reopen it if I hit this again. I will add all the log files if I hit it again.

Sorry!


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