ubuntu gnome does not boot after install - blank screen after grub menu

[Johan Nilsson]

I installed Ubuntu GNOME Desktop amd64 with the with the 20150422 vivid daily ISO on my laptop. The installer finished without any issues and the system rebooted. When the system started again the grub menu appeared and I selected "Ubuntu". After this the screen went blank, the backlight turned off, and nothing else happend (here I expected ubuntu gnome to boot).

Hardware Info:
https://gist.github.com/3e2acb9303c62ecae4b8

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1447356

[Johan Nilsson (johan5)]

I found a way to boot into the gnome desktop. After starting the computer as described above I let it sit for a few minutes with a blank screen then I closed the lid and allowed it to suspend and then I resumed again. Now the gnome start screen appeared and I could log in normally.

After log in I got a message "Sorry, Ubuntu 15.04 has experienced an internal error", according to the details /lib/systemd/systemd-logind had crashed with the title "systemd-logind crashed with SIGABRT in __read_nocancel()", I let the tool submit the crash report and after that I could navigate the desktop as expected.

[Brian Murray (brian-murray)]

Could you get the OOPSID of that crash report? You can find it by grep'ing /var/log/syslog for "OOPSID" e.g. "grep OOPSID /var/log/syslog".

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Anders Feder (afeder)]

I have what seems to be an identical issue: black screen after GRUB instead of login GUI, no cursor, no backlight. I have NVIDIA Optimus plus integrated Intel graphics, though - not Radeon.

[Johan Nilsson (johan5)]

Here are the OOPS IDs:
1750e7fa-e93b-11e4-beb5-fa163e78b027
4a8c3ca8-e9f6-11e4-b32c-fa163e707a72

If I remember correctly I ran into the same issue two times.

[Brian Murray (brian-murray)]

The two crashes are the same and they both are bug 1431141. I think that's unrelated to your screen being blank but you might want to comment on that other bug.

[Ronan Jouchet (ronj)]

Hi, I am hitting the same exact symptoms (blank screen after grub), but my case might differ:

1. I don't have any kernel oops in my syslog
2. Boot fails if I use the default grub entry, but succeeds if I use "recovery mode" then just resume booting.

Are we sure this bug is about the kerneloops, or might we be hitting the same issue?

Specs: machine was originally on 14.10 and was `do-release-upgrade`d. Arch is x86_64 and GPU is nv using package nvidia-346-updates.

[Anders Feder (afeder)]

The recovery mode -> resume normal boot workaround works for me too.

[Brian Murray (brian-murray)]

Although both of you are experiencing the same symptom, it'd be best to open a separate bug report for each system.

[Anders Feder (afeder)]

brian-murray: Will do. How do I generate a hardware info report like the one in the OP's bug description?

[Brian Murray (brian-murray)]

I don't know but if you report a bug using apport it'll gather useful information for your system. I'd recommend the following command "ubuntu-bug plymouth".

[Anders Feder (afeder)]

I've opened my report here: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1447838

[Johan Nilsson (johan5)]

I tried the recovery mode -> resume normal boot workaround and it works for me as well.

[Tony O'Rourke (tor-irl)]

Same for me but plugging in an external monitor fixes it as well.

[Johan Nilsson (johan5)]

The problems I'm having with my pc, which made me file this report, is not related to the nvidia graphics drivers, my pc has AMD graphics.

[Tony O'Rourke (tor-irl)]

A fresh install on a new partition fixed the problem for me.

[Joselotl (joselotl)]

I had the same problem with an Intel+Nvidia optimus card. recovery mode -> resume normal boot workaround worked. Adding nomodeset to grub options solved the problem.