After update from Lucid Lynx to Maverick Xorg doesn't start

[Sascha Rehberg]

Binary package hint: syslinux

Hi, I had been using Lucid Lynx up to now and have done the update to the maverick meerkat version today.

Now what happens when I start my computer I see it prompting me for my login and password (but without the usual log in screen), when I do that it says:

Welcome to Ubuntu!
0 packages can be updated
0 updates are security updates

hislordship@thrumptoncastle:~$

What am I supposed to enter here to get the computer started???

[Sascha Rehberg (sascharehberg)]

I am new to this - so not sure if it has anything to do with syslinux... I entered it here because on the known bugs page that was the only one that had anything to do with not booting...

[Dave Gilbert (ubuntu-treblig)]

Hi,
  I doubt it's syslinux, because it's actually let you get to a login prompt; it feels more like a graphics driver problem.

Can you from that login prompt run the following commands and append the output to this bug:

lspci | grep -i vga
jockey-text -l

and also if you can attach the /var/log/Xorg.0.log from your machine to this report.

Dave

[bugbot (bugbot)]

Hey Sascha,

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

[Bryce Harrington (bryce)]

Not enough information has been provided to troubleshoot. See http://wiki.ubuntu.com/X/Reporting for instructions on reporting X issues.