Ubuntu
gdm package

cannot log in after upgrade from 10.4 to 10.10 on amd64

Asked by gratefulfrog

After upgrading via the upgrade manager, I rebooted and found:

1. the default kernel wouldn't boot, just filled the screen with messages that I could not read - this was the case for a bug I reported on 10.04
2. the 1st kernel that would boot was the rt one.
3. this got me to the login screen but my password wouldn't work. I repeated it many times.

I now have no access to my system!

Please help me! I've been a long time supporter and debugger for Ubuntu, but now a feel abandoned!

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu gdm Edit question
Assignee:
No assignee Edit question
Solved by:
gratefulfrog
Solved:
Last query:
Last reply:

This question was originally filed as bug #718388.

Revision history for this message
gratefulfrog (gratefulfrog) said : 		#1

Thanks for looking into the bug.

I am totally blocked now. Is there anything I can do to gain access to my
machine?

Thanks,
Bob.

On Sun, Feb 13, 2011 at 10:01 PM, Fabio Marconi
<email address hidden>wrote:

> ** Package changed: ubuntu => gdm (Ubuntu)
>
> ** Tags added: lucid
>
> ** Tags added: lucid2maverick
> ** Tags removed: lucid
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/718388
>
> Title:
> cannot log in after upgrade from 10.4 to 10.10 on amd64
>

--
 50°48'39.85"N 4°25'20.29"E

Revision history for this message
Sam_ (and-sam) said : 		#2

#1
If access to recovery mode is possible try some offered system repair options.
#2
Try login via tty and startx.
#3
If login via tty works, update grub, repair packages, review log files such as dmesg.
#4
Boot and repair via LiveCD, e.g. reinstall Grub, review dmesg.
#5
In case get a new passwd.

https://help.ubuntu.com/community/Grub2
https://help.ubuntu.com/community/LiveCdRecovery
https://help.ubuntu.com/community/LostPassword

Revision history for this message
gratefulfrog (gratefulfrog) said : 		#3

Hi Sam!
Thanks for your help.
I tried all the recovery kernels on my grub menu and finally found one that worked.
I ran the dpkg repairs, then logged in from the command line with my old password and startx and everything looks ok.
I am now doing a full backup of all the data on my system so that I'll be safe when I start "fixing".

Are there log files I could send you to help understand what's wrong?

I am wondering about the grub menu.lst?
I normally want the real time kernel, but it seems like another is called "default" although the pointer is aimed at "Ubuntu 10.10, kernel 2.6.31-11-rt"?
- Could you advise on how to clean up or re-build this file?
- Should I remove the "generic" kernel packages with apt, or do I need them for the rt kernel?
- Can you advise on what is best to get my system more solid? Should I scratch it, and re-install from zero? That sounds scary...
Again, Thanks for your help already and for any more you could offer!
Bob

Here are the non-commented lines from /boot/grub/menu.lst
-----
default 12
timeout 5
hiddenmenu
color cyan/blue white/blue

title Ubuntu 10.10, kernel 2.6.35-25-generic Default
root (hd0,0)
kernel /boot/vmlinuz root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 quiet vga=769
initrd /boot/initrd.img

title Ubuntu 10.10, kernel 2.6.35-25-generic Default (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 single
initrd /boot/initrd.img

title Ubuntu 10.10, kernel 2.6.32-28-generic Previous
root (hd0,0)
kernel /boot/vmlinuz.old root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 quiet vga=769
initrd /boot/initrd.img.old

title Ubuntu 10.10, kernel 2.6.32-28-generic Previous (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz.old root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 single
initrd /boot/initrd.img.old

title Ubuntu 10.10, kernel 2.6.35-25-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.35-25-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 quiet vga=769
initrd /boot/initrd.img-2.6.35-25-generic

title Ubuntu 10.10, kernel 2.6.35-25-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.35-25-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 single
initrd /boot/initrd.img-2.6.35-25-generic

title Ubuntu 10.10, kernel 2.6.32-28-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-28-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 quiet vga=769
initrd /boot/initrd.img-2.6.32-28-generic

title Ubuntu 10.10, kernel 2.6.32-28-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-28-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 single
initrd /boot/initrd.img-2.6.32-28-generic

title Ubuntu 10.10, kernel 2.6.32-26-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-26-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 quiet vga=769
initrd /boot/initrd.img-2.6.32-26-generic

title Ubuntu 10.10, kernel 2.6.32-26-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-26-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 single
initrd /boot/initrd.img-2.6.32-26-generic

title Ubuntu 10.10, kernel 2.6.32-25-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-25-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 quiet vga=769
initrd /boot/initrd.img-2.6.32-25-generic

title Ubuntu 10.10, kernel 2.6.32-25-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-25-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 single
initrd /boot/initrd.img-2.6.32-25-generic

title Ubuntu 10.10, kernel 2.6.31-11-rt
root (hd0,0)
kernel /boot/vmlinuz-2.6.31-11-rt root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 quiet vga=769
initrd /boot/initrd.img-2.6.31-11-rt

title Ubuntu 10.10, kernel 2.6.31-11-rt (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.31-11-rt root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 single
initrd /boot/initrd.img-2.6.31-11-rt

title Ubuntu 10.10, kernel 2.6.24-28-rt
root (hd0,0)
kernel /boot/vmlinuz-2.6.24-28-rt root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 quiet vga=769
initrd /boot/initrd.img-2.6.24-28-rt

title Ubuntu 10.10, kernel 2.6.24-28-rt (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.24-28-rt root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 single
initrd /boot/initrd.img-2.6.24-28-rt

title Ubuntu 10.10, kernel 2.6.22-14-rt
root (hd0,0)
kernel /boot/vmlinuz-2.6.22-14-rt root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 quiet vga=769
initrd /boot/initrd.img-2.6.22-14-rt

title Ubuntu 10.10, kernel 2.6.22-14-rt (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.22-14-rt root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 single
initrd /boot/initrd.img-2.6.22-14-rt

title Ubuntu 10.10, kernel 2.6.20-16-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 quiet vga=769
initrd /boot/initrd.img-2.6.20-16-generic

title Ubuntu 10.10, kernel 2.6.20-16-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.20-16-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 single
initrd /boot/initrd.img-2.6.20-16-generic

title Ubuntu 10.10, kernel 2.6.17-11-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.17-11-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 quiet vga=769
initrd /boot/initrd.img-2.6.17-11-generic

title Ubuntu 10.10, kernel 2.6.17-11-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.17-11-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 single
initrd /boot/initrd.img-2.6.17-11-generic

title Ubuntu 10.10, kernel 2.6.17-10-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.17-10-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 quiet vga=769
initrd /boot/initrd.img-2.6.17-10-generic

title Ubuntu 10.10, kernel 2.6.17-10-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.17-10-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 single
initrd /boot/initrd.img-2.6.17-10-generic

title Ubuntu 10.10, kernel 2.6.15-27-amd64-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-27-amd64-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 quiet vga=769
initrd /boot/initrd.img-2.6.15-27-amd64-generic

title Ubuntu 10.10, kernel 2.6.15-27-amd64-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-27-amd64-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 single
initrd /boot/initrd.img-2.6.15-27-amd64-generic

title Ubuntu 10.10, kernel 2.6.15-26-amd64-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-26-amd64-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 quiet vga=769
initrd /boot/initrd.img-2.6.15-26-amd64-generic

title Ubuntu 10.10, kernel 2.6.15-26-amd64-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-26-amd64-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 single
initrd /boot/initrd.img-2.6.15-26-amd64-generic

title Ubuntu 10.10, kernel 2.6.15-25-amd64-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-25-amd64-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 quiet vga=769
initrd /boot/initrd.img-2.6.15-25-amd64-generic

title Ubuntu 10.10, kernel 2.6.15-25-amd64-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-25-amd64-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 single
initrd /boot/initrd.img-2.6.15-25-amd64-generic

title Ubuntu 10.10, kernel 2.6.15-23-amd64-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-23-amd64-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 quiet vga=769
initrd /boot/initrd.img-2.6.15-23-amd64-generic

title Ubuntu 10.10, kernel 2.6.15-23-amd64-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.15-23-amd64-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 single
initrd /boot/initrd.img-2.6.15-23-amd64-generic

title Ubuntu 10.10, kernel 2.6.12-10-amd64-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.12-10-amd64-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 quiet vga=769
initrd /boot/initrd.img-2.6.12-10-amd64-generic

title Ubuntu 10.10, kernel 2.6.12-10-amd64-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.12-10-amd64-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 single
initrd /boot/initrd.img-2.6.12-10-amd64-generic

title Ubuntu 10.10, kernel 2.6.10-6-amd64-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.10-6-amd64-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 quiet vga=769
initrd /boot/initrd.img-2.6.10-6-amd64-generic

title Ubuntu 10.10, kernel 2.6.10-6-amd64-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.10-6-amd64-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 single
initrd /boot/initrd.img-2.6.10-6-amd64-generic

title Ubuntu 10.10, kernel 2.6.10-5-amd64-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.10-5-amd64-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 quiet vga=769
initrd /boot/initrd.img-2.6.10-5-amd64-generic

title Ubuntu 10.10, kernel 2.6.10-5-amd64-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.10-5-amd64-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 single
initrd /boot/initrd.img-2.6.10-5-amd64-generic

title Ubuntu 10.10, kernel 2.6.10-4-amd64-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.10-4-amd64-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 quiet vga=769
initrd /boot/initrd.img-2.6.10-4-amd64-generic

title Ubuntu 10.10, kernel 2.6.10-4-amd64-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.10-4-amd64-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 single
initrd /boot/initrd.img-2.6.10-4-amd64-generic

title Ubuntu 10.10, kernel 2.6.10-3-amd64-generic
root (hd0,0)
kernel /boot/vmlinuz-2.6.10-3-amd64-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 quiet vga=769
initrd /boot/initrd.img-2.6.10-3-amd64-generic

title Ubuntu 10.10, kernel 2.6.10-3-amd64-generic (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.10-3-amd64-generic root=UUID=260c7d17-77a1-4f82-9e5f-46ad2a97b150 ro console=tty0 single
initrd /boot/initrd.img-2.6.10-3-amd64-generic

title Ubuntu 10.10, memtest86+
root (hd0,0)
kernel /boot/memtest86+.bin

Revision history for this message
Sam_ (and-sam) said : 		#4

> Are there log files

As mentioned dmesg is the one which shows what happens during boot.

> wondering about the grub menu.lst

Me too, it looks a little crowded.
Maybe your disk is full? Are all these 21 images installed and needed?
I'd say try to clean-up first and then the system may not have a hiccup anymore.
Usually to keep at least two or three images should be fine.
## Kernel images don't get removed automatically during upgrades, they need to be removed manually via apt or Synaptic.

Don't know what the flags 'default' and 'previous' are about. Maybe it's a Grub_legacy feature, don't remember. ## Is there a reason for not using Grub_2?
https://help.ubuntu.com/community/GrubHowto

> pointer is aimed at "Ubuntu 10.10, kernel 2.6.31-11-rt

Found it only available for Lucid (10.04)
http://packages.ubuntu.com/search?suite=default&section=all&arch=any&searchon=names&keywords=linux-image-2.6.31-11-rt
I don't see -rt for Maverick there, but I'm not familiar with update policy of -rt images.
http://packages.ubuntu.com/search?suite=maverick&section=all&arch=any&searchon=names&keywords=linux-image

-rt kernel seems having some issues, reading this Bug #561288
and others.
https://launchpad.net/ubuntu/+source/linux-rt/+bugs

> Should I scratch it, and re-install from zero?

Depends on subjective cost-benefit ratio and available time.
If clean-up or else doesn't help, why not, the solid version would be 10.04 since it's a LTS which is supported till April 2013 (desktop).
If there is a separate /home partition you can even keep that unformatted and only format / to reinstall root fs.
You could download LiveCD 10.04.2 LTS with the latest snapshot to save updates.
http://releases.ubuntu.com/lucid/
https://wiki.ubuntu.com/LucidLynx/ReleaseNotes/ChangeSummary/10.04.2

> That sounds scary...

Why? You have backups and hopefully afterwards enjoy a clean system.

Revision history for this message
gratefulfrog (gratefulfrog) said : 		#5

Hi Sam,

I am now at a loss as to how to proceed.

I tried to remove all the extra kernels but got tons of error messages about directories not emptied.

I tried to install grub2, but I still can't get by the graphic login screen. I have to login via recovery mode to console, then startx manually.

What do you suggest? I am not a sys admin and really don't know what I'm doing or where to go.

I orginally was running 10.4 but wanted to upgrade to be more up to date. Now you say 10.4 was a better release?

Any advise would be good.
Thanks again,
Bob

Revision history for this message
Sam_ (and-sam) said : 		#6

How did you remove kernel images, manually by hand, with apt-get or Synaptic?
They need to be uninstalled 'completely' (option in Synaptic) or 'purged' (option of apt-get).
Grub_2 is already standard in 10.04 and 10.10.

I didn't say better, 10.04 is an LTS (long term support) no more no less.
https://help.ubuntu.com/community/UpgradeNotes

If you'd like to be updated consider a clean installation of 10.10.
https://wiki.ubuntu.com/MaverickMeerkat/ReleaseNotes
https://help.ubuntu.com/10.10/installation-guide/index.html
https://help.ubuntu.com/community/Installation

Revision history for this message
gratefulfrog (gratefulfrog) said : 		#7

Hi!
Thanks again for all your help!
I tired to remove the kernels via semantic using the "remove completely" option, but that seems to have failed, at least partially.

Using grub2 has made no difference. I cannot login on the graphic boot screen.

When I start the realtime kernel in "recovery mode" I can simply continue boot, login at the command line and startx.

When I select any other generic kernel, even in recovery mode, there are all sorts of error messages on screen and all I can do is a hard shutdown.

I think it's time to re-install from scratch. This time I will put the home directories on a separate disk, (or partition? what do you advise?)

Is there any good advice that is easy to understand and follow about partitioning or disk layouts for a robust install? I boot only to Ubuntu and used the rt kernel for rosegarden. I'm not sure that the rt kernel is still needed though :
>>
 at http://www.rosegardenmusic.com/wiki/Frequently_Asked_Questions
2. Recompile your kernel with system timer set to 1000 Hz. Sadly there's no way to change this without a recompile. It's the best solution though.
If you don't want to recompile your kernel and are running (K)Ubuntu, you can choose a lowlatency kernel from the repository (search for it with synaptic or your favorite tool). Install the new kernel and reboot. This will solve the problem and remove the lag.
<<

Again, thank you for all your help! The Ubuntu community remains the best there is! I wear my Ubuntu T-shirt with pride and repsect!
Ciao,
Bob.

Revision history for this message
Sam_ (and-sam) said : 		#8

As mentioned, with a separate /home partition one can keep it's configuration in case of reinstallation. Anything else is a matter of preferences, usage, paranoia or whatever.

https://help.ubuntu.com/community/DiskSpace
https://help.ubuntu.com/community/DrivesAndPartitions
http://members.iinet.net.au/~herman546/p17.html#help_on_partitioning

http://ubuntuforums.org/showpost.php?s=44dbd228b914c8e7591f08c5d1dada27&p=7297989&postcount=2

From what I've read regarding ubuntustudio -rt kernel is recommended, assume the same is true for rosegarden. In case post a separate question regarding rosegarden or ask on their website.
https://answers.launchpad.net/ubuntu/+source/rosegarden

Revision history for this message
gratefulfrog (gratefulfrog) said : 		#9

Hi Sam,

It's been a while, but I wanted to thank you for your help!

In the end, I bought a new disk and installed 10.10 from scratch. It seems to work perfectly.

I'm now going to try to install 10.10 next to Windows on my EEEpc!

Again, thanks for all your patient help - the Ubuntu community has always been and remains one of the greatest things about Ubuntu!

Ciao,
Bob.

Revision history for this message
Sam_ (and-sam) said : 		#10

Thanks for the feedback and giving 10.10 another chance, enjoy it.