Feature #10064
Warn when persistent volume is getting full
0%
Description
GNOME has a notification mechanism for when internal hard disks get full. See https://search.disconnect.me/image?l=aHR0cHM6Ly9lbmNyeXB0ZWQtdGJuMC5nc3RhdGljLmNvbS9pbWFnZXM/cT10Ym46QU5kOUdjUjdDMVE4ZkVvMHlyRnhBcGQwWUFscDBFRmhScVc2WXV0bjNNTU81RldWampXRnZuMTBPUQ==.
But this mechanism doesn’t work in Tails for the persistent volume. I think it should :)
How can we do that?
Subtasks
Related issues
|
Related to Tails - |
Rejected | 2015-07-07 | |
|
Related to Tails - |
Confirmed | 2015-08-18 | |
| Related to Tails - Feature #6254: Make it easy to empty Trash on persistent volume | Confirmed | 2013-09-03 | |
| Related to Tails - Feature #14544: Spend software developer time on smallish UX improvements | In Progress | 2018-08-31 | |
|
Related to Tails - |
Confirmed | 2015-08-18 | |
|
Has duplicate Tails - |
Duplicate | 2016-10-05 | |
| Blocks Tails - Feature #7782: Warn the user when available RAM / memory is low | Confirmed | 2014-08-14 |
History
#1 Updated by sajolida 2015-08-20 00:33:30
- Tracker changed from Bug to Feature
#2 Updated by intrigeri 2015-08-25 00:38:19
- Category set to Persistence
#3 Updated by intrigeri 2016-10-05 15:09:12
- has duplicate
Bug #11863: Warn when the persistence is getting full added
#4 Updated by intrigeri 2016-10-05 15:10:04
- related to
Feature #9699: Show the available space on the persistence volume. added
#5 Updated by sajolida 2016-10-06 17:58:41
- related to
Feature #10060: Warn when the in-memory filesystem is getting full added
#6 Updated by Anonymous 2018-08-18 10:33:34
- Type of work changed from Code to Research
- Starter set to Yes
It would be nice to figure out why the default GNOME mechanism does not work for us. Making this a research ticket for now.
#7 Updated by intrigeri 2018-08-18 10:51:32
u wrote:
> It would be nice to figure out why the default GNOME mechanism does not work for us. Making this a research ticket for now.
I suspect that’s because the relevant part of the GNOME stack monitors only certain types of devices, whose set probably does not include the crazy mountpoints our persistence sets up. I bet segfault is able to easily add a pointer to the corresponding piece of GNOME code :)
#8 Updated by intrigeri 2018-08-18 10:51:55
- related to Feature #6254: Make it easy to empty Trash on persistent volume added
#9 Updated by Anonymous 2018-08-18 12:11:25
- Assignee set to segfault
@segfault, would you like to look into this at some point?
#10 Updated by sajolida 2018-08-21 15:41:35
- related to Feature #14544: Spend software developer time on smallish UX improvements added
#11 Updated by segfault 2018-08-24 17:37:17
intrigeri wrote:
> u wrote:
> > It would be nice to figure out why the default GNOME mechanism does not work for us. Making this a research ticket for now.
>
> I suspect that’s because the relevant part of the GNOME stack monitors only certain types of devices, whose set probably does not include the crazy mountpoints our persistence sets up. I bet segfault is able to easily add a pointer to the corresponding piece of GNOME code :)
I think this is the code, but I couldn’t yet identify which of the checks (if any) filters out the persistence partition.
#12 Updated by sajolida 2019-01-18 16:20:25
- related to
Feature #10060: Warn when the in-memory filesystem is getting full added
#13 Updated by intrigeri 2019-01-23 11:40:41
We probably get this for free if we do Feature #6254 but we could also implement a ad-hoc home-made notification system for this one.
#14 Updated by intrigeri 2019-01-23 13:11:53
- blocks Feature #7782: Warn the user when available RAM / memory is low added
#15 Updated by segfault 2019-05-11 23:38:29
- Assignee deleted (
segfault)
I’m not currently working on this, so I’m unassigning myself in order to allow others to take it. If no one else does, I might come back to it when I work on Feature #14544 tickets.