← Back to team overview

mythbuntu-bugs team mailing list archive

[Bug 579769] Re: [Lucid] Can't login, entering username/password blanks and refreshes screen asking for username/password

 

(Clearly an error about not having write permissions to the folder would
be a lot nicer.)

-- 
[Lucid] Can't login, entering username/password blanks and refreshes screen asking for username/password
https://bugs.launchpad.net/bugs/579769
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.

Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Invalid

Bug description:
On Lucid Final, fully updated, I cannot login to mythbuntu desktop or XFCE. When I type in my login credentials, it blanks the screen as if it is going into the desktop and then reloads the login screen. I can login using the same username/password in a terminal (Alt+Ctrl+F1). I chose to autologin, so this should not be requesting a login at all. /etc/gdm/custom.conf is set to autologin.

The system is an AMD 780G with a PCI-E 8600GT using nvidia-current drivers.

I have a different hard drive that has Mythbuntu Lucid Beta 2 installed on it and this is running perfectly (thankfully I have had enough issues in the past to keep this one ready to swap back in!)

I tried reinstalling Lucid on the new drive and this does the same thing (the only difference is that the login screen no longer lists "Mythbuntu" as a user, so I have to type it instead of selecting it -- it still reloads the screen each time I try to login.

I can login to "x-term" if I choose it in the dropdown box in the bottom right, but neither "Mythbuntu" nor "XFCE" let me login. 

I took a video of this to upload, but importing it into my laptop (also running Lucid) crashed the system and lost my first attempt at a bug report (it has an Intel 855GM so has all sorts of graphics issues that weren't in previous releases). This isn't relevant, but hopefully explains any brevity.

http://ubuntuforums.org/showthread.php?t=1320954&page=3 and some of the comments in Bug #463314 sound vaguely similar, but not really on point.  All the other bugs that I can find are about nvidia-legacy, rather than nvidia-current.

Please let me know if there is anything else that I can send you to help.





References