casper caching for shutdown is broken

Bug #1436656 reported by Mathieu Trudel-Lapierre on 2015-03-26
This bug affects 1 person
Affects Status Importance Assigned to Milestone
casper (Ubuntu)

Bug Description

The caching code appears to be broken, and currently does not take into account the fact that plymouth was split into separate plugins.

The shutdown sequence under systemd might jigger this just enough to make it work by accident, but syncing the cache list with what gets copied in /usr/share/initramfs-tools/hooks/plymouth would probably help a lot.

Related branches

Changed in casper (Ubuntu):
status: New → Triaged
importance: Undecided → Medium

I guess this could also be considered bitesize too if someone wants to tackle this before I (or someone else who usually looks after casper) looks into it. There is a bit of information on the bug here, but anyone wanting to work on this should feel free to ask for more information if necessary.

tags: added: bitesize
tags: added: vivid
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package casper - 1.359

casper (1.359) vivid; urgency=medium

  * Do a better job at caching files we might need for plymouth and systemd
    on shutdown. (LP: #1436656)
  * debian/casper.service: Order the casper service just before
    so it's running at a better point in time on shutdown.
  * scripts/casper-bottom/25disable_cdrom.mount: mask the cdrom.mount task,
    so it doesn't unncessarily spin trying to unmount the cdrom, which casper
    will do. (LP: #1436715)
 -- Mathieu Trudel-Lapierre <email address hidden> Mon, 13 Apr 2015 14:50:24 -0500

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

Other bug subscribers