Cannot login in graphical mode - Ubuntu 10.04 LTS
Solution 1
This appears to be a known bug with the GNOME Display Manager (gdm
) in Ubuntu 10.04 Lucid Lynx.
Comment #21 of that bug suggests disabling the Ubuntu logo splash screen will work around this issue. To do so temporarily, you may edit the kernel arguments from the GRUB menu and remove the splash
option. To do so permanently, remove splash
from the GRUB_CMDLINE_LINUX_DEFAULT
environment variable line in /etc/default/grub
, and run sudo update-grub
to make the changes take effect.
If that fails, you could also switch to a different display manager for the time being, like lightdm
or KDE's kdm
(which you can install without necessarily installing the KDE Plasma Desktop environment). You won't get GNOME's login screen, but you will still be able to login to a GNOME desktop. To install either of these, just run sudo apt-get install lightdm
or sudo apt-get install kdm
and restart. To login to a GNOME session, just choose GNOME
or Ubuntu Desktop
from the Session menu of your chosen display manager. It should remember your selection for future logins.
Solution 2
This is almost certainly an nvidia binary driver problem. Completely remove the binary nvidia driver (apt-get purge should do the trick; i forget the nvidia binary driver package - will a kind soul edit this answer?).
This should cause you to fall back to nouveau or vga. Nouveau will probably work but you will have some bugs and no 3D acceleration. (I had better luck w/ 10.10 and nouveau.)
VGA will certainly work but you'll be constrained to such a tiny screen size the only thing to do is install one of the other drivers.
user3127771
Updated on September 18, 2022Comments
-
user3127771 almost 2 years
How to convert the image with the following information: ColorType: truecolor Format: png bitDepth: 24
to a png grayscale image with bitdepth=8 in matlab ?
-
Patches about 13 yearsDid you install the proprietary Nvidia drivers, or are you using the built-in Noveau drivers? If you log in on the text console and run
startx
, can you get into GNOME? -
Botond Béres about 13 years@Patches: Updated my question with more info.
-
Patches about 13 years@Beres: Have you tried doing a full update? (
sudo apt-get dist-upgrade
) If that doesn't help, please post the contents of/var/log/gdm/:0-greeter.log
. -
Botond Béres about 13 years@Patches: Added the log output. So far I did
aptitude full-upgrade
, notapt-get dist-upgrade
however, as I would've liked to use latest LTS distribution. But I'll try to upgrade the distribution too, I'm curious if it fixes the issue. -
Botond Béres about 13 years@Patches: Please ignore my previous comment about
dist-upgrade
, my mistake. I do have all the packages up to date at the moment though. -
Patches about 13 years@Beres: The updates wouldn't have helped you anyway. Your
greeter.log
output indicates that you're experiencing a bug that has not yet been fixed by Canonical. I've posted an answer with two possible workarounds. -
Ratbert over 9 yearsBy convert, you mean create a new file ? How do you want to manage the extra bits, by truncation or by mapping the grey ranges ?
-
user3127771 over 9 yearsi tried to use imwrite(I2,nom_fich,'BitDepth',8); but e the image is always 24 bits: no change
-
Ratbert over 9 yearsOk, but can you answer the questions in the comment ?
-
user3127771 over 9 yearsthe method that will preserve as much quality.
-
-
Botond Béres about 13 yearsIt certainly seemed to be nvidia related, but I don't have the restricted drivers installed (fresh install, first login) so it looks like it's something else. Also removed all other nvidia related packages. Updated my question with more concrete info.
-
Broam about 13 yearsMy father's machine had this problem but it was from an upgrade from 8.04 -
kdm
solved the issue. -
Botond Béres about 13 yearsThanks a lot for your help. I didn't end up needing this however as the issue mysteriously disappeared after another reinstall and format of /home drive. Works fine even with restricted drivers enabled at the moment. On previous try I think I've missed formatting /home, however I did have other installs before that with reformatting, so that is not necessarily the obvious problem. Another difference is that I've set /home to be encrypted, but I'm not sure how that would "fix" this. If the issue suddenly reappears this workaround will certainly be the first thing I'll try.
-
Botond Béres about 13 yearsApparently the login issue only "went away" temporarily (on first boot after reinstall), after that it started behaving the same again. The
etc/default/grub
change didn't seem to help, but the workaround of installingkdm
and then choosing GNOME session was OK. -
Patches about 13 years@Beres: If you haven't already, you can add
splash
back to/etc/default/grub
and rerunsudo update-grub
to get your pretty boot screen back. Also, if you'd like, you can report your experience to that bug and subscribe to be notified when/if it is fixed.