Ubuntu
gdm package

(auto)login failed after upgrade feistyfawn herd5 to 7.04

Bug #102508 reported by maarten
2
Affects Status Importance Assigned to Milestone
gdm (Ubuntu)
Fix Released
Medium
Brian Murray

Bug Description

I did a clean install of feistyfawn herd 5 a few days ago,
I went to the securety and put the autologin on and it worked fine.
I tried to dissable the passwordmanager (keyring) by modifying the gdm file, but it didn't work.
Today the updatemanger said there was a update to 7.04, so I did that.
During the installation I got the question if I want to keep the modified gdm file, I choose to use the one from the installer.
After the installation I did a reboot.
Now I get the loginscreen, but because iI had the autologin option on it tries to login and then say authentication failed.
The only option is to press ok after I get the same message again.

I'm no expert and can't repair it with recoverymode (just don't know how, so I wil do a new install)
Hopefully I'm the only one with this problem.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Have you already reinstalled? If not I may be able to help you out. Thanks in advance.

Revision history for this message
Sebastien Bacher (seb128) wrote :

When you replied to use the installer version you dropped the autologin setting since that was a change of your version, doesn't look a bug. Does login with your username and password work correctly?

Changed in gdm:
importance: Undecided → Medium
Revision history for this message
maarten (m-vorm) wrote :

I'm just back from hollyday.
Before my hollyday I did a new install bud didn't do any updates.
Tomorrow I will try to update because it will take some time (203 updates).

I will turn the autologin off before the new update, since the last time the login password was proberly not taken over correctly and than it keeps saying wrongpassword and you can't fill in another password.
(the loginname was taken correcly I think because the number of digits was right.)

Revision history for this message
maarten (m-vorm) wrote :

After the update without any problems I did a restart.
Grub was loading fine, direcly after that I got this message:

starting up ...
[ 17.799287] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 17.799332]

The system hangs, even 5 seconds on the powerbutton dont help, so I pulled out the plug.
Restart, same problem.

I hope this is helpfull for someone, but I'll wait for the final release before doing any updates.

Revision history for this message
Sebastien Bacher (seb128) wrote :

he new comment looks like a linux bug

Revision history for this message
maarten (m-vorm) wrote :

with esc I got into the grubmenu and succesfully loaded ubuntu by choosing 2.6.20-9
standard it was 2.6.20-15, with the kernel panic message
with 2.6.20-14 it looks like it will load ubuntu, but only the first block (ubuntu logo) then nothing happens.

Is there a way to see what the system is loading/doing instead of the ubuntu logo?

Revision history for this message
maarten (m-vorm) wrote :

Just did another update witch fixed the problem and I can load linux again with the 2.6.20-15 kernel.

Revision history for this message
Brian Murray (brian-murray) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. Thanks again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Changed in gdm:
status: Needs Info → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.