It's disabled

H

HikariKnight•12/30/23, 9:47 PM

sudo systemctl enable --now systemd-timesyncd.service

sudo systemctl enable --now systemd-timesyncd.service

sudo systemctl enable --now systemd-timesyncd.service

sudo systemctl enable --now systemd-timesyncd.service
it will enable syncing of the time with an ntp server so it will grab the time online

H

heriOP•12/30/23, 9:48 PM

ok

H

HikariKnight•12/30/23, 9:48 PM

should fix your wrong time and also should hopefully fix the ssl issue with discord flatpak

H

heriOP•12/30/23, 9:55 PM

Do I need to reboot for it to apply properly?

H

HikariKnight•12/30/23, 9:56 PM

should sync immediately, but you can reboot to be sure

H

HikariKnight•12/30/23, 9:56 PM

you can check with the status command again

H

HikariKnight•12/30/23, 9:56 PM

HHikariKnight you can check with the status command again

H

heriOP•12/30/23, 9:56 PM

It says it's running but discord still fails to run

H

heriOP•12/30/23, 9:57 PM

Same cert errors

H

HikariKnight•12/30/23, 9:57 PM

what does it say on the status line for systemd-timesyncd

HHikariKnight what does it say on the status line for systemd-timesyncd

H

heriOP•12/30/23, 9:57 PM

Fym

H

HikariKnight•12/30/23, 9:57 PM

fym?

Hheri It says it's running but discord still fails to run

H

heriOP•12/30/23, 9:58 PM

Like I said, The status command says it's active and running

H

HikariKnight•12/30/23, 9:58 PM

H

HikariKnight•12/30/23, 9:58 PM

this line

H

HikariKnight•12/30/23, 9:59 PM

and the actual log part

HHikariKnight Click to see attachment

H

heriOP•12/30/23, 10:01 PM

Ah, it says it's contacted 0.fedora.pool.ntp.org

H

HikariKnight•12/30/23, 10:01 PM

ok and what does the log say?

HHikariKnight ok and what does the log say?

H

heriOP•12/30/23, 10:02 PM

heri@floof ~> systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Sat 2023-12-30 16:47:59 EST; 10min ago
       Docs: man:systemd-timesyncd.service(8)
   Main PID: 16682 (systemd-timesyn)
     Status: "Contacted time server 108.61.73.244:123 (0.fedora.pool.ntp.org)."
      Tasks: 2 (limit: 11699)
     Memory: 1.4M
        CPU: 66ms
     CGroup: /system.slice/systemd-timesyncd.service
             └─16682 /usr/lib/systemd/systemd-timesyncd

Dec 30 16:47:59 floof systemd[1]: Starting systemd-timesyncd.service - Network Time Synchronization...
Dec 30 16:47:59 floof systemd[1]: Started systemd-timesyncd.service - Network Time Synchronization.
Dec 30 16:48:00 floof systemd-timesyncd[16682]: Contacted time server 108.61.73.244:123 (0.fedora.pool.ntp.org).
Dec 30 16:48:00 floof systemd-timesyncd[16682]: Initial clock synchronization to Sat 2023-12-30 16:48:00.002305 EST.

heri@floof ~> systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Sat 2023-12-30 16:47:59 EST; 10min ago
       Docs: man:systemd-timesyncd.service(8)
   Main PID: 16682 (systemd-timesyn)
     Status: "Contacted time server 108.61.73.244:123 (0.fedora.pool.ntp.org)."
      Tasks: 2 (limit: 11699)
     Memory: 1.4M
        CPU: 66ms
     CGroup: /system.slice/systemd-timesyncd.service
             └─16682 /usr/lib/systemd/systemd-timesyncd

Dec 30 16:47:59 floof systemd[1]: Starting systemd-timesyncd.service - Network Time Synchronization...
Dec 30 16:47:59 floof systemd[1]: Started systemd-timesyncd.service - Network Time Synchronization.
Dec 30 16:48:00 floof systemd-timesyncd[16682]: Contacted time server 108.61.73.244:123 (0.fedora.pool.ntp.org).
Dec 30 16:48:00 floof systemd-timesyncd[16682]: Initial clock synchronization to Sat 2023-12-30 16:48:00.002305 EST.

heri@floof ~> systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Sat 2023-12-30 16:47:59 EST; 10min ago
       Docs: man:systemd-timesyncd.service(8)
   Main PID: 16682 (systemd-timesyn)
     Status: "Contacted time server 108.61.73.244:123 (0.fedora.pool.ntp.org)."
      Tasks: 2 (limit: 11699)
     Memory: 1.4M
        CPU: 66ms
     CGroup: /system.slice/systemd-timesyncd.service
             └─16682 /usr/lib/systemd/systemd-timesyncd

Dec 30 16:47:59 floof systemd[1]: Starting systemd-timesyncd.service - Network Time Synchronization...
Dec 30 16:47:59 floof systemd[1]: Started systemd-timesyncd.service - Network Time Synchronization.
Dec 30 16:48:00 floof systemd-timesyncd[16682]: Contacted time server 108.61.73.244:123 (0.fedora.pool.ntp.org).
Dec 30 16:48:00 floof systemd-timesyncd[16682]: Initial clock synchronization to Sat 2023-12-30 16:48:00.002305 EST.

heri@floof ~> systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Sat 2023-12-30 16:47:59 EST; 10min ago
       Docs: man:systemd-timesyncd.service(8)
   Main PID: 16682 (systemd-timesyn)
     Status: "Contacted time server 108.61.73.244:123 (0.fedora.pool.ntp.org)."
      Tasks: 2 (limit: 11699)
     Memory: 1.4M
        CPU: 66ms
     CGroup: /system.slice/systemd-timesyncd.service
             └─16682 /usr/lib/systemd/systemd-timesyncd

Dec 30 16:47:59 floof systemd[1]: Starting systemd-timesyncd.service - Network Time Synchronization...
Dec 30 16:47:59 floof systemd[1]: Started systemd-timesyncd.service - Network Time Synchronization.
Dec 30 16:48:00 floof systemd-timesyncd[16682]: Contacted time server 108.61.73.244:123 (0.fedora.pool.ntp.org).
Dec 30 16:48:00 floof systemd-timesyncd[16682]: Initial clock synchronization to Sat 2023-12-30 16:48:00.002305 EST.

H

HikariKnight•12/30/23, 10:03 PM

yeah so it should have set the time for you then

H

HikariKnight•12/30/23, 10:03 PM

is the time still wrong when running discord?

H

HikariKnight•12/30/23, 10:03 PM

as in the log output

H

heriOP•12/30/23, 10:04 PM

Yep

HHikariKnight is the time still wrong when running discord?

H

heriOP•12/30/23, 10:04 PM

blackbox: 2023-12-30T22:04:22.333Z 6 ✅ window.created win2 "Discord"
[63:1230/170422.432276:ERROR:ssl_client_socket_impl.cc(982)] handshake failed; returned -1, SSL error code 1, net_error -202
blackbox: 2023-12-30T22:04:22.574Z 7 ❌ webContents.did-fail-provisional-load web2: -202 ERR_CERT_AUTHORITY_INVALID
[WebContents] did-fail-load -202 ERR_CERT_AUTHORITY_INVALID retry in 1000 ms
(node:5) electron: Failed to load URL: https://discord.com/app?_=1703973862259 with error: ERR_CERT_AUTHORITY_INVALID
(Use `Discord --trace-warnings ...` to show where the warning was created)
blackbox: 2023-12-30T22:04:22.579Z 8 ❌ webContents.did-fail-load web2" -202 ERR_CERT_AUTHORITY_INVALID

blackbox: 2023-12-30T22:04:22.333Z 6 ✅ window.created win2 "Discord"
[63:1230/170422.432276:ERROR:ssl_client_socket_impl.cc(982)] handshake failed; returned -1, SSL error code 1, net_error -202
blackbox: 2023-12-30T22:04:22.574Z 7 ❌ webContents.did-fail-provisional-load web2: -202 ERR_CERT_AUTHORITY_INVALID
[WebContents] did-fail-load -202 ERR_CERT_AUTHORITY_INVALID retry in 1000 ms
(node:5) electron: Failed to load URL: https://discord.com/app?_=1703973862259 with error: ERR_CERT_AUTHORITY_INVALID
(Use `Discord --trace-warnings ...` to show where the warning was created)
blackbox: 2023-12-30T22:04:22.579Z 8 ❌ webContents.did-fail-load web2" -202 ERR_CERT_AUTHORITY_INVALID

blackbox: 2023-12-30T22:04:22.333Z 6 ✅ window.created win2 "Discord"
[63:1230/170422.432276:ERROR:ssl_client_socket_impl.cc(982)] handshake failed; returned -1, SSL error code 1, net_error -202
blackbox: 2023-12-30T22:04:22.574Z 7 ❌ webContents.did-fail-provisional-load web2: -202 ERR_CERT_AUTHORITY_INVALID
[WebContents] did-fail-load -202 ERR_CERT_AUTHORITY_INVALID retry in 1000 ms
(node:5) electron: Failed to load URL: https://discord.com/app?_=1703973862259 with error: ERR_CERT_AUTHORITY_INVALID
(Use `Discord --trace-warnings ...` to show where the warning was created)
blackbox: 2023-12-30T22:04:22.579Z 8 ❌ webContents.did-fail-load web2" -202 ERR_CERT_AUTHORITY_INVALID

blackbox: 2023-12-30T22:04:22.333Z 6 ✅ window.created win2 "Discord"
[63:1230/170422.432276:ERROR:ssl_client_socket_impl.cc(982)] handshake failed; returned -1, SSL error code 1, net_error -202
blackbox: 2023-12-30T22:04:22.574Z 7 ❌ webContents.did-fail-provisional-load web2: -202 ERR_CERT_AUTHORITY_INVALID
[WebContents] did-fail-load -202 ERR_CERT_AUTHORITY_INVALID retry in 1000 ms
(node:5) electron: Failed to load URL: https://discord.com/app?_=1703973862259 with error: ERR_CERT_AUTHORITY_INVALID
(Use `Discord --trace-warnings ...` to show where the warning was created)
blackbox: 2023-12-30T22:04:22.579Z 8 ❌ webContents.did-fail-load web2" -202 ERR_CERT_AUTHORITY_INVALID

H

HikariKnight•12/30/23, 10:05 PM

hmm then i am not sure how else to fix it

H

heriOP•12/30/23, 10:05 PM

hopefully someone can chime in

H

heriOP•12/30/23, 10:05 PM

this is very weird

H

heriOP•12/30/23, 10:06 PM

i tried stock, canary, armcord, webcord, vencord. none of them work and all give the same error......but the website inside firefox works

H

HikariKnight•12/30/23, 10:06 PM

it is weird, discord app doesnt work in flatpak on my work laptop either, but thats a separate issue as the log says nothing about anything being wrong, so i use armcord on that one

H

HikariKnight•12/30/23, 10:06 PM

only that pc that has the issue

H

heriOP•12/30/23, 10:06 PM

not even armcord works for me tho

H

HikariKnight•12/30/23, 10:06 PM

hmm

H

HikariKnight•12/30/23, 10:07 PM

does the discord website client work fine then?

H

heriOP•12/30/23, 10:08 PM

just the website, but yes

H

heriOP•12/30/23, 10:08 PM

and though, not webcord. which is the weirdest part

H

HikariKnight•12/30/23, 10:08 PM

https://tenor.com/view/oh-god-need-tomboy-not-like-this-torment-gif-14128414539717779752

Tenor

H

HikariKnight•12/30/23, 10:08 PM

me right now trying to think wth is causing that for you

H

HikariKnight•12/30/23, 10:10 PM

hopefully someone else has an idea. at least you have time sync enabled now at least

J

j0rge•12/30/23, 10:12 PM

what else is on the system?

J

j0rge•12/30/23, 10:12 PM

do you have nix or brew installed?

Hheri i have 200gb, half of it being HALO lol

B

Bartley•12/30/23, 10:17 PM

https://tenor.com/view/halo-emile-halo-reach-gif-21006491

Tenor

Vvertigo.red `nvidia-compute-utils-G06-545.29.06-18.1.x86_64` And repo if matters: https://do...

V

vertigo.red•12/30/23, 10:45 PM

From openSUSE machine.

BBartley https://tenor.com/view/halo-emile-halo-reach-gif-21006491

H

heriOP•12/30/23, 10:53 PM

God I love halo

HHikariKnight me right now trying to think wth is causing that for you

H

heriOP•12/30/23, 10:53 PM

Haha same

Jj0rge do you have nix or brew installed?

H

heriOP•12/30/23, 10:53 PM

Yes both

J

j0rge•12/30/23, 10:53 PM

check to see if you have a tls library or something in your path

H

heriOP•12/30/23, 10:53 PM

How would I do that

J

j0rge•12/30/23, 10:54 PM

I'd remove both of them from your path temporarily and then try to launch discord

H

heriOP•12/30/23, 10:54 PM

Again, how would I do that.

J

j0rge•12/30/23, 10:57 PM

go into your .bashrc or wherever you put it and edit it out. pastebin it somewhere

Similar Threads

Similar Threads

Similar Threads