Bug #8124
Scary failure messages when shutting down the system while the Unsafe Browser is still running
Start date:
2014-10-15
Due date:
% Done:
100%
Description
I guess we should forcefully run the Unsafe Browser teardown code at shutdown time, if we don’t find anything more clever.
Subtasks
Related issues
Related to Tails - |
Resolved | 2014-07-19 | |
Related to Tails - |
Rejected | 2013-12-02 |
History
#1 Updated by BitingBird 2015-02-23 05:34:10
- related to
Feature #5417: Improve user experience when wiping memory at shutdown added
#2 Updated by BitingBird 2015-02-23 05:34:42
- related to
Feature #6463: Make shutdown faster by keeping even more services running added
#3 Updated by intrigeri 2017-05-18 09:16:12
- Status changed from Confirmed to In Progress
- Assignee set to anonym
- Target version set to Tails_3.0~rc1
- % Done changed from 0 to 50
- QA Check set to Ready for QA
- Feature Branch set to bugfix/12354-drop-kexec-memory-wipe
On my branch for Bug #12354 I’ve tried two scenarios:
- starting the Unsafe Browser then clicking the shutdown button (in the GNOME Shell top-right menu)
- starting the Unsafe Browser then unplugging the boot device
In both cases the machine shuts down within a few seconds, and I had no time to see any scary failure message.
#4 Updated by anonym 2017-05-18 14:58:17
- Assignee changed from anonym to intrigeri
- % Done changed from 50 to 100
- QA Check changed from Ready for QA to Pass
I temporarily altered all the emergency_shutdown.feature
scenarios to start the Unsafe Browser, and I saw nothing strange.
See Bug #12354 for the review (no blockers found). Please close when you merge!
#5 Updated by intrigeri 2017-05-18 15:38:44
- Status changed from In Progress to Fix committed
- Assignee deleted (
intrigeri)
#6 Updated by intrigeri 2017-05-23 09:04:05
- Status changed from Fix committed to Resolved