Add HYPRLAND_NO_SD_VARS env condition #7358
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your PR, what does it fix/add?
Closes #7083. This was pretty simple.
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
Not sure if hardcoding
systemctl
&dbus-update-activation-environment
stuff is really a good idea. Config would be more appropriate IMHO.Especially the way
dbus-update-activation-environment
and the original dbus' environment works: it can not unset stuff.Calling
dbus-update-activation-environment
with a bunch of already unset vars does literally nothing. From manpage:The only cleanup option with original dbus is to export empty strings, and execute without
--systemd
.And with
dbus-broker
there is no need fordbus-update-activation-environment
at all, which begs for special treatment.Is it ready for merging, or does it need work?
Patched my debian's hyprland 0.41.2, seems to work.