ZacharyZhang-NY/omarchy-pkgs
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Ship the USB and Thunderbolt approval watchers as user units (#922)

Browse Source 
Omarchy enables omarchy-usb-authorization.service and
omarchy-thunderbolt-authorization.service from first-run, and the
Thunderbolt one from its setup command and a migration. The settings
packages left both only in /usr/share/omarchy/default/systemd/user, where
systemd does not look.

On edge the Thunderbolt migration (1790344599) therefore fails with "Unit
omarchy-thunderbolt-authorization.service does not exist" and every later
migration stays pending. First-run fails as well and enables none of its
units.

Install both in /usr/lib/systemd/user, wherever the source has them: the
4.0.4 release does not, so its package is unchanged.
This commit is contained in:
Emir Beganović authored and GitHub committed 2026-10-10 00:18:43 +00:00
1 parent 4936892061
commit 011a14a0d6
2 files changed
+20
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

pkgbuilds/omarchy-settings-dev/PKGBUILD
+10
View File
@@ -220,6 +220,16 @@ package() {
if [[ -f default/systemd/user/omarchy-brightness-keyboard-auto.service ]]; then
install -Dm644 default/systemd/user/omarchy-brightness-keyboard-auto.service "$pkgdir/usr/lib/systemd/user/omarchy-brightness-keyboard-auto.service"
fi
# First-run, a migration and their own setup commands enable the USB and
# Thunderbolt approval watchers. Left in /usr/share/omarchy/default alone,
# systemd cannot find them: the Thunderbolt migration fails, which holds back
# every migration after it, and first-run enables none of its units.
if [[ -f default/systemd/user/omarchy-usb-authorization.service ]]; then
install -Dm644 default/systemd/user/omarchy-usb-authorization.service "$pkgdir/usr/lib/systemd/user/omarchy-usb-authorization.service"
fi
if [[ -f default/systemd/user/omarchy-thunderbolt-authorization.service ]]; then
install -Dm644 default/systemd/user/omarchy-thunderbolt-authorization.service "$pkgdir/usr/lib/systemd/user/omarchy-thunderbolt-authorization.service"
fi
# Marks app.slice (and only app.slice) as a systemd-oomd kill candidate, so
# memory pressure costs one app scope instead of the compositor session.
# Thresholds live in etc/systemd/oomd.conf.d/10-omarchy.conf. Both this and
pkgbuilds/omarchy-settings/PKGBUILD
+10
View File
@@ -225,6 +225,16 @@ package() {
if [[ -f default/systemd/user/omarchy-brightness-keyboard-auto.service ]]; then
install -Dm644 default/systemd/user/omarchy-brightness-keyboard-auto.service "$pkgdir/usr/lib/systemd/user/omarchy-brightness-keyboard-auto.service"
fi
# First-run, a migration and their own setup commands enable the USB and
# Thunderbolt approval watchers. Left in /usr/share/omarchy/default alone,
# systemd cannot find them: the Thunderbolt migration fails, which holds back
# every migration after it, and first-run enables none of its units.
if [[ -f default/systemd/user/omarchy-usb-authorization.service ]]; then
install -Dm644 default/systemd/user/omarchy-usb-authorization.service "$pkgdir/usr/lib/systemd/user/omarchy-usb-authorization.service"
fi
if [[ -f default/systemd/user/omarchy-thunderbolt-authorization.service ]]; then
install -Dm644 default/systemd/user/omarchy-thunderbolt-authorization.service "$pkgdir/usr/lib/systemd/user/omarchy-thunderbolt-authorization.service"
fi
# Marks app.slice (and only app.slice) as a systemd-oomd kill candidate, so
# memory pressure costs one app scope instead of the compositor session.
# Thresholds live in etc/systemd/oomd.conf.d/10-omarchy.conf. Both this and