Usplash at startup kills virtual terminals - nVidia

Bug #448977 reported by gali98
36
This bug affects 9 people
Affects Status Importance Assigned to Milestone
usplash (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: usplash

When the decision was made a couple of days ago to use usplash on startup, it broke virtual terminals (ctrl+alt+f*) on my computer. I know this has happened before and it affected a lot of nVidia cards.
When I took "splash" out of the options in /etc/default/grub and ran update-grub2, it fixed the problem. (Because there was no usplash.)
When usplash is enabled, and you try to go to a virtual terminal, the screen is either black, or has random colored blocks all over the screen.

This may not be necessary for every user, but it is for a lot. If something happens to X, you have no backup terminal to fall back to and you have to manually power off the machine.

If you need more info, please ask. Apport should have attached everything. I'm on default grub2 with the karmic beta install.
Kory

ProblemType: Bug
Architecture: amd64
Date: Sun Oct 11 14:18:47 2009
DistroRelease: Ubuntu 9.10
MachineType: Hewlett-Packard HP Pavilion tx2000 Notebook PC
NonfreeKernelModules: wl nvidia
Package: usplash 0.5.42
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-13-generic root=UUID=0a19dd9d-a34c-4ef8-93a2-4f859ca819c1 ro quiet
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic
SourcePackage: usplash
Uname: Linux 2.6.31-13-generic x86_64
UsplashConf:
 # Usplash configuration file
 # These parameters will only apply after running update-initramfs.

 xres=1280
 yres=800
XsessionErrors:
 (gnome-settings-daemon:1884): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1884): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:1999): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:1980): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
dmi.bios.date: 04/18/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.08
dmi.board.name: 30E5
dmi.board.vendor: Quanta
dmi.board.version: 88.0A
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.08:bd04/18/2008:svnHewlett-Packard:pnHPPaviliontx2000NotebookPC:pvrRev1:rvnQuanta:rn30E5:rvr88.0A:cvnQuanta:ct10:cvrN/A:
dmi.product.name: HP Pavilion tx2000 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
gali98 (korylp) wrote :
tags: added: ubuntu-boot-experience
Revision history for this message
nerdy_kid (nerdy-kid) wrote :

I can confirm both the bug and the solution.

Nvidia Geforce 8600M GT
ubuntu 9.10
Dell Vostro 1500
usplash 0.5.42

gali98 (korylp)
Changed in usplash (Ubuntu):
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package usplash - 0.5.44

---------------
usplash (0.5.44) karmic; urgency=low

  [ Colin Watson ]
  * Add usplash_backend_name() function to the svgalib and bogl backends,
    returning "svga" and "bogl" respectively.

  [ Scott James Remnant ]
  * Move the console restoration into an atexit() function registered
    before the one from the svga or bogl backends; that way switching
    the VT doesn't result in svgalib having a panic attack and vomiting
    all over everything.
  * Remove the svgalib code guarding against restoring text mode when in
    a child process of the one that initialised the display; since we
    daemonise, this code meant we never restored text mode and left a
    corrupted or blank display. LP: #448977, #447692.

 -- Scott James Remnant <email address hidden> Wed, 14 Oct 2009 04:36:31 +0100

Changed in usplash (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
gali98 (korylp) wrote :

This was not fixed right in usplash 0.5.44.
Whilst usplash is running, switching to any of the virtual terminals will result in the same garbled screen with flashing colors.
Once X starts, you can switch to virtual terminal 1 (F1) and it works correctly, but the rest are corrupted. (A screen with white blocks filling the screen.)
What's more, when going back to X from a virtual terminal screen, it sometimes corrupts the screen in X. (an example is the top bar of gnome turns completely white. It is still clickable, but it doesn't refresh.) This may be a problem unrelated to usplash, but the rest is not. I am marking as confirmed again.
Kory

Changed in usplash (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
gali98 (korylp) wrote :

This was fixed as of 10/20/09. Thanks Guys!
Kory

Changed in usplash (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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