Shadow file appears to have been accessed while my computer was...turned off?

English Applications
#1

I’m not sure if this is making any sense. I was trying to see when /etc/shadow was last accessed, so I tried this and found something odd:

u@localhost:~> ls -lu --time-style=full-iso /etc | grep -i shadow
-rw-r----- 1 root shadow   1098 2023-08-29 02:57:38.316429831 +0800 shadow
-rw-r----- 1 root shadow   1064 2023-05-23 12:20:22.000000000 +0800 shadow-
-rw-r----- 1 root root      837 2022-08-29 02:19:08.006632345 +0800 shadow.YaST2save

The shadow file shows an access time stamp of August 29 at 2:57AM. The problem with that time stamp is (1) I was asleep at that time and (2) so was the computer as it was turned off.

Now I noticed that +0800 thing trailing at the end of the full-iso time stamp, so I thought maybe it’s in UTC and I need to add 8 hours. The resulting time would have made sense because I was already using the computer at the time, except I tried the thing below and confirmed that it’s not a time zone thing:

u@localhost:~> touch test
u@localhost:~> ls -lu --time-style=full-iso . | grep -i test
-rw-r--r-- 1 u u   0 2023-08-29 21:53:28.555156004 +0800 test

That’s while I was writing this post, and 21:53 was the same time I saw on the computer clock when I executed those commands.

Trying to dig deeper, I looked into logs. I picked /var/log/messages randomly and found these:

u@localhost:~> sudo cat /var/log/messages | grep 02:57
[output redacted for brevity]
...
2023-08-29T02:57:37.103685+08:00 localhost systemd[1]: Reached target Network is Online.
2023-08-29T02:57:37.103699+08:00 localhost systemd[1]: Starting Freshclam virus definitions downloader...
2023-08-29T02:57:37.103707+08:00 localhost systemd[1]: Starting Login and scanning of iSCSI devices...
2023-08-29T02:57:37.103715+08:00 localhost systemd[1]: Starting System Logging Service...
2023-08-29T02:57:37.103723+08:00 localhost tlp[1934]: Error: tlp.service is not enabled, power saving will not apply on boot.
2023-08-29T02:57:37.103730+08:00 localhost tlp[1934]: >>> Invoke 'systemctl enable tlp.service' to correct this!
2023-08-29T02:57:37.103738+08:00 localhost iscsiadm[1903]: iscsiadm: No records found
2023-08-29T02:57:37.103753+08:00 localhost iscsiadm[1958]: iscsiadm: No records found
2023-08-29T02:57:37.103764+08:00 localhost iscsiadm[1961]: iscsiadm: Could not get list of targets from firmware. (err 21)
2023-08-29T02:57:37.103772+08:00 localhost systemd[1]: Finished Login and scanning of iSCSI devices.
2023-08-29T02:57:37.103780+08:00 localhost systemd[1]: Reached target Remote File Systems.
2023-08-29T02:57:37.103790+08:00 localhost systemd[1]: Starting Permit User Sessions...
2023-08-29T02:57:37.103798+08:00 localhost tlp[1934]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
2023-08-29T02:57:37.103812+08:00 localhost tlp[1934]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
2023-08-29T02:57:37.103821+08:00 localhost tlp[1934]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
2023-08-29T02:57:37.103829+08:00 localhost tlp[1934]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
2023-08-29T02:57:37.103837+08:00 localhost systemd[1]: Finished Permit User Sessions.
2023-08-29T02:57:37.103844+08:00 localhost systemd[1]: Starting X Display Manager...
2023-08-29T02:57:37.103852+08:00 localhost systemd[1]: Starting Hold until boot process finishes up...
2023-08-29T02:57:37.103866+08:00 localhost display-manager[1990]: /etc/vconsole.conf available
2023-08-29T02:57:37.103875+08:00 localhost display-manager[1990]: KEYMAP: jp106
2023-08-29T02:57:37.103882+08:00 localhost display-manager[1990]: Command: localectl set-keymap jp106
2023-08-29T02:57:37.096883+08:00 localhost rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd.  [v8.2106.0]
2023-08-29T02:57:37.097040+08:00 localhost systemd[1]: Started System Logging Service.
2023-08-29T02:57:37.097135+08:00 localhost rsyslogd: [origin software="rsyslogd" swVersion="8.2106.0" x-pid="1982" x-info="https://www.rsyslog.com"] start
2023-08-29T02:57:37.116583+08:00 localhost display-manager[1990]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
2023-08-29T02:57:37.203269+08:00 localhost dbus-daemon[1145]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.13' (uid=0 pid=2002 comm="localectl set-keymap jp106 ")
2023-08-29T02:57:37.210499+08:00 localhost systemd[1]: Starting Locale Service...
2023-08-29T02:57:37.431712+08:00 localhost systemd[1]: Started Freshclam virus definitions downloader.
2023-08-29T02:57:37.435234+08:00 localhost systemd[1]: Starting Clamav antivirus Deamon...
2023-08-29T02:57:37.456433+08:00 localhost dbus-daemon[1145]: [system] Successfully activated service 'org.freedesktop.locale1'
2023-08-29T02:57:37.456969+08:00 localhost systemd[1]: Started Locale Service.
2023-08-29T02:57:38.021973+08:00 localhost systemd[1]: Received SIGRTMIN+21 from PID 309 (plymouthd).
2023-08-29T02:57:38.130299+08:00 localhost dbus-daemon[1145]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service' requested by ':1.15' (uid=0 pid=2011 comm="/usr/sbin/gdm ")
2023-08-29T02:57:38.137141+08:00 localhost systemd[1]: Starting Accounts Service...
2023-08-29T02:57:38.612928+08:00 localhost display-manager[1979]: Starting service gdm..done
2023-08-29T02:57:38.615989+08:00 localhost systemd[1]: Started X Display Manager.
2023-08-29T02:57:39.778749+08:00 localhost accounts-daemon[2017]: started daemon version 0.6.55
2023-08-29T02:57:39.782289+08:00 localhost dbus-daemon[1145]: [system] Successfully activated service 'org.freedesktop.Accounts'
2023-08-29T02:57:39.782711+08:00 localhost systemd[1]: Started Accounts Service.
2023-08-29T02:57:39.782865+08:00 localhost accounts-daemon[2017]: g_dbus_interface_skeleton_get_object_path: assertion 'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed
2023-08-29T02:57:39.815473+08:00 localhost tlp[2022]: Error: tlp.service is not enabled, power saving will not apply on boot.
2023-08-29T02:57:39.829357+08:00 localhost tlp[2022]: >>> Invoke 'systemctl enable tlp.service' to correct this!
2023-08-29T02:57:39.881854+08:00 localhost tlp[2022]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
2023-08-29T02:57:39.885926+08:00 localhost tlp[2022]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
2023-08-29T02:57:39.909911+08:00 localhost tlp[2022]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
2023-08-29T02:57:39.913748+08:00 localhost tlp[2022]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
...
[output redacted for brevity]

I couldn’t make sense of what I see so far. How come there’s logged activity at a time that my computer is turned off?

Anyone have any thoughts on this?

#2

@markLopez9 what does the output from timedatctl show?

#3

As is obvious from provided logs, computer was not turned off. Why it was not turned off is impossible to even guess from this redacted output. Start with showing full log which includes at least going to sleep and resuming. And if computer again went to sleep after doing something - also this part.

#4

I’d like to start off with “I know I’m a rookie but I’m not yet crazy.” I know the computer is powered off, although it’s plugged in to a power outlet. I’m sure it’s off because I shut down my computer when not in use.

I’ll see if I can find more logs for you. brb

#5

@malcolmlewis

u@localhost:~> timedatectl
               Local time: Wed 2023-08-30 11:53:09 PST
           Universal time: Wed 2023-08-30 03:53:09 UTC
                 RTC time: Wed 2023-08-30 11:53:09
                Time zone: Asia/Manila (PST, +0800)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: yes

Warning: The system is configured to read the RTC time in the local time zone.
         This mode cannot be fully supported. It will create various problems
         with time zone changes and daylight saving time adjustments. The RTC
         time is never updated, it relies on external facilities to maintain it.
         If at all possible, use RTC in UTC by calling
         'timedatectl set-local-rtc 0'.
#6

@arvidjaar I have logs but I could not post it (too large). Tried uploading it but it looks like this thing will only accept pictures (.odt and .txt do not work)

#7

As your local time is UTC +8 and in your output it shows +8, I would bet that it’s just the UTC time you see.

Why don’t you just create a textfile with sudo somewhere like /etc/foo and then run

ls -lu --time-style=full-iso /etc | grep -i foo

to verify whether it’s UTC or not?

Edit:
Does

ls -lu --time-style=locale /etc | grep -i shadow

return the correct time?

#8

Upload to openSUSE Paste

It is possible that on boot your system is confused by this and starts with the “wrong” time until it is corrected by time server later. The logs shown so far are apparently from system boot. Try to compare times when you booted your system. Any similarity (modulo time zone offset)?

#9

@markLopez9 You can set the BIOS time to UTC and all should be good, if your dual booting with Windows, then add the registry setting RealTimeIsUniversal in TimeZone (Check the Internet for details).

#10

I already did that @404_UsernameNotFound in my initial post (quoted below):

Now, having mentioned this:

I tried it out earlier this afternoon and it looks the same.

@localhost:~> ls -lu --time-style=locale /etc | grep -i shadow
-rw-r----- 1 root shadow   1098 Sep  2 17:30 shadow
-rw-r----- 1 root shadow   1064 May 23 12:20 shadow-
-rw-r----- 1 root root      837 Aug 29  2022 shadow.YaST2save
u@localhost:~> ls -lu --time-style=full-iso /etc | grep -i shadow
-rw-r----- 1 root shadow   1098 2023-09-02 17:30:17.416529186 +0800 shadow
-rw-r----- 1 root shadow   1064 2023-05-23 12:20:22.000000000 +0800 shadow-
-rw-r----- 1 root root      837 2022-08-29 02:19:08.006632345 +0800 shadow.YaST2save
#11

Just tried that and this is what it said:

Content can't be larger than 2MB

I’m not sure I follow. Do what now?

#12

Well, use whatever other resource you can.

#13

This made me remember something, so I went back to the Start-Up guide and saw on the screenshot provided that “Hardware clock set to UTC” appears to be checked by default when installing for the first time. I don’t believe I unchecked that, although that was more than 3 years ago.

So would that be the culprit?

My box is actual on triple boot (openSUSE, Ubuntu and Windows - the latter two are for experiments only). Curious to know how that registry setting would affect openSUSE…?

#14

@markLopez9 Check the BIOS time, BIOS needs to be set to UTC, windows can’t handle UTC unless that registry setting is added…

#15

Is there a way around that? Like change something in openSUSE to read the BIOS time as is instead of changing it to UTC?

#16

I decided to manually sift through the logs given your theory on my system being confused with the time, and it looks like I found something:

2023-08-29T02:57:37.203269+08:00 localhost dbus-daemon[1145]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.13' (uid=0 pid=2002 comm="localectl set-keymap jp106 ")
2023-08-29T02:57:37.210499+08:00 localhost systemd[1]: Starting Locale Service...
2023-08-29T02:57:37.431712+08:00 localhost systemd[1]: Started Freshclam virus definitions downloader.
2023-08-29T02:57:37.435234+08:00 localhost systemd[1]: Starting Clamav antivirus Deamon...
2023-08-29T02:57:37.456433+08:00 localhost dbus-daemon[1145]: [system] Successfully activated service 'org.freedesktop.locale1'
2023-08-29T02:57:37.456969+08:00 localhost systemd[1]: Started Locale Service.
2023-08-29T02:57:38.021973+08:00 localhost systemd[1]: Received SIGRTMIN+21 from PID 309 (plymouthd).
2023-08-29T02:57:38.130299+08:00 localhost dbus-daemon[1145]: [system] Activating via systemd: service name='org.freedesktop.Accounts' unit='accounts-daemon.service' requested by ':1.15' (uid=0 pid=2011 comm="/usr/sbin/gdm ")
2023-08-29T02:57:38.137141+08:00 localhost systemd[1]: Starting Accounts Service...
2023-08-29T02:57:38.612928+08:00 localhost display-manager[1979]: Starting service gdm..done
2023-08-29T02:57:38.615989+08:00 localhost systemd[1]: Started X Display Manager.
2023-08-29T02:57:39.778749+08:00 localhost accounts-daemon[2017]: started daemon version 0.6.55
2023-08-29T02:57:39.782289+08:00 localhost dbus-daemon[1145]: [system] Successfully activated service 'org.freedesktop.Accounts'
2023-08-29T02:57:39.782711+08:00 localhost systemd[1]: Started Accounts Service.
2023-08-29T02:57:39.782865+08:00 localhost accounts-daemon[2017]: g_dbus_interface_skeleton_get_object_path: assertion 'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed
2023-08-29T02:57:39.815473+08:00 localhost tlp[2022]: Error: tlp.service is not enabled, power saving will not apply on boot.
2023-08-29T02:57:39.829357+08:00 localhost tlp[2022]: >>> Invoke 'systemctl enable tlp.service' to correct this!
2023-08-29T02:57:39.881854+08:00 localhost tlp[2022]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
2023-08-29T02:57:39.885926+08:00 localhost tlp[2022]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
2023-08-29T02:57:39.909911+08:00 localhost tlp[2022]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
2023-08-29T02:57:39.913748+08:00 localhost tlp[2022]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
2023-08-29T02:57:40.189325+08:00 localhost systemd[1]: Created slice User Slice of UID 460.
2023-08-29T02:57:40.195610+08:00 localhost systemd[1]: Starting User Runtime Directory /run/user/460...
2023-08-29T02:57:40.204461+08:00 localhost systemd-logind[1313]: New session c1 of user gdm.
2023-08-29T02:57:40.334626+08:00 localhost systemd[1]: Finished User Runtime Directory /run/user/460.
2023-08-29T02:57:40.339059+08:00 localhost systemd[1]: Starting User Manager for UID 460...
2023-08-29T02:57:40.432959+08:00 localhost (systemd): pam_unix(systemd-user:session): session opened for user gdm by (uid=0)
2023-08-29T02:57:41.638010+08:00 localhost systemd[2059]: Queued start job for default target Main User Target.
2023-08-29T02:57:41.640891+08:00 localhost systemd[2059]: Created slice User Application Slice.
2023-08-29T02:57:41.641308+08:00 localhost systemd[2059]: Reached target Paths.
2023-08-29T02:57:41.641601+08:00 localhost systemd[2059]: Reached target Timers.
2023-08-29T02:57:41.642899+08:00 localhost systemd[2059]: Starting D-Bus User Message Bus Socket...
2023-08-29T02:57:41.643544+08:00 localhost systemd[2059]: Listening on PipeWire Multimedia System Socket.
2023-08-29T02:57:41.644140+08:00 localhost systemd[2059]: Listening on Sound System.
2023-08-29T02:57:41.667817+08:00 localhost systemd[2059]: Listening on D-Bus User Message Bus Socket.
2023-08-29T02:57:41.667983+08:00 localhost systemd[2059]: Reached target Sockets.
2023-08-29T02:57:41.668117+08:00 localhost systemd[2059]: Reached target Basic System.
2023-08-29T02:57:41.668545+08:00 localhost systemd[1]: Started User Manager for UID 460.
2023-08-29T02:57:41.669906+08:00 localhost systemd[1]: Started Session c1 of User gdm.
2023-08-29T02:57:41.673822+08:00 localhost systemd[2059]: Reached target Main User Target.
2023-08-29T02:57:41.673968+08:00 localhost systemd[2059]: Startup finished in 1.228s.
2023-08-29T02:57:41.683284+08:00 localhost gdm-launch-environment]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
2023-08-29T02:57:41.891170+08:00 localhost tlp[2067]: Error: tlp.service is not enabled, power saving will not apply on boot.
2023-08-29T02:57:41.895158+08:00 localhost tlp[2067]: >>> Invoke 'systemctl enable tlp.service' to correct this!
2023-08-29T02:57:41.937985+08:00 localhost tlp[2067]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
2023-08-29T02:57:41.941881+08:00 localhost tlp[2067]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
2023-08-29T02:57:41.964942+08:00 localhost tlp[2067]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
2023-08-29T02:57:41.969087+08:00 localhost tlp[2067]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
2023-08-29T02:57:42.084128+08:00 localhost systemd[2059]: Started D-Bus User Message Bus.
2023-08-29T02:57:43.992125+08:00 localhost tlp[2110]: Error: tlp.service is not enabled, power saving will not apply on boot.
2023-08-29T02:57:43.996151+08:00 localhost tlp[2110]: >>> Invoke 'systemctl enable tlp.service' to correct this!
2023-08-29T02:57:44.045199+08:00 localhost tlp[2110]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
2023-08-29T02:57:44.049136+08:00 localhost tlp[2110]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
2023-08-29T02:57:44.074823+08:00 localhost tlp[2110]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
2023-08-29T02:57:44.078863+08:00 localhost tlp[2110]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
2023-08-29T10:57:46.194947+08:00 localhost chronyd[1484]: Selected source 162.159.200.123 (2.opensuse.pool.ntp.org)
2023-08-29T10:57:46.195075+08:00 localhost chronyd[1484]: System clock wrong by 28800.735247 seconds
2023-08-29T10:57:46.195144+08:00 localhost chronyd[1484]: System clock was stepped by 28800.735247 seconds
2023-08-29T10:57:46.206327+08:00 localhost systemd[1]: Started Timeline of Snapper Snapshots.
2023-08-29T10:57:46.437731+08:00 localhost dbus-daemon[1145]: [system] Activating via systemd: service name='org.opensuse.Snapper' unit='snapperd.service' requested by ':1.22' (uid=0 pid=2152 comm="/usr/lib/snapper/systemd-helper --timeline ")
2023-08-29T10:57:46.444127+08:00 localhost systemd[1]: Starting DBus interface for snapper...
2023-08-29T10:57:46.536277+08:00 localhost dbus-daemon[1145]: [system] Successfully activated service 'org.opensuse.Snapper'
2023-08-29T10:57:46.537927+08:00 localhost systemd[1]: Started DBus interface for snapper.
2023-08-29T10:57:46.558261+08:00 localhost systemd[1]: snapper-timeline.service: Deactivated successfully.
2023-08-29T10:57:46.695543+08:00 localhost gnome-shell[2149]: Running GNOME Shell (using mutter 41.9) as a Wayland display server
2023-08-29T10:57:46.801909+08:00 localhost tlp[2156]: Error: tlp.service is not enabled, power saving will not apply on boot.
2023-08-29T10:57:46.816133+08:00 localhost tlp[2156]: >>> Invoke 'systemctl enable tlp.service' to correct this!
2023-08-29T10:57:46.898193+08:00 localhost tlp[2156]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
2023-08-29T10:57:46.906112+08:00 localhost gnome-shell[2149]: Device '/dev/dri/card0' prefers shadow buffer
2023-08-29T10:57:46.910338+08:00 localhost tlp[2156]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
2023-08-29T10:57:46.916582+08:00 localhost gnome-shell[2149]: Added device '/dev/dri/card0' (i915) using atomic mode setting.
2023-08-29T10:57:46.950118+08:00 localhost tlp[2156]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
2023-08-29T10:57:46.971731+08:00 localhost tlp[2156]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
2023-08-29T10:57:47.799089+08:00 localhost gnome-shell[2149]: Created gbm renderer for '/dev/dri/card0'
2023-08-29T10:57:47.807471+08:00 localhost gnome-shell[2149]: Boot VGA GPU /dev/dri/card0 selected as primary
2023-08-29T10:57:48.550840+08:00 localhost /usr/lib/gdm/gdm-wayland-session[2104]: dbus-daemon[2104]: [session uid=460 pid=2104] Activating service name='org.a11y.Bus' requested by ':1.6' (uid=460 pid=2149 comm="/usr/bin/gnome-shell ")
2023-08-29T10:57:48.600707+08:00 localhost /usr/lib/gdm/gdm-wayland-session[2104]: dbus-daemon[2104]: [session uid=460 pid=2104] Successfully activated service 'org.a11y.Bus'
2023-08-29T10:57:48.998300+08:00 localhost tlp[2205]: Error: tlp.service is not enabled, power saving will not apply on boot.
2023-08-29T10:57:49.002386+08:00 localhost tlp[2205]: >>> Invoke 'systemctl enable tlp.service' to correct this!
2023-08-29T10:57:49.091304+08:00 localhost gnome-shell[2149]: Using public X11 display :1024, (using :1025 for managed services)
2023-08-29T10:57:49.091482+08:00 localhost gnome-shell[2149]: Using Wayland display name 'wayland-0'
2023-08-29T10:57:49.093602+08:00 localhost tlp[2205]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
2023-08-29T10:57:49.105589+08:00 localhost tlp[2205]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
2023-08-29T10:57:49.150841+08:00 localhost tlp[2205]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
2023-08-29T10:57:49.165101+08:00 localhost tlp[2205]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
2023-08-29T10:57:51.094295+08:00 localhost tlp[2241]: Error: tlp.service is not enabled, power saving will not apply on boot.
2023-08-29T10:57:51.106063+08:00 localhost tlp[2241]: >>> Invoke 'systemctl enable tlp.service' to correct this!
2023-08-29T10:57:51.182138+08:00 localhost tlp[2241]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.
2023-08-29T10:57:51.209837+08:00 localhost tlp[2241]: >>> Invoke 'systemctl mask systemd-rfkill.service' to correct this.
2023-08-29T10:57:51.250148+08:00 localhost tlp[2241]: Warning: systemd-rfkill.socket is not masked, radio device switching may not work as configured.
2023-08-29T10:57:51.269846+08:00 localhost tlp[2241]: >>> Invoke 'systemctl mask systemd-rfkill.socket' to correct this.
2023-08-29T10:57:52.507291+08:00 localhost kernel: [   57.911152][ T1725] BTRFS info (device sda2): balance: start -dusage=0
2023-08-29T10:57:52.507322+08:00 localhost kernel: [   57.911191][ T1725] BTRFS info (device sda2): balance: ended with status: 0
2023-08-29T10:57:52.734024+08:00 localhost nscd: 1270 monitoring file `/etc/resolv.conf` (5)
2023-08-29T10:57:52.734137+08:00 localhost nscd: 1270 monitoring directory `/etc` (2)
2023-08-29T10:57:52.736384+08:00 localhost systemd-hostnamed[1465]: Hostname set to <localhost.localdomain> (transient)
2023-08-29T10:57:53.099704+08:00 localhost nscd: 1270 monitoring file `/etc/resolv.conf` (5)
2023-08-29T10:57:53.099830+08:00 localhost nscd: 1270 monitoring directory `/etc` (2)
2023-08-29T10:57:53.113918+08:00 localhost gnome-shell[2149]: Getting parental controls for user 460
2023-08-29T10:57:54.010402+08:00 localhost tlp[2359]: Error: tlp.service is not enabled, power saving will not apply on boot.
2023-08-29T10:57:54.014866+08:00 localhost tlp[2359]: >>> Invoke 'systemctl enable tlp.service' to correct this!
2023-08-29T10:57:54.059837+08:00 localhost tlp[2359]: Warning: systemd-rfkill.service is not masked, radio device switching may not work as configured.

Does this make any sense?

#17

@markLopez9 That is the way openSUSE defaults now AFAIK, using UTC rather than localtime, I suspect it’s the same for other Linux systems…

#18

That’s a bummer. But okay, just another thing I just have to live with.

#19

@markLopez9 I believe Ubuntu is probably the same Arch expects to use UTC…

#20

In my experience, the default for openSUSE is to use local time if the installer finds a Windows system – and otherwise to use UTC.

I always use UTC, and if I need Windows I set that registry value or I put up with Windows always having the wrong time.

1 Like