Feature #12094
Persistence preset: localized timezone for displayed time
0%
Description
I reboot TAILS (2.9.1) often and I find it a hassle to reset the timezone myself (on the GUI) each time. On the other hand, if I don’t reset it, I find it disorienting to work with a time on the screen that’s not my local time (like if someone asks me what time it is I have to calculate that in my head).
I know if my timezone is added to the persistence it’s just one more thing an adversary could hack, but if someone did hack my system my timezone isn’t going to worry me much: it’s much more functional for me to have a clock accurate to my timezone to work under.
I think other users may feel the same.
Subtasks
Related issues
Related to Tails - Feature #5774: Robust time syncing | In Progress | 2015-05-17 | |
Related to Tails - Feature #10434: Document differences between displayed time zone and time zone reported by programs | Confirmed | 2015-10-27 | |
Blocked by Tails - |
Duplicate | 2015-12-31 | |
Blocked by Tails - Feature #6284: Display time in local timezone | Confirmed | 2015-10-27 |
History
#1 Updated by intrigeri 2016-12-29 08:25:14
- blocked by Feature #6284: Display time in local timezone added
#2 Updated by intrigeri 2016-12-29 08:25:37
- blocked by
Feature #10819: Allow changing timezone in session added
#3 Updated by intrigeri 2016-12-29 08:29:02
- Subject changed from Make TimeZone part of persistence to Allow persisting localized timezone for displayed time
- Category set to Persistence
- Status changed from New to Confirmed
First of all, changing the timezone of a Tails system is dangerous, so we have no plans to support that. However, we do have plans (Feature #6284, Feature #12069) to allow changing the timezone for the date/time that’s displayed in the GNOME Desktop, without affecting the internal, system timezone. Also see Feature #5774 for a more iterative implementation plan.
And then, once we allow changing that displayed timezone, indeed we should enable users to persist this preference of theirs, just like other localization settings.
#4 Updated by intrigeri 2016-12-29 08:29:16
- related to Feature #5774: Robust time syncing added
#5 Updated by Velexx 2016-12-29 12:58:11
Agreed. I had forgotten the internal versus displayed time. —Velexx
intrigeri wrote:
> First of all, changing the timezone of a Tails system is dangerous, so we have no plans to support that. However, we do have plans (Feature #6284, Feature #12069) to allow changing the timezone for the date/time that’s displayed in the GNOME Desktop, without affecting the internal, system timezone. Also see Feature #5774 for a more iterative implementation plan.
>
> And then, once we allow changing that displayed timezone, indeed we should enable users to persist this preference of theirs, just like other localization settings.
#6 Updated by Anonymous 2017-06-29 12:21:19
Once we have Feature #6284, we can consider persisting the time zone.
#7 Updated by Anonymous 2017-06-29 12:23:08
- blocks deleted (
Feature #6284: Display time in local timezone)
#8 Updated by Anonymous 2017-06-29 12:23:22
- blocked by Feature #6284: Display time in local timezone added
#9 Updated by Anonymous 2018-01-17 16:26:10
- related to Feature #10434: Document differences between displayed time zone and time zone reported by programs added
#10 Updated by Anonymous 2018-08-19 06:52:04
- Subject changed from Allow persisting localized timezone for displayed time to Persistence present: localized timezone for displayed time
#11 Updated by intrigeri 2018-08-19 07:58:49
- Subject changed from Persistence present: localized timezone for displayed time to Persistence preset: localized timezone for displayed time