if "splash" and "quiet" are on, system crashes on startup

Bug #574943 reported by AlainKnaff
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Plymouth
New
Undecided
Unassigned
plymouth (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

If "quiet" and "splash" are on in /boot/grub/menu.lst, system crashes shortly after startup.

The screen goes black (both on DVI and on VGA), and the system stays unresponsive to the network.

# lspci | fgrep VGA
01:05.0 VGA compatible controller: ATI Technologies Inc RS690 [Radeon X1200 Series]

Revision history for this message
Leo Arias (elopio) wrote :

What version of ubuntu are you using?

You should assign the bug to the package:
* plymouth since 10.04 Lucid Lynx,
* xsplash in 9.10 Karmic Koala and
* usplash in versions before that.

Thanks your report :)

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
AlainKnaff (kubuntu-misc) wrote :

10.04

Leo Arias (elopio)
affects: ubuntu → plymouth (Ubuntu)
Changed in plymouth (Ubuntu):
status: Incomplete → New
Revision history for this message
Steve Langasek (vorlon) wrote :

Please run 'apport-collect 574943' on the affected system.

Changed in plymouth (Ubuntu):
status: New → Incomplete
Revision history for this message
Leo Arias (elopio) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
AlainKnaff (kubuntu-misc) wrote :

I can no longer reproduce it on current versions of Kubuntu 10.04

But I suspect what happened was a combination between bug 574808 (RAID issue causing the actual failure to boot) and 574814 (display issue hiding any indication of what really went wrong).

Lesson learned: messing with the display during early boot is a really bad idea, because it removes means of tracking down other unrelated problems if it goes wrong.

Revision history for this message
Leo Arias (elopio) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in plymouth (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.