casper caching for shutdown is broken
Bug #1436656 reported by
Mathieu Trudel-Lapierre
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| casper (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
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/
Related branches
lp:~cyphermox/casper/shutdown
- Ubuntu branches: Pending requested
-
Diff: 102 lines (+34/-6)5 files modifiedbin/casper-stop (+6/-4)
debian/casper.service (+3/-2)
debian/changelog (+19/-0)
scripts/casper-bottom/25disable_cdrom.mount (+3/-0)
scripts/casper-bottom/34disable_kde_services (+3/-0)
| Changed in casper (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Mathieu Trudel-Lapierre (cyphermox) wrote | #1 |
| tags: | added: bitesize |
| tags: | added: vivid |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in casper (Ubuntu): | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
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.