Having the same issues with ingame times showing as UTC, which is 5 hours ahead of me.
~ $ sudo hwclock
2025-09-05 07:38:21.990494-04:00
~ $ timedatectl
Local time: Fri 2025-09-05 07:40:27 EDT
Universal time: Fri 2025-09-05 11:40:27 UTC
RTC time: Fri 2025-09-05 11:40:27
Time zone: America/New_York (EDT, -0400)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
~ $
Distribution: Fedora 42
Flatpak: Yes
Steam Beta Branch: Stable Client
Steam Version: 1751405894
Steam Client Build Date: Fri, Jun 27 21:07 UTC -05:00
Steam Web Build Date: Tue, Jul 1 17:19 UTC -05:00
Steam API Version: SteamClient022
Can confirm this issue. Unlike #10057 the steam overlay is correct, just the time display in games is wrong. It seems that Proton has no timezone information, it seems to always use UTC.
I solved it by setting the following in the launch options:
TZ=EST5EDT LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 %command%
TZ=EST5EDT LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 %command%
If using the Steam flatpak, adding these as environment variables with Flatseal also seems to work.
It doesn't seem to use UTC for me but something like UTC-4.
I just saved a game at 21:59 (UTC+2) and the game says 15:59.
How are you all running Steam? I stopped having the issue a while ago, running the Flatpak distribution, on Aurora 44.
$ flatpak info --show-permissions com.valvesoftware.Steam
[Context]
shared=ipc;network;
sockets=pulseaudio;wayland;x11;
devices=all;
features=bluetooth;devel;multiarch;per-app-dev-shm;
filesystems=xdg-config/MangoHud:ro;xdg-config/gtk-4.0:ro;xdg-music:ro;xdg-pictures:ro;xdg-run/app/com.discordapp.Discord:create;/run/udev:ro;xdg-run/speech-dispatcher:ro;/run/media;/mnt;/media;/var/mnt/extra/aidan/steam;xdg-run/pipewire-0:ro;
persistent=.;
unset-environment=ALSA_CONFIG_PATH;TZ;STEAM_RUNTIME_PREFER_HOST_LIBRARIES;STEAM_RUNTIME;SDL_VIDEODRIVER;MESA_GLSL_CACHE_DIR;QT_QPA_PLATFORMTHEME;
[Session Bus Policy]
com.steampowered.*=own
org.kde.StatusNotifierWatcher=talk
org.freedesktop.Notifications=talk
org.freedesktop.ScreenSaver=talk
org.freedesktop.PowerManagement=talk
org.gnome.SessionManager=talk
[System Bus Policy]
org.freedesktop.UPower=talk
org.freedesktop.UDisks2=talk
[Environment]
ALSA_CONFIG_PATH=
TZ=
STEAM_EXTRA_COMPAT_TOOLS_PATHS=/app/share/steam/compatibilitytools.d:/app/utils/share/steam/compatibilitytools.d:/run/parent/app/share/steam/compatibilitytools.d
PYTHONPATH=/app/utils/lib/python3.13/site-packages
LC_NUMERIC=C
LC_MONETARY=C
FLATPAK_STEAM_UPDATE_SYMLINKS=0
DBUS_FATAL_WARNINGS=0
STEAM_RUNTIME_PREFER_HOST_LIBRARIES=
MANGOHUD=1
FLATPAK_STEAM_XDG_DIRS_PREFIX=~/.var/app/com.valvesoftware.Steam
LC_TELEPHONE=C
SSL_CERT_DIR=/etc/ssl/certs
STEAM_RUNTIME=
LC_MEASUREMENT=C
XDG_DATA_DIRS=/app/share:/usr/lib/extensions/vulkan/share:/usr/share:/usr/share/runtime/share:/run/host/user-share:/run/host/share:/usr/lib/pressure-vessel/overrides/share
LC_NAME=C
XDG_CONFIG_DIRS=/etc/xdg:/usr/lib/x86_64-linux-gnu/GL:/usr/lib/i386-linux-gnu/GL
LC_COLLATE=C
SDL_VIDEODRIVER=
GST_PLUGIN_SYSTEM_PATH=/app/lib/gstreamer-1.0:/app/lib32/gstreamer-1.0:/usr/lib/extensions/gstreamer-1.0:/usr/lib/x86_64-linux-gnu/codecs-extra/lib/gstreamer-1.0:/usr/lib/i386-linux-gnu/codecs-extra/lib/gstreamer-1.0:/usr/lib/x86_64-linux-gnu/gstreamer-1.0:/usr/lib/i386-linux-gnu/gstreamer-1.0
MESA_GLSL_CACHE_DIR=
LC_ADDRESS=C
QT_QPA_PLATFORMTHEME=
PATH=/app/bin:/app/utils/bin:/usr/bin
PROTON_DEBUG_DIR=/var/tmp
No overrides.
$ flatpak override --show com.valvesoftware.Steam
$
MANGOHUD=1x1 2026-09MESA_GLSL_CACHE_DIRx1 2026-09PROTON_DEBUG_DIR=/var/tmpx1 2026-09SDL_VIDEODRIVERx1 2026-09
Your system information
tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]Please describe your issue in as much detail as possible:
Games that are running through Proton such as Diablo 4 and Anno 1800 are showing the current time as being an hour ahead of where it actually is. As of the writing, the time here in Ireland is 22:48 on 24/01/25, but playing Diablo 4 or Anno 1800, the time shows as 23:48 instead. This seems to be similar to #10057, which was previously closed.
Steps for reproducing this issue: