Skip to content
This repository has been archived by the owner on Aug 22, 2024. It is now read-only.

Wrong time #1585

Closed
FlavioMala opened this issue Oct 19, 2020 · 6 comments · Fixed by ubports/systemd-packaging#2
Closed

Wrong time #1585

FlavioMala opened this issue Oct 19, 2020 · 6 comments · Fixed by ubports/systemd-packaging#2
Assignees
@peat-psuwit
Labels
critical (devel)

Comments

@FlavioMala
Copy link

FlavioMala commented Oct 19, 2020 •
edited
Loading

BUG-REPORT

Time

  • Device: bq Aquaris E5 HD
  • Channel: dev
  • Build: "608" 18 oct 2020

Steps to reproduce

The time in the top bar (and in the "circle") is UTC (e.g. 13:35); the time in the settings is UTC+2 (e.g. 15:35) as before upgrade.

In 'settings ' it is "manual", but:
I can change the time, but changes are lost exit from 'settings'.
The same if I set to 'auto' (return to manual) and also is not possible to set a different UTC (test with 'Berlin, Rome, Milan, Genua....')... lost after exit from 'settings'.

Still present with upgrade to "609" and "610".
@Daniel20000522
Copy link

Confirmed on Nexus 5 devel 1756

@FlavioMala
Copy link
Author

FlavioMala commented Oct 20, 2020 •
edited
Loading

Addendum:
If I have got an alarm set at 7:35 (for example), the alarm will sound at 11:35, 4 hours later !!
This while the top bar shows 9:35 (UTC) and the phone time in 'settings' (not editable) shows 11:35 (UTC+2).

In summary:
I need to set an alarm at UTC-2 (e.g. 3:35) to make it sound at a time set on the phone UTC+2 (e.g. 7:35), while the top bar shows UTC (e.g. 5:35)...

@bjm39
Copy link

bjm39 commented Oct 20, 2020

The same on bq Aquaris E4.5

@peat-psuwit peat-psuwit self-assigned this Oct 20, 2020
peat-psuwit added a commit to peat-psuwit/systemd-packaging that referenced this issue Oct 20, 2020
@peat-psuwit
Fix crash if /etc/writable/localtime is not a symlink
bc3342e 
I'm not sure how is it possible, but some devices have /etc/writable/
localtime as a file instead of a symlink. This should trigger Debian's
fallback but 1.) it didn't 2.) it crashes due to double-free.

Thus, we have to move our code up above the Debian fallback again.
Because the Debian fallback doesn't guard the unsuccessful first read
for us, we have to check it ourself. To fix double-free, we'll have to
set the variable we free to NULL again, or the auto-free mechanism will
double-free it if the suppose-to-overwrite call is not successful.

Fixes ubports/ubuntu-touch#1585
@peat-psuwit peat-psuwit mentioned this issue Oct 20, 2020
Merged
dobey pushed a commit to ubports/systemd-packaging that referenced this issue Oct 21, 2020
@peat-psuwit
Fix crash if /etc/writable/localtime is not a symlink (#2)
b9ca931 
I'm not sure how is it possible, but some devices have /etc/writable/
localtime as a file instead of a symlink. This should trigger Debian's
fallback but 1.) it didn't 2.) it crashes due to double-free.

Thus, we have to move our code up above the Debian fallback again.
Because the Debian fallback doesn't guard the unsuccessful first read
for us, we have to check it ourself. To fix double-free, we'll have to
set the variable we free to NULL again, or the auto-free mechanism will
double-free it if the suppose-to-overwrite call is not successful.

Fixes ubports/ubuntu-touch#1585
@TellingBerto
Copy link

Device: VollaPhone
Channel: rc
Build: 2020-W43

Top bar shows 9:46 (UTC+1), the phone time in 'settings' (not editable) shows 9:46 (UTC+1).
If 'settings ' it is set to "manual": Changed time are kept when exiting from 'settings'. Manually changed time remain after reboot.

No problem on Volla.

@FlavioMala
Copy link
Author

I confirm that after upgrade ("612" 22 Oct or "613" 24 Oct, now I do not remember well) the problem is over.
Thanks a lot !

@jezek
Copy link

jezek commented Oct 28, 2020

Device: FP2
OS: 2020-W43

Top bar shows 17:12. In the settings the timezone is UTC+1, time is set to "auomatic" and the non editable time says "... 17:12:55 CET".
When time setting it is set to "manual", changed time (16:12) is kept after settings are closed and remains after reboot.
After switching to "automatic", the time changes back to right value (17:12) after few seconds (internet connection has to be turned on).

@UniversalSuperBox UniversalSuperBox mentioned this issue Oct 29, 2020
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@peat-psuwit peat-psuwit

Labels
critical (devel)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix crash if /etc/writable/localtime is not a symlink peat-psuwit/systemd-packaging
7 participants
@jezek @dobey @peat-psuwit @Daniel20000522 @bjm39 @FlavioMala @TellingBerto