This was caused by dnf dependency issues. Changing title of the bug to be more accurate.

(In reply to Dan Mashal from comment #0)
> Unable to install mate, kde, xfce, lxde on netinstall TC2
...

Do you mean you are attempting to install all of these together?

> Get errror checking software dependencies related to dnf.

Do you get a bug-reporting dialog or an error alert? Please describe what you actually see or attach a screenshot (or digital photo).

If you can get installer log files, could you attach them?
/tmp/anaconda-tb* from the install environment (ctrl-alt-f2) contains all the other logs. Otherwise, /tmp/*log.

Separate, uncompressed, text/plain.

I was unable to reproduce this issue with a XFCE install to VM from TC2 x86_64 netinstall iso.

Dan, can you attach your logs as requested in c#2?

I tried three times to reproduce this, but each time I got a fatal error alert:
"script error with package firefox"
which is Bug 1003230 (duped to Bug 1003691).

For the record, here is my procedure:

Start the installer with:
$ qemu-kvm -m 4096 -hda f20-test-3.img -cdrom ~/xfr/fedora/F20/Alpha/Fedora-20-Alpha-TC2-x86_64-netinst.iso -vga std -boot menu=on

Reclaim all disk space.

Select Basic Desktop for Base Environment in Software Selection.

Select these Add-Ons:
kde
lxde
mate
xfce

Click Begin Installation.

Discussed at 2013-09-04 blocker review meeting [1]. This is reject as an Alpha blocker, because this doesn't violate any F20 alpha release criterion and is a request for anaconda behavior change and thus doesn't qualify as a release blocking bug for F20 alpha.

We should be able to cover broken packages by other criteria and therefore ensure that installation is working properly. If there are cases which are not covered on package basis, please add useful information (like logs, screenshots, etc) and re-propose.

[1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-09-04/

Doing a VM kickstart text install of F20-Alpa-TC5 with rpmfusion rawhide enabled.  There are broken deps in rpmfusion rawhide, e.g.:

20:46,901 WARNING packaging: xine-lib-extras-freeworld-1.1.21-6.fc20.x86_64 requires libavcodec.so.54()(64bit)

However, I get no diagnostic output on the screen - instead the installer aborts and systemd shuts down the system preventing any kind on debugging.  I followed https://fedoraproject.org/wiki/Anaconda/Logging#Remote_logging_via_virtio and finally got:

20:46,901 WARNING packaging: xine-lib-extras-freeworld-1.1.21-6.fc20.x86_64 requires libavcodec.so.54()(64bit)
20:46,901 INFO packaging: gave up _yum_lock for AnaInstallThread
20:47,043 DEBUG anaconda: running handleException
20:47,922 DEBUG anaconda: Gtk cannot be initialized
20:47,922 DEBUG anaconda: In a non-main thread, sending a message with exception data
20:47,923 INFO anaconda: Thread Done: AnaInstallThread (140482842216192)

but that's it.

This possibly violates the Alpha installer bug reporting criteria, although there seems to be some question as to how broad that is:

http://fedoraproject.org/wiki/Fedora_20_Alpha_Release_Criteria#Failure_reporting

(In reply to Orion Poplawski from comment #6)
> However, I get no diagnostic output on the screen - instead the installer
> aborts and systemd shuts down the system preventing any kind on debugging. 

Orion, I believe it auto-restarts because you're doing a kickstarted installation. If you can reproduce the same issue with interactive install, that would be a serious problem, yes.

With kickstarted installation, you might want to remove "reboot" command from the kickstart or use "nokill" boot option:
http://fedoraproject.org/wiki/Anaconda_Boot_Options#nokill

(In reply to Steve Tyler from comment #2)
> (In reply to Dan Mashal from comment #0)
> > Unable to install mate, kde, xfce, lxde on netinstall TC2
> ...
> 
> Do you mean you are attempting to install all of these together?


No.


> > Get errror checking software dependencies related to dnf.
> 
> Do you get a bug-reporting dialog or an error alert? Please describe what
> you actually see or attach a screenshot (or digital photo).

IIRC it crashed. Will test again.
 
> If you can get installer log files, could you attach them?
> /tmp/anaconda-tb* from the install environment (ctrl-alt-f2) contains all
> the other logs. Otherwise, /tmp/*log.
> 
> Separate, uncompressed, text/plain.

Will test again (probably wont be able to reproduce now). The general point of this bug was if Anaconda hits a depsolving issue it crashes. The question is do we want to continue installation (with exceptions) or fail? I did discuss this with tflink and we'd rather fail (although I don't necessarily agree and this is my opinion)

(In reply to Kamil Páral from comment #8)
> With kickstarted installation, you might want to remove "reboot" command
> from the kickstart or use "nokill" boot option:
> http://fedoraproject.org/wiki/Anaconda_Boot_Options#nokill

Thanks, I'll try nokill.  Although in the past I've filed bugs from kickstart installs that aborted.  This just strikes me as a very unhelpful failure mode.