Remove systemd integration from nautilus extension #10082
Merged
+2
−30
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
swsnr
force-pushed
the
remove-systemd-from-nautilus-extension
branch
from
d246fa2 to
3356545
Compare
tristan957
approved these changes
Dec 29, 2025
Member
tristan957
left a comment
tristan957
left a comment
There was a problem hiding this comment.
Pinging @jcollie for review
jcollie
approved these changes
Dec 29, 2025
As far as I understand ghostty integrates with systemd already nowadays, and manages its own scopes/cgroups for tabs. As such, explicitly moving launching ghostty into a separate systemd scope from nautilus no longer seems necessary.
swsnr
force-pushed
the
remove-systemd-from-nautilus-extension
branch
from
3356545 to
622d492
Compare
Contributor
Author
|
@jcollie @tristan957 Thanks for the review. I pushed a small last-minute amend which removes the unused I hope that's okay 🙂 |
jcollie
approved these changes
Dec 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
As far as I understand ghostty already integrates with systemd nowadays, and manages its own scopes/cgroups for the application and all tabs. As such, explicitly moving launching ghostty into a separate systemd scope from nautilus no longer seems necessary. In any case the scope created by the nautilus extension quickly goes away, suggesting that Ghostty moves its processes out of this scope, and the process tree looks just the same when spawning ghostty directly.