[Bug 577331] Re: fsck cannot be ignored with plymouth

Ubuntu QA's Bug Bot bug-stats at murraytwins.com
Mon Sep 19 21:19:18 UTC 2011


** Tags added: testcase

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

Title:
  fsck cannot be ignored with plymouth

Status in “mountall” package in Ubuntu:
  Fix Released
Status in “mountall” source package in Lucid:
  Fix Released
Status in “mountall” source package in Maverick:
  Fix Released

Bug description:
  Binary package hint: plymouth

  PROBLEM

  There seems to be no way to skip an fsck with plymouth.

  TEST CASE

  1. sudo touch /forcefsck && sudo reboot

  2. While fsck is in progress, press c

  3. press i for ignore

  * Plymouth locks up and reboot is required

  OBSERVATIONS

  Currently, and in my case, to be able to get to the cancel screen at all, c must be pressed almost immediately as plymouth splash is initiated, due to Bug #571707 which makes plymouth stall otherwise.
  If using the patched packages available for said bug, it seems to be possible to cancel at any point during the fsck (there is still a considerable delay between the keypress and the cancel screen though), but the issue in this bug remains.

  Message when c is pressed says "Serious error was encounterd";
  cancelling an fsck does not inherently cause errors, does it? This is a case of very bad wording to me.

  Trying to skip mounting (pressing s) after cancelling fsck locks up
  plymouth with the message "waiting for /tmp" Is this the right way to
  handle this? Should the option to skip mounting the root filesystem
  even exist? (Now Bug #578184)

  Dropping to maintenance shell with m works as expected, but only if
  plymouth hasn't already locked up by any of the other options

  ---

  Architecture: i386
  CurrentDmesg:
   [   77.543932] vboxdrv: exports duplicate symbol RTMemExecFree (owned by vboxguest)
   [   78.010602] vboxvfs: Successfully loaded version 3.1.6_OSE (interface 0x00010004)
   [   85.195014] end_request: I/O error, dev fd0, sector 0
   [   85.308195] end_request: I/O error, dev fd0, sector 0
   [   85.668090] eth1: no IPv6 routers present
  DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091209)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: innotek GmbH VirtualBox
  Package: plymouth 0.8.2-2ubuntu2
  PackageArchitecture: i386
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=c3804ba1-72aa-4d8c-88c3-1bb81f2619f6 ro quiet splash
  ProcEnviron:
   LANG=en_GB.utf8
   SHELL=/bin/bash
  ProcFB: 0 VGA16 VGA
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Tags: lucid
  TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Uname: Linux 2.6.32-22-generic i686
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/577331/+subscriptions




More information about the foundations-bugs mailing list