To gripped: after reading about hwclock, investigating, messing around (rm'ing /etc/adjtime, recreating...) i left the HW clock in UTC mode (i thought). But just now, i get this:
~$ sudo hwclock --verbose
hwclock from util-linux 2.38.1
System Time: 1679312428.911494
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Last drift adjustment done at 1678922230 seconds after 1969
Last calibration done at 1678922230 seconds after 1969
Hardware clock is on local time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2023/03/20 11:40:29
Hw clock time : 2023/03/20 11:40:29 = 1679334029 seconds since 1969
Time since last adjustment is 411799 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2023-03-20 11:40:28.911255-06:00
~$
After deleting /etc/adjtime:
~$ sudo hwclock --verbose
hwclock from util-linux 2.38.1
System Time: 1679315128.619317
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2023/03/20 12:25:29
Hw clock time : 2023/03/20 12:25:29 = 1679315129 seconds since 1969
Time since last adjustment is 1679315129 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2023-03-20 06:25:28.621131-06:00
~$
I then put back /etc/adjtime, except changing LOCALTIME => UTC:
~$ cat /etc/adjtime
0.000000 1678922230 0.000000
1678922230
UTC
~$
~$ sudo hwclock --verbose
hwclock from util-linux 2.38.1
System Time: 1679315579.712009
Trying to open: /dev/rtc0
Using the rtc interface to the clock.
Last drift adjustment done at 1678922230 seconds after 1969
Last calibration done at 1678922230 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2023/03/20 12:33:00
Hw clock time : 2023/03/20 12:33:00 = 1679315580 seconds since 1969
Time since last adjustment is 393350 seconds
Calculated Hardware Clock drift is 0.000000 seconds
2023-03-20 06:32:59.710228-06:00
~$
I've gone back and forth editing this because i didn't realize that hwclock reports the time differently when you specify --verbose. Normally, it always reports the localtime. But verbose appears to report the unadjusted time. So, i ran the first hwclock, above at about 5:40am local time, the others around 6:30am. The clocks appear to be in perfect sync, as far as i can tell.
So, to clarify (?):
~$ date; sudo hwclock
Mon Mar 20 07:23:29 AM MDT 2023
2023-03-20 07:23:29.444075-06:00
~$
I created a new user, after trying as root, and get the same result both ways:
~# mpv http://s1.voscast.com:8054/
(+) Audio --aid=1 (mp3 2ch 44100Hz)
[ao/pipewire] Could not connect to context '(null)': Host is down
[ao/alsa] Playback open error: Host is down
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
[ao/jack] cannot open server
[ao] Failed to initialize audio driver 'jack'
Could not open/initialize audio device -> no sound.
Audio: no audio
Exiting... (Errors when loading file)
~#
I haven't done that before, so i'm not sure why there's no audio. My normal audio situation is that i'm running pipewire, et al, as my normal (craig) user:
~$ show wire
craig 1146 1106 0 Mar19 ? 00:00:00 /usr/bin/bash -c pipewire & pipewire-pulse & wireplumber
craig 1149 1146 0 Mar19 ? 00:04:09 pipewire
craig 1150 1146 0 Mar19 ? 00:02:10 pipewire-pulse
craig 1151 1146 0 Mar19 ? 00:00:01 wireplumber
~$
So maybe that's a problem? Just as one thing to try, i added the new user (test) to the audio group, but no diff.
To hitman... there's nothing "normal" about the current behavior i'm seeing. As i said, on my other laptop, with the exact same versions of mpv, libavutil, libavcodec, libavformat, libswscale, libavfilter, libswresample and ffmpeg installed it plays fine (stream starts at 0:00). Also, video playback in falkon & firefox is not even remotely "normal". Normally, videos play fine most of the time. Now, as i said, falkon plays the audio, but the time display does not advance and the video is mostly frozen. In firefox, nothing plays at all. All these problems began, recently, at the same time. In falkon, with the video "playing", when i click on the time bar, the time display updates to the corresponding time, and the video updates to that frame, the sound plays from that point, but neither the video (frame) nor the time counter change from that point. I am *so* mystified.
Topic: [SOLVED] Weirdest Pipewire problem (Read 1601 times)
previous topic - next topic