issues logging in after fresh install fc16 SOLVED!!

[les]

On Sat, 2012-02-18 at 02:05 -0800, Les Howell wrote:
> 
> 
> --- On Fri, 2/17/12, Tim <ignored_mailbox at yahoo.com.au> wrote:
>         
>         From: Tim <ignored_mailbox at yahoo.com.au>
>         Subject: Re: issues logging in after fresh install fc16
>         To: "Community support for Fedora users"
>         <users at lists.fedoraproject.org>
>         Date: Friday, February 17, 2012, 8:29 PM
>         
>         On Fri, 2012-02-17 at 19:59 -0800, Les Howell wrote:
>         > NEW problem  ON login I get the Fedora version of BSD "Oh
>         No!
>         > something has gone wrong"  Only option button is logout.
>         This is not
>         > helpful...
>         
>         Agreed.
>         
>         >  Also get a SELinux alert but of course can't read it due to
>         the
>         > logout button screen blocking the world from view.
>         
>         Sometimes left or right clicking on some other part of the
>         screen,
>         apparently with no reaction, does prove useful in a delayed
>         manner
>         (something else shows up, or you do actually manage to log in
>         despite
>         the appearance that you're not going to be allowed to).
>         
>         Have you done a "yum update" after your install?  That made it
>         usable
>         for me.
>         
>         -- 
>         [tim at localhost ~]$ uname -r
>         2.6.27.25-78.2.56.fc9.i686
>         
>         Hi, Tim,
>         Yes, I did yum update immediately after the install.  Sorry I
>         left that out of the log.
>         I am sure it is something in my user account that is messing
>         up.  However I use a large number of tools, and have ongoing
>         development of some software, some embedded stuff and two
>         books in that directory, so I really  don't want to spend too
>         much time trying out vearious things.  If there is a log to
>         check, that would be wonderful.  dmesg didn't tell me anything
>         useful.  I am still poking the carcass, and found a few
>         interesting things:
>           1. the add users tools is in the "other" portion of the
>         menus.  I think it would be better in system tools.  There are
>         a few other things I would move.  But I can't drag and drop
>         them into the other menues.
>           2.  The shows what appears to be extra unformatted
>         partitions on the disk, at least if I am reading it correctly.
>         Not to worry I know because I have plenty of space, I just
>         wasn't expecting F16 to leave nearly half the disk
>         unformatted.
>          
>           I am going to spend tomorrow on it, then if I cannot resolve
>         the issue I will create a new user, and begin migrating
>         directories one at a time until things work.  However this is
>         no way the way things should work.  There is nothing more
>         frustrating than a useless error message with no clue what
>         caused it or where to look for more information.  Whoever
>         wrote that little bit of trivia needs to revisit it and
>         provide some useful guidance.
>         
>         And for those who don't like the new format of the desktop
>         +1.... to get to a specific application before with a right
>         click and a pull down, it is replaced with two clicks, a
>         scroll some more clicks and other handwaving of one sort or
>         another.  AND NO LIST.  What about the visually impared.  How
>         can a screen reader deal with this?
>         
>         Some lessons have to be learned again and again I guess.
>         
>         Oh well, back to the original problem.  I think I will try
>         another search based on the login time to see if I can find
>         another error file updated.  I looked at a lot before I found
>         the xsession-errors file that had been updated.  Maybe there
>         is another I missed.
>         
>         I will also try the trick of clicking somewhere else on the
>         screen.  thanks,
>         
>         Les H
>         

Well, I deleted a bunch of old gaming .xx directories in the user file
and one or two of applications I no longer use and things got better. 

I could log in, but not do anything. I restarted the system, and logged
in as my admin user, opened the selinux troubleshooter and found that
there were three problems, two with colord needing dbus read and another
that I can't read my own handwriting to figure out again.  

Followed the advice and set the policy to set those using audit2allow
and semodule -i as instructed.  Then touched /.autorelable and rebooted.
Next login I got "Could not create ICE listening socket.  Cannot
establish an listening sockets."  I suspected that this was due to a
setup issue for networking, so waited a bit and logged in.  Found
another SELinux error about colord, so added that one too.

Another /.autorelable, reboot login cycle and success.  Evolution
remapped the files and email now works (the earlier messages were sent
using webmail).

So looks good for now.  A more helpful error message would have saved me
about 12 hours of poking and prodding and googling. How do I get that on
the bug list, or has someone already done that?

So I am now on F16 FEL.  I still have lots to do, adding MPLABX from
microchip, OpenSCAD, skeinforge, the various eclipse packages for
android, C++, etc.  But the first 18 hours is over and it is up and
running.  Still better than Windows 7, which by the time I had the
various utilities running, took me three weeks. and two OS upgrades
ending at Ultimate and at great expense. (it still has some issues with
some of the development packages and somethings still have to be run as
admin.  Windows is not my favorite by a long shot.)

So solved for now.  Thanks Tim for your help.

Regards,
Les H