search

blue-systems / neon-pinebook-remix

Todos for Neon Pinebook Remix
3 stars 0 forks source link

datetime: ff: seems some https issue due to too long ago date #89

Closed star-buck closed 5 years ago

star-buck commented 5 years ago

screenshot_20180128_171623

bhush9 commented 5 years ago

This looks like is due to date configuration being wrong?

bhush9 commented 5 years ago

for record,

14:49 <bshah> well this time bug fix is breaking working clock for me :/ my hardware RTC clock is set to correct time, I add service which sets the time to build timestamp, at boot, time is updated from time server, after that service triggers setting time in past
14:49 <bshah> which is completely broken behavior
14:49 <bshah> and also for some reason, after setting time to correct time "once" timesyncd never catces up

I am investigating more.

bhush9 commented 5 years ago

Found issue. Trying potential fix locally.

bhush9 commented 5 years ago

The issue we thought was missing libnss-systemd which was removed to fix the #77 but it doesn't seem to have helped with the problem.

star-buck commented 5 years ago

Yeah, its still 1:30-2 minutes before live boots up here.

bhush9 commented 5 years ago

Um no, That delay bug is already fixed

it takes roughly 1:30-2 minutes to boot sure, but not 1:30-2 minutes of blocking (and total of 4 minutes of boot time), what I meant was fix for the delay bug might have caused this bug of time, but that was not cause.

star-buck commented 5 years ago

i think it is 1:30-2min of blocked boot time, right after the neon logo disappears

then it takes that time before cursor shows up and the splash comes... then it takes again some 1:00min to boot from splash into full desktop appears

will test with next new flashed img and stopwatch time in new ticket.

bhush9 commented 5 years ago

So I have image which supposedly should fix wrong date and time,

Testing done

In general there is something still wrong but I am out of time unfortunately today and tomorrow is travel time., so this will have to wait till Akademy or after Akademy. If anyone have free time and wants to figure this out, help would be appreciated.

adriaandegroot commented 5 years ago
  • Connect internet
  • Load github.com, which loads fine.

This will fail when the certificate start date is in the future -- that's a problem I have fairly regularly in VMs which have been suspended for a while and where sync-to-host-clock is disabled (e.g. whatever a default Manjaro install does). For instance, when I set the date (manually) to january 28th and try github from my local VM, I get a "not secure" notice from FF, telling me the date on my computer is probably wrong.

bhush9 commented 5 years ago

Okay finally I figured out what was issue with build_stamp workaround, I was using timedatectl, but since timesyncd is not started at that point, it will fail/hang forever. I have fixed it to use the traditional date command.

https://files.kde.org/neon/images/pinebook-remix-nonfree/useredition/20180808-1033/

Testing done:

Boot delay

I checked this with timer, and it seems that the delay was due to wrong time only, now fixing it i get desktop in 1 minute 21 seconds.. Which is quite reasonable.

davidedmundson commented 5 years ago

I tried with one MicroSD card and had a failed boot. This card was weirdly hot after writing it, so probably doesn't count but worth mentioning.

Next boot with a new card and a different usb writer: Boot took 1 minute 41 Timestamp on boot was 8th August 11am After connecting to the internet NTP did not update immediately NTP did update after a few minutes.

star-buck commented 5 years ago

is this satisfyingly fixed to not block RC release?

star-buck commented 5 years ago

closing for now