Ubuntu
plymouth package

in /usr/share/initramfs-tools/hooks/plymouth line 53 change /bin/bash to /bin/sh

Bug #715482 reported by dude
38
This bug affects 6 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Fix Released
Undecided
Unassigned
Maverick
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: plymouth

Hello,

I found out that it's not possible to remote login while the system starts although dropbear is installed. The dropbear script creates a passwd file with /bin/sh as shell while the plymouth script overwrites it with /bin/bash.
A /bin/bash file does not exist in my initrd.

Sorry for my english, I hope you get what I mean :-)

Best regards,

dude

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: plymouth 0.8.2-2ubuntu5.1 [modified: usr/share/initramfs-tools/hooks/plymouth]
ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10
Uname: Linux 2.6.35-25-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Feb 8 23:38:20 2011
DefaultPlymouth: /lib/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth
InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: System manufacturer P5Q-PRO
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-25-generic root=/dev/mapper/ubuntu-root ro quiet splash
ProcEnviron:
 LANGUAGE=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB:

SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/kubuntu-text/kubuntu-text.plymouth
dmi.bios.date: 02/23/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2102
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5Q-PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2102:bd02/23/2009:svnSystemmanufacturer:pnP5Q-PRO:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5Q-PRO
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Related branches

lp:ubuntu/natty/plymouth
Revision history for this message
dude (ilduderino) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package plymouth - 0.8.2-2ubuntu14

---------------
plymouth (0.8.2-2ubuntu14) natty; urgency=low

  [ Mathieu Trudel-Lapierre ]
  * Adjust the text plymouth themes to only ship a template, which then gets
    used to generate the actual message from the output of lsb_release.
  * debian/plymouth-theme-kubuntu-text.postinst,
    debian/plymouth-theme-ubuntu-text.postinst:
    - Build on the changes to set the text and colors for the -text themes via
      settings; attempt to properly set the current Ubuntu version according to
      what LSB tells us.
  * debian/plymouth-theme-kubuntu-text.prerm,
    debian/plymouth-theme-ubuntu-text.prerm:
    - Clean up the actual theme config file for ubuntu-text themes since it's
      generated at install time.
  * debian/plymouth-theme-kubuntu-text.postrm,
    debian/plymouth-theme-ubuntu-text.postrm:
    - Don't remove /lib/plymouth and /lib/plymouth/themes, it will be done by
      the plymouth package itself on removal.

  [ Steve Langasek ]
  * Clean up the prerm scripts:
    - don't use this horrible case $1 meme that infests maintainer
      scripts everywhere (including the other scripts in this package :)
    - use rm -f instead of ignoring failures
    - avoid useless exit 0 at the end
  * While we're at it, clean up the other postrm scripts by moving
    update-alternatives calls to new prerms, and clean up the unnecessary
    boilerplate in the remaining postrms.
  * debian/initramfs-tools/hooks/plymouth: don't overwrite /etc/passwd in
    the initramfs if it's already present, since ours is just there as an
    NSS stub and some other hooks may care about the contents. Also, as
    long as we're setting this up, use /bin/sh for the shell instead of
    /bin/bash since that actually exists in the initramfs. LP: #715482
 -- Steve Langasek <email address hidden> Wed, 09 Feb 2011 13:26:13 -0800

Changed in plymouth (Ubuntu):
status: New → Fix Released
Revision history for this message
Matthias Andree (matthias-andree) wrote :

Can this please be backported to all affected (at least maverick is - <https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/733268>) and supported releases? Thanks.

Steve Langasek (vorlon)
Changed in plymouth (Ubuntu Maverick):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Hanno Foest (hurga-launch) wrote :

Actually, there is a second issue with plymouth, even when the shell is fixed remotely unlocking an encrypted root file system is not possible. See https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/595648 for an explanation and possible workaround.

Revision history for this message
Matthias Andree (matthias-andree) wrote : Re: [Bug 715482] Re: in /usr/share/initramfs-tools/hooks/plymouth line 53 change /bin/bash to /bin/sh

Not a big deal, I'm using this script:

exec ssh <email address hidden> \
    -i private-ssh-key \
    -t \
    'export PATH=$PATH:/sbin ; plymouth quit ; sh /scripts/local-top/cryptroot && kill $(pidof cryptroot)'

There may be better versions - but this is a viable workaround. However
the non-installed-shell problem can *NOT* be worked around as dropbear
refuses the login because /bin/bash is an invalid shell.

Revision history for this message
Hanno Stock (hefe_bia) (hanno-stock) wrote :

Also affects Lucid. Please nominate for Lucid!

Adolfo Jayme Barrientos (fitojb)
Changed in plymouth (Ubuntu Maverick):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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