FL90 plymouth freezee after [enter] (VGA16FB)

Bug #520593 reported by 00raq00
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: plymouth

FL90 plymouth freeze after [enter] (reconfigure console-setup doesn't resolve problem)
I remove plymouth and works but it isn't good resolve...

ProblemType: Bug
Architecture: amd64
Date: Thu Feb 11 18:58:39 2010
DistroRelease: Ubuntu 10.04
DkmsStatus: Error: [Errno 2] No such file or directory
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113)
MachineType: - N/A
NonfreeKernelModules: nvidia
Package: xorg 1:7.5+1ubuntu2
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-13-generic root=UUID=e00c4565-5a4e-4f1c-97a5-ab3a543257b6 ro nohz=off quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
RelatedPackageVersions:
 xserver-xorg 1:7.5+1ubuntu2
 libgl1-mesa-glx 7.7-0ubuntu8
 libdrm2 2.4.17-0ubuntu2
 xserver-xorg-video-intel 2:2.9.1-1ubuntu4
SourcePackage: xorg
Symptom: display
Uname: Linux 2.6.32-13-generic x86_64
dmi.bios.date: 06/18/2008
dmi.bios.vendor: COMPAL
dmi.bios.version: 1.18
dmi.board.name: IFL90
dmi.board.vendor: -
dmi.board.version: IFT00
dmi.chassis.asset.tag: -
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnCOMPAL:bvr1.18:bd06/18/2008:svn-:pnN/A:pvrN/A:rvn-:rnIFL90:rvrIFT00:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: N/A
dmi.product.version: N/A
dmi.sys.vendor: -
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 architecture: x86_64kernel: 2.6.32-13-generic

Revision history for this message
00raq00 (00raq00) wrote :
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

security vulnerability: yes → no
visibility: private → public
Revision history for this message
Steve Langasek (vorlon) wrote : Re: FL90 plymouth freezee after [enter] (reconfigure console-setup doesn't resolve problem)

There's no reason that dpkg-reconfigure console-setup should have any effect.

Your bug report says that you are using the nvidia binary driver.

Please provide the following information:

 - did you see an Ubuntu logo at boot?
 - if so did it disappear before the spinning X cursor appeared?
 - if you don't see an Ubuntu logo, do you see a blue and white bar at the bottom of your screen?
 - show the output of 'cat /proc/fb'
 - show the output of 'ps aw | grep X.*vt' run from a console VT (Ctrl+Alt+F2)
 - what version of the grub-pc and grub-common packages do you have installed?
 - have you manually made any changes to your grub config (in particular, gfxpayload)?

Changed in plymouth (Ubuntu):
status: New → Incomplete
Revision history for this message
00raq00 (00raq00) wrote :

I use nvidia driver from nvidia.com

I don't see ubuntu logo but blue and withe bar.

cat /proc/fb:
0 VGA16 VGA

ps aw | grep X.*vt:
 1193 tty7 Ss+ 8:49 /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-IKdKLw/database -nolisten tcp vt7
10535 pts/1 S+ 0:00 grep --color=auto X.*vt

grub-pc -> 1.98~20100128~1ubuntu3
grub-common -> 1.98~20100128~1ubuntu3

I only add nohz=off into grub

Revision history for this message
00raq00 (00raq00) wrote :

0.8~10 plymouth dont resolve problem

Steve Langasek (vorlon)
Changed in plymouth (Ubuntu):
status: Incomplete → New
summary: - FL90 plymouth freezee after [enter] (reconfigure console-setup doesn't
- resolve problem)
+ FL90 plymouth freezee after [enter] (VGA16FB)
Revision history for this message
IKT (ikt) wrote :

Possible dupe of : 529230 ?

Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (4.1 KiB)

This bug was fixed in the package plymouth - 0.8.0~-13

---------------
plymouth (0.8.0~-13) lucid; urgency=low

  [ Steve Langasek ]
  * Don't attach /proc/cmdline to apport reports, this is already in the
    standard info that gets collected...

  [ Alberto Milone ]
  * ubuntu_logo theme:
    - New logo from Otto Greenslade.
    - Switch off dots starting from the ones on the left instead of
      switching them off all at once.

  [ Scott James Remnant ]
  * Move the Ubuntu logo up as discussed with Otto, this makes the mouse
    cursor appear between the logo and dots and solves the optical illusion
    of the logo being too low. LP: #535014.
  * Don't include message about disk checks, which can come from mountall.
  * Drop the rc script splash functions, we don't want the SysV-rc compat
    stuff messing around with the splash screen - this can be entirely
    managed by Upstart now. LP: #528787, #537262.

  * Plymouth Fix Mega Patch:
    - This hasn't yet been broken up into enough bits to send upstream, and
      doesn't *quite* address all the issues yet, but it's a major step.

    - Rewrite the VT handling, rather than abusing /dev/tty0 keep all VT
      operations on the actual VT (tty7), this avoids issues where we set
      the graphics mode of the wrong VT or put the wrong VT into VT_PROCESS
      mode. LP: #520460, #522598, #526321, #533135
    - Don't attempt VT switch when using non-VT consoles.
    - Make VT mandatory for renderer plugins, so we fallback gracefully to
      text when the console is not a VT. LP: #516825, #527083.
    - Restore VT when finished displaying the splash unless plymouth quit
      is called with --retain-splash. LP: #506297.
    - Activate VT from text and details plugins, rather than haphardly in
      the main code, this means the textual boot is also on VT7.
      LP: #518352, #520122.
    - Add a --has-active-vt command that can let gdm inquire whether it
      should reuse Plymouth's VT; fixes the issue where Plymouth has no
      visible splash screen and X ends up on VT1. LP: #519641, #533572.

    - Don't open terminal device in X11, fixes the issue where X will crash
      when debugging plugins using the X11 renderer.
    - Add --tty option to plymouthd for debugging when X is running and
      thus using an alternate VT.

    - Improve deactivate command so that the terminal is no longer watched
      for keyboard input, session is closed, etc. LP: #528787, #531650.
    - Ignore mode changes while deactivated, otherwise we can end up
      resetting the VT back into text mode while X is starting up.
      LP: #523788, #502509.

    - Fix races with simultaneous quit and deactivate commands, or multiples
      of those commands.
    - Ignore --show-splash, --hide-splash, etc. commands while deactivated.
    - Add reactivate command for testing purposes.

    - Don't scan out drm buffer contents to fbcon when not called with
      quit --retain-splash. LP: #527180.

    - Avoid resetting the terminal to unbuffered mode on every write, this
      results in setting X's VT into raw mode and results in the X server
      crashing on key presses. LP: #532047, #534861, #519460, #520...

Read more...

Changed in plymouth (Ubuntu):
status: New → 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.