Same error here. Any update?

system info:
OS: Arch Linux
Kernel: Linux 6.12.1-arch1-1
DE: KDE Plasma 6.2.4
WM: Kwin (Wayland)
CPU: AMD Ryzen 7 6800H
GPU: NVIDIA GeForce RTX 3060 Mobile /MAX-Q (nvidia-open 565.57.01)
Memory: 16GiB
Swap: 16GiB

steam version: stable branch 1733265492

log:
steam_logs.tar.gz

@sklynic based on your logs, there is an error with the connection from steamwebhelper to steam. There isn't enough data to say exactly why. I'll add some extra logging the next beta release to see if we can track down the culprit.

Meanwhile, can you give us any information on what make your setup different than the usual install Arch then sudo pacman -S steam and run steam? E.g. running steam inside specialized containers, or flatpak. Or non-standard security features or virtualized features like virtual /home. Any hints here could help us track down what is going on.

Can you also post the output of lsof -h and which lsof on your system?

To identify when you are running into this problem, you can run tail -F ~/.steam/steam/logs/transport_steamui.txt and you'll see errors being printed every couple of seconds. Normally it should just look like this:

[2024-12-11 11:32:30] WebUITransportController: Initialized
[2024-12-11 11:32:34] WebUITransport: Websocket connection from: https://steamloopback.host
[2024-12-11 11:32:34] WebUITransport: Connection from: 127.0.0.1:58366

But yours has a series of connection rejected messages instead.

Replying to [#11045 (comment)](https://github.com/valveSoftware/steam-for-linux/issues/11045#issuecomment-2537303977)

I don't know if any following action would modify my steam installization (I have done it before to test other games, most of the time i use the defalut steam provided by sudo pacman -S steam):

1. use steam-native-runtime provided from Arch repository;
2. running steam-runtime --reset

Should I delete steam client folder and perform a fresh steam install, or continuing look on current one and opt-in steam beta?

➜  ~ lsof -h
lsof 4.99.4
 latest revision: https://github.com/lsof-org/lsof
 latest FAQ: https://github.com/lsof-org/lsof/blob/master/00FAQ
 latest (non-formatted) man page: https://github.com/lsof-org/lsof/blob/master/Lsof.8
 usage: [-?abhHKlnNoOPRtUvVX] [+|-c c] [+|-d s] [+D D] [+|-E] [+|-e s] [+|-f[gG]]
 [-F [f]] [-g [s]] [-i [i]] [+|-L [l]] [+m [m]] [+|-M] [-o [o]] [-p s]
 [+|-r [t]] [-s [p:s]] [-S [t]] [-T [t]] [-u s] [+|-w] [-x [fl]] [--] [names]
Defaults in parentheses; comma-separated set (s) items; dash-separated ranges.
  -?|-h list help          -a AND selections (OR)     -b avoid kernel blocks
  -c c  cmd c ^c /c/[bix]  +c w  COMMAND width (9)    +d s  dir s files
  -d s  select by FD set   +D D  dir D tree *SLOW?*   +|-e s  exempt s *RISKY*
  -i select IPv[46] files  -K [i] list|(i)gn tasKs    -l list UID numbers
  -n no host names         -N select NFS files        -o list file offset
  -O no overhead *RISKY*   -P no port names           -Q allow failed search
  -R list paRent PID       -s list file size          -t terse listing
  -T disable TCP/TPI info  -U select Unix socket      -v list version info
  -V verbose search        +|-w  Warnings (+)         -X skip TCP&UDP* files
  -H human readable size   -- end option scan       
  -E display endpoint info              +E display endpoint info and files
  +f|-f  +filesystem or -file names     +|-f[gG] flaGs 
  -F [f] select fields; -F? for help  
  +|-L [l] list (+) suppress (-) link counts < l (0 = all; default = 0)
                                        +m [m] use|create mount supplement
  +|-M   portMap registration (-)       -o o   o 0t offset digits (8)
  -p s   exclude(^)|select PIDs         -S [t] t second stat timeout (15)
  -T fqs TCP/TPI Fl,Q,St (s) info
  -g [s] exclude(^)|select and print process group IDs
  -i i   select by IPv[46] address: [46][proto][@host|addr][:svc_list|port_list]
  +|-r [t[m<fmt>]] repeat every t seconds (15);  + until no files, - forever.
       An optional suffix to t is m<fmt>; m must separate t from <fmt> and
      <fmt> is an strftime(3) format for the marker line.
  -s p:s  exclude(^)|select protocol (p = TCP|UDP) states by name(s).
  -u s   exclude(^)|select login|UID set s
  -x [fl] cross over +d|+D File systems or symbolic Links
  names  select named files or files on named file systems
Only root can list all files, but anyone can list socket files.
/dev warnings disabled; kernel ID check disabled.

➜  ~ which lsof
/usr/bin/lsof

the connection rejected message pops up right after I start steam and continues showing up

@sklynic the newest beta client has some extra log info that should help narrow down the problem you are experiencing.

Can update to the latest beta, repro the problem and then send me your updated logs?

Replying to [#11045 (comment)](https://github.com/ValveSoftware/steam-for-linux/issues/11045#issuecomment-2543188143)

steam version: steam beta update 1734061824

Tried launch steam, enable game recording, launch linux native and windows .exe games. Connection rejected still kept showing up right after I launched steam client, along with Cannot read properties of undefined (Reading 'GetTimelineLoaderForGame') error in overlay.

logs: steam_logs_1734061824.tar.gz

Thanks for the logs @sklynic , I think I see the bug, I'll get a fix out for it next week.

@sklynic I'm curious, what is your system hostname? You can find it by running:

hostnamectl

or

cat /proc/sys/kernel/hostname

Replying to [#11045 (comment)](https://github.com/ValveSoftware/steam-for-linux/issues/11045#issuecomment-2543506036)

hostname is LAPTOP-NPL4IC5Z, if that helps diagnose into it

@sklynic thanks for the info. The newest beta should have a fix to address your issue. Let me know if it works properly now.

It will probably also speed up your startup times.

@sklynic thanks for the info. The newest beta should have a fix to address your issue. Let me know if it works properly now.

It will probably also speed up your startup times.

Comfirmed both issue solved now, no more error message in log or overlay.

@artik are you still running into issues? If it is fixed for both of you I'm going to close the issue.

If it isn't working, can you grab a new copy of your logs while running the latest beta?

@artik are you still running into issues? If it is fixed for both of you I'm going to close the issue.

If it isn't working, can you grab a new copy of your logs while running the latest beta?

It's working on my side now, thanks for the fix.