* Launch apps in their own scope instead of the compositor's cgroup
The launcher ran desktop entries through gtk-launch, so the app inherited
quickshell's cgroup, which belongs to wayland-wm@hyprland.desktop.service.
A kernel OOM kill there fails the compositor unit and tears down the whole
session, dropping the user at SDDM with every window lost. A single runaway
app took the desktop down three times in one afternoon.
Route launches through uwsm-app so each app gets its own scope under
app-graphical.slice. A runaway app now fails its own scope and the session
keeps running.
The post-install launches had the same inheritance bug in a milder form,
where the app landed in the installer terminal's scope and died with it.
0aedef58 patched that with setsid, which detaches the session but leaves
cgroup membership behind. A scope fixes it properly.
* Detach post-install app launches
* Preserve desktop entry launch compatibility
---------
Co-authored-by: David Heinemeier Hansson <david@hey.com>
30 lines
866 B
Bash
Executable File
30 lines
866 B
Bash
Executable File
#!/bin/bash
|
|
|
|
# omarchy:summary=Install VS Code and configure Omarchy defaults for secrets, updates, and theme
|
|
|
|
echo "Installing VSCode..."
|
|
omarchy-pkg-add visual-studio-code-bin
|
|
|
|
mkdir -p ~/.vscode ~/.config/Code/User
|
|
|
|
cat > ~/.vscode/argv.json << 'EOF'
|
|
// This configuration file allows you to pass permanent command line arguments to VS Code.
|
|
// Only a subset of arguments is currently supported to reduce the likelihood of breaking
|
|
// the installation.
|
|
//
|
|
// PLEASE DO NOT CHANGE WITHOUT UNDERSTANDING THE IMPACT
|
|
//
|
|
// NOTE: Changing this file requires a restart of VS Code.
|
|
{
|
|
"password-store":"gnome-libsecret"
|
|
}
|
|
EOF
|
|
|
|
# Ensure VSC's own auto-update feature is turned off
|
|
printf '{\n "update.mode": "none"\n}\n' > ~/.config/Code/User/settings.json
|
|
|
|
# Apply Omarchy theme to VSCode
|
|
omarchy-theme-set-vscode
|
|
|
|
setsid uwsm-app -- gtk-launch code >/dev/null 2>&1 &
|