-
-
Notifications
You must be signed in to change notification settings - Fork 71
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Before Reporting
- I found no existing issues matching my bug
- My issue is not caused by a theme
- My issue is not caused by a plugin
Describe the Bug
After running the following command as the website says
curl -fsSL "https://raw.githubusercontent.com/SteamClientHomebrew/Millennium/main/scripts/install.sh" | sudo sh
And then running sudo millennium patch
, this error pops up
# sudo millennium patch
Resolving permissions...
Error: Steam start script not found. Ensure you're Steam installation is not flatpak, or snap.
To clarify, my Steam installation in Debian was done by following the official Debian wiki.
This article to be exact.
Summarizing, I enabled Multi-Arch with dpkg --add-architecture i386
, installed steam-installer
with apt
, and installed Steam.
Expected Behavior
The patcher should be able to find the Steam run script normally.
Steps To Reproduce
- On a stable Debian 13 "Trixie" operating system, with
contrib
andnon-free
added to theapt
sources, like this
deb http://deb.debian.org/debian/ bookworm main contrib non-free
- Run the commands to enable Multi-Arch, update the list of packages, and install
steam-installer
dpkg --add-architecture i386
sudo apt update
sudo apt install steam-installer
- Install additional libraries (amd64 system)
apt install mesa-vulkan-drivers libglx-mesa0:i386 mesa-vulkan-drivers:i386 libgl1-mesa-dri:i386
- Run Millennium installation
curl -fsSL "https://raw.githubusercontent.com/SteamClientHomebrew/Millennium/main/scripts/install.sh" | sudo sh
- Try to patch Steam
sudo millennium patch
Operating System
Linux
Anything else?
My humble guess => Something to do with this Steam installation on Debian 13, since (as far as I know), it differs from the installation on previous Debian versions, where you just installed Steam as a normal package.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working