[BUG] plugin_loader.service replaced with 429: Too Many Requests #822
Description
Please confirm
- I have searched existing issues
- This issue is not a duplicate of an existing one
- I have checked the common issues section in the readme file
- I have attached logs to this bug report (failure to include logs will mean your issue may not be responded to).
Bug Report Description
When I try a fresh install of Decky Loader prerelease version using official installer, Konsole produces the following output:
[sudo] password for deck: [sudo] password for deck: XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 199 100 199 0 0 972 0 --:--:-- --:--:-- --:--:-- 975
Failed to start plugin_loader.service: Unit plugin_loader.service has a bad unit file setting.
See system logs and 'systemctl status plugin_loader.service' for details.
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.
Possible reasons for having these kinds of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/, .requires/, or .upholds/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
The error states that plugin_loader.service is misconfigured.
So I open the file at /etc/systemd/system/plugin_loader.service, and surely enough, it's contents are gibberish:
429: Too Many Requests
For more on scraping GitHub and how it may affect your rights, please review our Terms of Service (https://docs.github.com/en/site-policy/github-terms/github-terms-of-service).
Manually deleting the service file and reinstalling produces the same result.
Expected Behaviour
Fresh install of Decky Loader should generate a plugin_loader.service file that looks something like this:
[Unit]
Description=SteamDeck Plugin Loader
After=network.target
[Service]
Type=simple
User=root
Restart=always
KillMode=process
TimeoutStopSec=15
ExecStart=${HOMEBREW_FOLDER}/services/PluginLoader
WorkingDirectory=${HOMEBREW_FOLDER}/services
Environment=UNPRIVILEGED_PATH=${HOMEBREW_FOLDER}
Environment=PRIVILEGED_PATH=${HOMEBREW_FOLDER}
Environment=LOG_LEVEL=DEBUG
[Install]
WantedBy=multi-user.target
SteamOS version
SteamOS 3.7.16 (Beta channel)
Selected Update Channel
Prerelease
Decky Loader Version
I'm guessing it's v3.1.11
Plugin Info
No plugins are installed.
Have you modified the read-only filesystem at any point?
No.
Backend Logs
Oct 26 19:47:26 steamdeck systemd[1]: /etc/systemd/system/plugin_loader.service:1: Assignment outside of section. Ignoring.
Oct 26 19:47:26 steamdeck systemd[1]: /etc/systemd/system/plugin_loader.service:2: Assignment outside of section. Ignoring.
Oct 26 19:47:26 steamdeck systemd[1]: plugin_loader.service: Service has no ExecStart=, ExecStop=, or SuccessAction=. Refusing.
Oct 26 19:47:26 steamdeck systemd[1]: /etc/systemd/system/plugin_loader.service:1: Assignment outside of section. Ignoring.
Oct 26 19:47:26 steamdeck systemd[1]: /etc/systemd/system/plugin_loader.service:2: Assignment outside of section. Ignoring.
Frontend Logs
cef_log.previous.txt is too large...