Timezone changes are not working due to ro /etc and bind mounts
Bug #1227520 reported by
Gema Gomez
This bug affects 9 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
android (Ubuntu) |
Fix Released
|
Undecided
|
Oliver Grawert | ||
apparmor (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
initramfs-tools-ubuntu-touch (Ubuntu) |
Fix Released
|
Undecided
|
Stéphane Graber | ||
livecd-rootfs (Ubuntu) |
Fix Released
|
Undecided
|
Martin Pitt | ||
lxc-android-config (Ubuntu) |
Fix Released
|
Undecided
|
Martin Pitt | ||
systemd (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
ubuntu-system-settings (Ubuntu) |
Invalid
|
High
|
Iain Lane |
Bug Description
There is no way to set up a different timezone than automatic in the System Settings
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: ubuntu-
Uname: Linux 3.4.0-3-mako armv7l
ApportVersion: 2.12.2-0ubuntu1
Architecture: armhf
Date: Thu Sep 19 08:41:07 2013
InstallationDate: Installed on 2013-09-18 (0 days ago)
InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20130918)
MarkForUpload: True
ProcEnviron:
TERM=linux
PATH=(custom, no user)
SourcePackage: ubuntu-
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | added: jfunk |
Changed in ubuntu-system-settings (Ubuntu): | |
importance: | Undecided → High |
Changed in systemd (Ubuntu): | |
importance: | Undecided → High |
status: | New → Confirmed |
summary: |
- Timezone cannot be selected on system settings app + Timezone changes are not working due to ro /etc and bind mounts |
Changed in systemd (Ubuntu): | |
status: | Incomplete → Triaged |
Changed in lxc-android-config (Ubuntu): | |
status: | New → Triaged |
Changed in livecd-rootfs (Ubuntu): | |
status: | New → In Progress |
assignee: | nobody → Martin Pitt (pitti) |
Changed in systemd (Ubuntu): | |
milestone: | none → ubuntu-13.09 |
tags: | added: patch |
Changed in android (Ubuntu): | |
status: | New → Fix Released |
assignee: | nobody → Oliver Grawert (ogra) |
To post a comment you must log in.
Status changed to 'Confirmed' because the bug affects multiple users.