F19: after upgrading I cant't login from gdm

[antonio montagnani]

After fedup'ing I have a fully updated system but surprise I cannot 
login, after the password insertion of any user I get a blank screen 
with the fedora log on the bottom, and nothing happens.

If I start from a console startx, it works fine.
Furthermore if the screen saver starts, if a password is required i get 
an authentication failure, same for any application asking for root 
password (i.e.yumex)

Running nouveau on a old FX5200 video card (but now Gnome 3 at least 
works, in F18 I was an fallback mode)
-- 
Antonio M
Skype: amontag52

Linux Fedora F18(Spherical Cow) on Acer 5720

http://lugsaronno.altervista.org
http://www.campingmonterosa.com

[Al Dunsmuir]

On Wednesday, July 3, 2013, 4:08:14 AM, Andew Robatino wrote:
>  antonio montagnani <antonio.montagnani <at> alice.it>
> writes: 
> > After fedup'ing I have a fully updated system but surprise I
> cannot 
> > login, after the password insertion of any user I get a blank screen 
> > with the fedora log on the bottom, and nothing happens. 
>  See 
>  https://bugzilla.redhat.com/show_bug.cgi?id=946964 
>  https://bugzilla.redhat.com/show_bug.cgi?id=955779 
>  If you're using gdm, and having the same issue, using any DM
> other than gdm
>  (for example lightdm) should allow logging into any DE. None of the other
>  testers saw this problem during testing, so it was deemed rare and didn't
>  block the release. 
See my append to 955779.

I  suspect  most  folks  test  with  the Live CDs and assume they will
behave the same as a final upgrade or full install.

Apparently  GDM  (and  the Gnome utility that create the initial user)
are  doing  something  weird and _incorrectly_forcing_ software rending
(which then behaves badly).

I was fine in both F19 alpha and beta Live Gnome experiments, but  the
actual installation  using final DVD (required to to dual boot  with XP)
does not work correctly.   This was after unsuccessful attempts to login
via GDM after F17 -> F19 via fedup.

I  have seen at least one other report of another user encountering the
same problem.

[Andre Robatino]

antonio montagnani <antonio.montagnani <at> alice.it> writes:

>  After fedup'ing I have a fully updated system but surprise I
> cannot 
>  login, after the password insertion of any user I get a blank screen 
>  with the fedora log on the bottom, and nothing happens. 
See

https://bugzilla.redhat.com/show_bug.cgi?id=946964

https://bugzilla.redhat.com/show_bug.cgi?id=955779

If you're using gdm, and having the same issue, using any DM other than gdm
(for example lightdm) should allow logging into any DE. None of the other
testers saw this problem during testing, so it was deemed rare and didn't
block the release.

[Corinna Vinschen]

On Jul  2 22:34, antonio montagnani wrote:
>  After fedup'ing I have a fully updated system but surprise I
> cannot
>  login, after the password insertion of any user I get a blank screen
>  with the fedora log on the bottom, and nothing happens. 
I had an analogue problem after yum distro-sync.  After logging in to
kdm, I just got the kdm desktop background and a mouse pointer I could
push around, but nothing else.

Looking into ps output, I saw that the usual xfce4 processes were
running, they were just not visible on the desktop for some magic
reason.  Per the log entries everything has run fine, no error message
at all.

I did the update with SELinux disabled and SELinux was still disabled
when this occured.  I also set SELinux to enforced and rebooted, which
relabled everything, but the problem persisted and there was nothing
pointing to an SELinux problem in the logs either.

I don't know if that helps in your case, but here's how I fixed it.

My login shell is tcsh.  In my .login file I had three entries to set
the tmp dir to ~/tmp:

  setenv TMP ~/tmp
  setenv TEMP ~/tmp
  setenv TMPDIR ~/tmp

At one point digging in the net, I read something about trouble when
some application couldn't write to /tmp.  So I had the crazy idea to
disable the above entries in my .login and I even removed the ~/tmp
directory entirely.

After init 3/init 5 (yes, I know), the next login worked as expected, my
xfce4 desktop showed up and the problem was fixed.

Next morning I thought it might be a good idea to write a bug report, so
I created ~/tmp again and enabled the above three environment vars in
.login, but it didn't help.  The xfce4 desktop still started normally.
I'm not able to reproduce the issue anymore.


Corinna