From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168) Gecko/20080404 Firefox/22.214.171.124
Description of problem:
Installed Fedora 9 on PS3 and selected lightweight window manager (XFCE).
Graphical login results in empty (nothing but background) desktop.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install Fedora 9 on PS3, unselect Gnome and select XFCE
2. Try to start graphical session
Session is started with only mouse cursor on default background (no window manager, nor windows)
A second X server is spawned and greeter activates (on other VC, which becames the active one)
Normal session startup
Can you attach your ~/.xsession-errors file?
Also, if you do a 'yum groupinstall XFCE' in a console what is the output?
Created attachment 305635 [details]
Created attachment 305637 [details]
Created attachment 305638 [details]
run of yum groupinstall XFCE
no .xsession-errors files found
yum groupinstall XFCE solves the problem.
Attached anaconda config and log.
It seems that for some reason installer fails to pull XFCE packages in even
though xfce-desktop is specfied.
Yeah, it looks like it didn't install them. ;(
What was your install method and media?
It looks like this bug is due to the a conditional package in the Xfce group:
im-chooser is available on the media, so anaconda decides it can offer the
entire Xfce group, when none of the other Xfce packages are on the media.
Installed using the release PPC DVD image, media test executed.
Yeah, that confirms the bug described in comment #7.
I have added this to the common issues page, so hopefully others running into it
will see the workaround.
Moving forward we should make sure this does not happen for F10.
(Not much we can do for F9 as the media is already shipped).
I am moving this bug over to anaconda to get fixed for the next release.
Also changing the Summary to be a bit more descriptive and adding it to the F10
Thanks again for reporting this!
*** Bug 450538 has been marked as a duplicate of this bug. ***
Surely this bug should block F10Blocker, not the other way around. Changing it.
The problem here is that the conditional as listed in comps was backwards, but this is fixed in F10 Alpha. Please try the alpha and verify that it's fixed. If not, feel free to reassign it back to us and we'll look at what we can do.