[Bug 967229] Re: Text mode shown briefly with various "cryptic" texts when logging out or shutting down

[Dmitrijs Ledkovs]

Ordering of the splash ahead of emitting rc runlevel level has been done
before in Fedora, to properly show shutdown splash to avoid "scary
messages".

I have also noticed that there are additional messages generated on the
VT through the lifecycle of the machine - that is after lightdm cleared
it and shutdown initiated. Therefore I add clearing VT messages before
lightdm shutdowns.

Instead of introducing a dummy intermediate job to negotiate "whether or
not there is a DM to stop", I use the wait-for-state facility and
therefore make the following dependency chain:

starting rc RUNLEVEL=[016] -> waits to start shutdown-plymouth (if any)
-> (stopping plymouth) -> waits to stop lightdm (if any)

This also splits plymouth into two jobs, instead of having duplicate /
ORed start on, exec & post-start scripts. Semantically it also makes
sense, it's two different instances.

This also makes "desktop-shutdown" event redundant.

To try this out:
cd /etc/init; sudo patch -p0 < path/to/patch

I have tested it on trusty and have a message-less shutdown. The patch
can equally be applied on precise, please test it on the affected
precise machines / OEM devices.

** Patch added: "message-less-shutdown.patch"
   https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/967229/+attachment/3924322/+files/message-less-shutdown.patch

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/967229

Title:
  Text mode shown briefly with various "cryptic" texts when logging out
  or shutting down

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project precise series:
  Triaged
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “plymouth” package in Ubuntu:
  Triaged

Bug description:
  Text mode hits in for about a half a second every time one logs out or
  shuts down the computer. UPDATE: log out part fixed in lightdm in
  Ubuntu 13.04 ->, shut down problem still there.

  The attached video "Text-mode in logout and shutdown.webm" is a
  combination of two clips showing this on one of my computers. This one
  has slightly more text output than my other machines, but on every
  machine it catches attention by being ugly and I'd guess "cryptic" or
  suspicious for ordinary people in the otherwise smooth experience
  starting from the bootup ubuntu logo.

  Tested on up-to-date Ubuntu 12.04 on an Intel IGD graphics netbook,
  Intel Sandy Bridge laptop and Radeon HD 4670 (open drivers) desktop
  machine. The video is from the sandy bridge one.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Wed Mar 28 18:25:44 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120316)
  MachineType: ASUSTeK Computer Inc. UX31E
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=3a913d68-5aad-4ac9-9436-4798da5b8fc2 ro crashkernel=384M-2G:64M,2G-:128M quiet splash drm.vblankoffdelay=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1 pcie_aspm=force vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX31E.211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX31E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX31E.211:bd01/20/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: UX31E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.7.2-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/967229/+subscriptions