hyprland 0.52.0-1 e uwsm

[Archpresident]

Description
Since version 0.52.0-1, Hyprland seems to execute exec commands differently.

When I launch applications through Hyprland binds using uwsm app --,
the apps are started as children of the Hyprland process instead of being placed in their own
app-*.scope under systemd.

However, if I run the same uwsm app -- command from a terminal that was launched via Rofi,
the app is correctly started in a new scope.

If I run the command from a terminal that was itself launched via a Hyprland bind,
then the new app also stays under the Hyprland cgroup — not under systemd.

So this behavior appears to propagate through the process tree originating from Hyprland itself.

Steps to Reproduce
Add this to ~/.config/hypr/hyprland.conf:

Press SUPER+Return to open Kitty.

Inside Kitty, run:

Check with:
The app runs under Hyprland’s cgroup, not its own app-*.scope.

Now, run the same uwsm app -- firefox from a terminal opened via Rofi:
it correctly spawns a new app-*.scope.

Expected behavior
Apps launched through uwsm app -- should always get their own systemd scope,
regardless of whether they originate from a Hyprland bind or a terminal opened via Hyprland.

Actual behavior
Anything launched directly or indirectly from a Hyprland bind stays in Hyprland’s cgroup.

Versions
Hyprland: 0.52.0-1 (Arch Linux)
uwsm: [exact version]
systemd: [exact version]
wlroots: [optional]
Distribution: Arch Linux (fully up to date)
Additional notes
This behavior did not occur with Hyprland 0.51.x.
It seems that exec-spawned processes now inherit Hyprland’s session leader
instead of being re-parented under systemd’s app scopes.

[vaxerski]

See #11735 @kolayne

[Archpresident]

And then it's time to use Rofi. Ok got it :)

[Vladimir-csp]

Just tested this on 0.52.0, with pcmanfm and firefox, started via a keybind, with both uwsm app and app2unit, successfully scoped.

Can you post systemctl --user status?

[Archpresident]

system.log

Ok but now all apps are launched via rofi which uses uwsm to impose scopes, I'm not using hyprland shortcuts and I'm on hyprland 0.52.1-1

[Archpresident]

I found a temporary workaround for launching apps under uwsm from Hyprland keybinds.
Instead of calling uwsm app -- {cmd} directly (which runs under Hyprland’s session), I’m using Rofi in run mode:

bind = $mainMod, T, exec, rofi -modi run -show run -filter "uwsm app -- $terminal"

Then pressing Enter launches the app under its own uwsm systemd scope.

It’s not automatic (requires pressing Enter once), but it ensures the app is spawned correctly under uwsm instead of Hyprland’s process tree.

It also works with App2Unit instead of uwsm app --

[Archpresident]

ok, here I have a terminal kitty launched with a bind without rofi just with a UWSM app --
systemd.log

[Vladimir-csp]

All kitties seem to be accounted for, nothing extra in wayland-wm@hyprland\x2duwsm.desktop.service.

The only odd-looking thing is app-Hyprland-kitty-653fe5a3.scope in app.slice with kitty --session ... command. Is that it?

[Archpresident]

I don't know systemctl's output well, is it possible that it doesn't show the children of hyprland? To see that apps are launched under hyprland and not under systemd use btop. As you can see from the image there are a lot of apps open (via rofi) but there is a kitty terminal started by bind with uwsm app -- which is under hyprland. This was not the case in older versions of hyprland

There's also hyprshot, which I used to take a screenshot under hyprland while all the other apps are under systemd.

Kitty session is normal, it's nothing more than a kitty session that includes multiple tabs with three mail accounts on neomutt, rmpc, newsboat, and calcurse. I grouped everything in one session so I can launch all those software with a single bind, even if now I use rofi...

[Vladimir-csp]

Works as designed. Process launched in scopes are still children of processes that spawned them, in this case Hyprland. Previously Hyprland double-forked exec's, so systemd collected orphans. Now they stay with Hyprland.

The important thing is that processes are still correctly assigned to cgroups and units (which systemctl output confirms). So there is no need to do anything about it.

If you want all started apps be children of systemd user service, start them as services (-t service argument for uwsm app and app2unit or set UWSM_APP_UNIT_TYPE=service, APP2UNIT_TYPE=service env vars to alter default behavior).

[Archpresident]

Ok app2unit -t service kitty work..Perfect, thanks.