Bug ID 1213366
Summary Steam sync not working in Lutris on Leap 15.5 (and likely also 15.4)
Classification openSUSE
Product openSUSE Distribution
Version Leap 15.5
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component X11 Applications
Assignee screening-team-bugs@suse.de
Reporter marix@marix.org
QA Contact qa-bugs@suse.de
Target Milestone ---
Found By ---
Blocker ---

Syncing the Steam library does not work in Lutris on Leap 15.5. I get the
following error:

2023-07-16 17:47:05,984: Error while completing task <bound method
BaseService.reload of <steam.SteamService object at 0x7f7b64cd87e0
(lutris+services+steam+SteamService at 0x557eb4432500)>>: <class 'KeyError'>
'contentstatsid'
  File "/usr/lib/python3.6/site-packages/lutris/util/jobs.py", line 34, in
target
    result = self.function(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/lutris/services/base.py", line 85, in
reload
    self.add_installed_games()
  File "/usr/lib/python3.6/site-packages/lutris/services/steam.py", line 159,
in add_installed_games
    for steamapps_path in self.steamapps_paths:
  File "/usr/lib/python3.6/site-packages/lutris/services/steam.py", line 154,
in steamapps_paths
    return get_steamapps_paths()
  File "/usr/lib/python3.6/site-packages/lutris/util/steam/config.py", line
170, in get_steamapps_paths
    return steam.steam().get_steamapps_dirs()
  File "/usr/lib/python3.6/site-packages/lutris/runners/steam.py", line 243, in
get_steamapps_dirs
    library_config = self.get_library_config()
  File "/usr/lib/python3.6/site-packages/lutris/runners/steam.py", line 149, in
get_library_config
    return read_library_folders(self.steam_data_dir)
  File "/usr/lib/python3.6/site-packages/lutris/util/steam/config.py", line
161, in read_library_folders
    library["libraryfolders"].pop("contentstatsid")

Well, most users will only get a popup that says "contentstatsid" and notice
the sync not working. But this backtrace is shown on the terminal when starting
Lutris from there.

The issue has been tracked upstream as
https://github.com/lutris/lutris/issues/4175 and is fixed in 0.5.10. But Leap
still ships 0.5.9.

The specific commit fixing it seems to be
https://github.com/lutris/lutris/commit/072e72a4aefd91101b79dd05d8ce9f100a4b6b0c.

If I manually apply the fix from the commit on my system, the issue is
resolved. We might want to consider applying the patch during packaging or just
upgrading the Leap version.


You are receiving this mail because: