Bug 1004878

Summary: GNOME desktop cannot be installed from netinstall iso
Product: [Fedora] Fedora Reporter: Mukundan Ragavan <nonamedotc>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: anaconda-maint-list, dshea, g.kaviyarasu, jonathan, mkolman, nonamedotc, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-05 17:45:36 UTC Type: Bug
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 Flags
Screenshot showing the errror screen. none

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!