Unable to log in except as root

edit

Please don't double post again, especially when you include such a massive block of quoted text. I must admit that I'm puzzled because you start off by saying that you're running Fedora 20, but every line in your boot log contains the word "ubuntu." Which is it? If you're running Fedora, why does your boot log read the way it is and if you're running Ubuntu, why are you asking here? Give me a reason not to close this as off-topic.

This is definitely Fedora, you can tell by looking at the log - the booting kernel is Linux version 3.15.7-200.fc20.i686 ( mockbuild@bkernel02.phx2.fedoraproject.org ) (gcc version 4.8.3 20140624 (Red Hat 4.8.3-1) (GCC) ) #1 SMP Mon Jul 28 19:21:33 UTC 2014

I honestly don't know why the boot log reads `ubuintu'. I assure you that I'm running Fedora on this disk as described above. And there was some issue with either the server or the network; I couldn't even get confrimation that the post occured even once.

Thanx, both of you. I didn't want to close the question when I wasn't sure, and your answers told me what I needed. @hawkfeather, this forum is currently being moderated. No posts, except from moderators, shows up until it's been accepted, so what you saw was normal. I'd much rather that the forum notified you that your post was waiting for moderation, but from what I can tell, the software running it doesn't do things like that. Just be patient; your posts will show up as soon as a (volunteer) moderator takes a look at it.

Please do not post debugging text, with too many lines. It is preferable to use fpaste for such long text. Thanks.

Thanx for the advice about fpaste. I'll remember that in future if I need it. And the reason why ubuntu appears in the boot log is likely because I was running Ubuntu on this disk before installing Fedora [18], and apparently neither anaconda or fedup changed the disk name.

Are you using an ubuntu kernel here?

@hello: No. As @jstanley noted above, the kernel in question is 3.15.7-200.fc20.i686. And as I explained above, Ubuntu was on the hard drive before I installed Fedora.

Did you reformat all of the partitions before reinstalling? Notably, if /home is not reformatted from your Ubuntu setup, it might result in this behavior. Alternately, if you're trying to dual boot Ubuntu and Fedora on the same disks, it may be to blame.

I repartitioned and reformatted the entire drive space when I reinstalled. I am not doing a dual boot; the drive in question is Fedora-only and Ubuntu is on a separate HDD. I have been using Fedora on this drive for months without difficulty until this behavior started a few days ago.

This whole Fedora/Ubuntu thing is a bit of a derailment.

Back to the question at hand, the log does not contain any errors. Please post the contents of /var/log/Xorg.*.log.

@QuLogic: Sorry it's taken so long to respond.
And I thought that the message generated by the yenta_cardbus driver that I posted above was an error msg. but maybe I was wrong.
At any rate, click here for the content of my /var/log/Xorg.0.log file.
Thanx in advance for any help you can provide, and for recognizing that the Ubuntu v. Fedora issue was a red herring.

What's a red herring? Please excuse my dumb questions. Try giving your user admin privileges (just a test, do not use this in real life). ;)

@hello: The phrase `red herring' is a slang expression meaning something that seems like it's highly relevant to an issue, but actually only serves as a distraction. Or as @QuLogic put it, `a derailment'. Click here for a more thorough definition.
And I don't know if this is another red herring or not, but I tried Fedora live media [Fedora 19] and it worked normally. Maybe I should check its /var/log/Xorg.*.log file against the one from the Fedora hard drive.

There's nothing that stands out in the log. Can you login from the console (Press Ctrl+Alt+F2)? What happens if you run startx from there?

@QuLogic: I'm afraid this issue is moot for the time being; I've reinstalled Fedora 20 KDE. But just for the record I'll say that attempts to log in as user never even got to the point where I could launch the terminal window at all.