Description of problem: AlexL asked me to create a new user in order to investigate bug #119666 and so I logged in as root (I couldn't use "su" or "sudo" because of bug #119406 ) and used system-config-users to create a user called "jbq". I added the login name, full name, pass and also added the user to the wheel group. I did no other changes to that pref panel. It created the user and then I tried to relogin as jbq. But now it wouldn't login, it would say that /home/jbq does not exist (it DOES exist btw) and that I would need to use failsafe and the / folder as jbq's home folder! The only DE I was able to boot was XFce. Gnome/Default won't boot it would just spit me back to the login screen. In the meantime, the console 1, would give the following error message: audit (1001405726.966.0: avc: denied (getattr) for pid=4110 exe=/bin/bash path=/home/jbq dev=hda2 ino=1305829 scontext=system_u:system_r:xdm_t tcontext=root:object_r:home_root_t tclass=dir Honestly guys, the one bug brings me to the other. I only used Fedora for a few hours the last few days and all I do is find more and more important bugs. You might want to rename it as "alpha", cause this thing ain't no beta. :( Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. See above. 2. 3. Additional info:
I think that the user-related problems you are seeing are SELinux related. Did you install with SELinux in Active, Permissive, or Disabled mode?
ping?
*** Bug 121664 has been marked as a duplicate of this bug. ***
>Did you install with SELinux in Active, Permissive, or Disabled mode? Oops, sorry Brent, I somehome missed your question. I installed SELinux with the default found in Anaconda, whatever that default was.
Yes, the default was on in test2. In test3, we've disabled SELinux by default. The only way to enable it is to manually pass some boot time options. The disabling of SELinux will make this problem go away. This is working for me with the test3 trees. Please reopen this bug report if you see the same behavior with test3.