After installing 10.04, gdm just constantly restarts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
Using an intel chipset. Worked fine in 9.10. After upgrading to 10.04, can't boot normally.
The splash screen comes up as normal. Then the screen blanks and an arrow cursor appears, with the sound that gdm normally makes. Instead of seeing the login dialog, the screen changes to a different black, then comes back, the sound is heard again, and this part repeats indefinitely.
Ctrl-Alt-F1 doesn't seem to help, nor Ctrl-Alt-Backspace. Hitting Ctrl-Alt-Delete at the right time (in between flashes) might make the machine reboot.
Changing the boot grub parameters to remove "quiet splash" and add "single" makes it so that I can login non-graphically. A "startx" is then successful, and normal operations can continue.
Can't figure out how to get gdm to start up properly.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.32-24-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'I82801DBICH4'
Mixer name : 'Realtek ALC658D'
Components : 'AC97a:414c4781'
Controls : 38
Simple ctrls : 24
Date: Wed Aug 25 19:45:53 2010
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
Lsusb:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Compaq Presario 061 PC129A-ABA SR1110NX NA430
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageV
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
dmi.bios.date: 05/17/2004
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 3.11
dmi.board.name: Gamila/Giovani/Neon series
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.board.version: 030
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: PC129A-ABA SR1110NX NA430
dmi.product.
dmi.sys.vendor: Compaq Presario 061
tags: | added: acpi-rsdp |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
K Everets, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please provide the information following https:/ /wiki.ubuntu. com/DebuggingKe rnelBoot ?
As well, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http:// cdimage. ubuntu. com/releases/ .
If it remains an issue, could you please run the following command in the development release from a Terminal (Applications- >Accessories- >Terminal) , as it will automatically gather and attach updated debug information to this report:
apport-collect -p linux <replace- with-bug- number>
Also, could you please test the latest upstream kernel available following https:/ /wiki.ubuntu. com/KernelMainl ineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag: testing
needs-upstream-
This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text: testing
needs-upstream-
If this bug is fixed in the mainline kernel, please add the following tags: fixed-upstream fixed-upstream- VERSION- NUMBER
kernel-
kernel-
where VERSION-NUMBER is the version number of the kernel you tested.
If the mainline kernel does not fix this bug, please add the following tags: bug-exists- upstream bug-exists- upstream- VERSION- NUMBER
kernel-
kernel-
If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags: unable- to-test- upstream unable- to-test- upstream- VERSION- NUMBER
kernel-
kernel-
Please let us know your results. Thank you for your understanding.