The services removed from hyprland.conf in this commit are also spawned by systemd when a user logs in and can cause breakage if Hyprland starts them manually. In theory, most of these daemons should detect that they're duplicates and fail, but I'd rather not have the potential for race conditions.
For reference, here's a depgraph of Hyprland's graphical-session.target:
It's also worth noting that every session -- graphical or otherwise -- gets Pipewire for free. None of the compositors should be launching it themselves, as that can lead to the screensharing failures mentioned in #80. This wasn't the case for Hyprland, but it's worth noting.
I believe the configuration lines are still useful for users launching from a tty and so left them in, commented out for reference.
Related to #80 Noissue
The services removed from
hyprland.conf
in this commit are also spawned by systemd when a user logs in and can cause breakage if Hyprland starts them manually. In theory, most of these daemons should detect that they're duplicates and fail, but I'd rather not have the potential for race conditions.For reference, here's a depgraph of Hyprland's
graphical-session.target
:It's also worth noting that every session -- graphical or otherwise -- gets Pipewire for free. None of the compositors should be launching it themselves, as that can lead to the screensharing failures mentioned in #80. This wasn't the case for Hyprland, but it's worth noting.
I believe the configuration lines are still useful for users launching from a tty and so left them in, commented out for reference.