Hello @josiahcarlson, can you check if [...]/logs/content_log.txt or [...]/logs/content_log.previous.txt has timestamps going back to when the Steam client forgot the secondary library folder? If it does, please share the information requested at https://github.com/ValveSoftware/steam-for-linux/issues/8552#issuecomment-1134892908.
I don't believe this is an OS/filesystem/library issue, but rather a Steam GUI one. I am seeing an identical broken 'add library' dialog, trying to add an external drive library from another machine (not lost, was never added/attached to the current Steam). Neither the "new folder" nor "select" buttons produce any effect in the mentioned logs, nor does the GUI respond in any way. I also see this same issue in the current Linux stable and beta steam client.
Exec summary: Believe this to be a GUI problem, not a file/filesystem one.
This is visible to me in both versions listed here:
Steam Version: 1700160213
Steam Client Build Date: Thu, Nov 16 1:23 PM UTC -08:00
Steam Web Build Date: Thu, Nov 16 1:06 PM UTC -08:00
Steam API Version: SteamClient021
Steam Version: 1700533348
Steam Client Build Date: Mon, Nov 20 8:07 PM UTC -08:00
Steam Web Build Date: Mon, Nov 20 8:50 PM UTC -08:00
Steam API Version: SteamClient021
In addition, when I use Storage -> (dropdown dialog, select "Add Drive") -> (dropdown, "Let me choose another location") -> (broken dialog, no selectable items aside from the buttons, "new folder..." and "select" have no visible effect, "cancel" does what it says) -> receive an error in the dialog, "#ContentManagement_Error_".
Recently upgraded to Ubuntu 22.04, and that seems to have solved the 'Settings -> Storage, clicking "Add Drive" ' leading to an empty dialog.
Have now added a path, moved a game, and have started the game from the new path. Settings seem to have persisted after restarting Steam.
I know people like to use the Ubuntu provided Snap or the community maintained Flatpak, but Valve didn't build the client with those pkg managers in mind and you shouldn't expect Valve to fix bugs with non-official packaging solutions.
I know people like to use the Ubuntu provided Snap or the community maintained Flatpak, but Valve didn't build the client with those pkg managers in mind and you shouldn't expect Valve to fix bugs with non-official packaging solutions.
Thanks for the input. I am running Arch, with the vanilla Steam client, not flatpak nor snap. I did workaround my issue by manually writing manifests for all my locations and it hasn’t yet re-broken, but I don’t think “Valve doesn’t support flatpak/snap” is the correct solution here.
Replying to https://github.com/ValveSoftware/steam-for-linux/issues/10207#issuecomment-1897471936
It's more that if there is a bug in the Snap, then the issue needs to be filed with Canonical first and then if it is found that the bug is in Steam itself, then file one here. But expecting any company or project to fix things so they work in a way that wasn't intended is ridiculous
I'm also seeing this on Arch, using both steam and steam-native-runtime packages (1.0.0.78-2).
I'm also seeing this on Arch, using both
steamandsteam-native-runtimepackages (1.0.0.78-2).
It's happening to me too.
EDIT: I fixed it by manually uninstalling all proton versions (removing the Proton* folders).
This is just happening to me now, also on an arch fresh install (but with leftover configs from a previous install. So far removed proton folders has not done anything.
I get this in Steam's console_log.txt when trying to add a new storage on my Arch system:
[2024-06-11 17:17:13] Unsupported desktop portal version: 0, falling back to a different file picker
I get this in Steam's console_log.txt when trying to add a new storage on my Arch system:
[2024-06-11 17:17:13] Unsupported desktop portal version: 0, falling back to a different file picker
I just got the exact issue, with this exact error message on EndeavourOS on KDE and i3.
I solved for i3 by doing the following
xdg-desktop-portal-gtk/usr/share/xdg-desktop-portal/portals/gtk.portalUseIn=gnome to UseIn=gnome;i3/usr/lib/xdg-desktop-portal-gtk and /usr/lib/xdg-desktop-portalHaven't tried on KDE
I can confirm @RedKage's solution worked for me. I'm on NixOS unstable with Sway and enabled Steam as normal:
programs.steam = {
enable = true;
remotePlay.openFirewall = true; # Open ports in the firewall for Steam Remote Play
dedicatedServer.openFirewall = true; # Open ports in the firewall for Source Dedicated Server
localNetworkGameTransfers.openFirewall = true; # Open ports in the firewall for Steam Local Network Game Transfers
};
and enabled XDG using the GTK portal, using a workaround from https://github.com/NixOS/nixpkgs/issues/262286 to patch gtk.portal with sway:
xdg.portal = {
enable = true;
extraPortals = [ pkgs.xdg-desktop-portal-gtk ];
wlr.enable = true;
};
# https://github.com/NixOS/nixpkgs/issues/262286
nixpkgs.overlays = [ (self: super: {
xdg-desktop-portal-gtk = super.xdg-desktop-portal-gtk.overrideAttrs {
postInstall = ''
sed -i 's/UseIn=gnome/UseIn=gnome;sway/' $out/share/xdg-desktop-portal/portals/gtk.portal
'';
};
} ) ];
and then restarted the XDG portal services:
systemctl --user restart xdg-desktop-portal-gtk.service
systemctl --user restart xdg-desktop-portal.service
and then restarted Steam. This was sufficient to get the GTK file picker working.
Also having this issue on Ubuntu 20.04. It occurred as I was re-organizing my storage and my steam installation is now unusable as a result!
I've also discovered that if you attempt to close steam with this dialogue open, the application hangs indefinitely and has to be manually killed.
Your system information
Steam client version (build number or date):
Steam Version: 1698777785
Steam Client Build Date: Mon, Oct 30 7:09 PM UTC -08:00
Steam Web Build Date: Fri, Oct 27 4:29 PM UTC -08:00
Steam API Version: SteamClient020
Distribution (e.g. Ubuntu):
Ubuntu 20.04
Opted into Steam client beta?: No
Have you checked for system updates?: Yes
Steam Logs:
Please describe your issue in as much detail as possible:
I've already checked atimes via stat on every path, and perms are 775 for all relevant paths
root is a 1tb SSD with ext4, with steam default stored in my home directory, I have a zfs pool mounted at
/mnt/bigpoolthat has about 3TB free, an encrypted sub-mount at/mnt/bigpool/encwith about the same.I have previously had a second steam folder at
/mnt/bigpool/steam, and it seems to still contain 549G of game contentI had downloaded the weekend demo for Space Engineers, installed, and played on the 28th. I also purchased Space Engineers, along with 2 other games on October 28.
Some time around October 29-30, according to the folder mod times, when Steam removed the demo automatically, and updated itself (Steam Client Build Date: Mon, Oct 30 7:09 PM UTC -08:00), it seems to have forgotten about the storage location at
/mnt/bigpool/steam, and no games in that path are listed as being installed (and no paths in that folder are shown as being modified after2023-10-30 20:38Pacific, which is approximately when I quit Steam on that day).When trying to add a library folder via Settings -> Storage, clicking "Add Drive" leads to a blank window, with "new folder", "select" and "cancel" buttons on the bottom, but no listings and nothing to click on the interior of the window
Prior to display of the window, there are a stream of "Couldn't write .../.steam_exec_test.sh: Read-only file system" logs prior, which seem to be fileio.cpp trying to test whether
/snap/*and/runmounts are writable. Those seem normal, but no other errors, and nothing in the list.Other information:
/mnt/bigpool/steamhave mod times after Oct 30 20:38, Pacific (when I quit Steam on that day)~/.local/share/Steam/logsreference/mnt/bigpool/steamafter2023-10-30 20:38:08Pacific (when I quit steam on that Day)/mnt/bigpool/steamare listed as being installed/mnt/bigpool/steam