Clarified Connection Troubleshooting section for Linux users in setup documentation and provided 2 additional workarounds#46
Open
DasStone wants to merge 1 commit into
Conversation
…x users and offered 2 alternative solutions other than installing the flatpak
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Underlying Issue
On Linux, Dolphin Memory Engine may not be able to connect to Dolphin. The current documentation recommends installing the Dolphin Flatpak as a workaround. However, it is perfectly fine to use any other Dolphin installation if the appropriate workarounds are applied. With this PR, anyone using Linux can use their preferred way of installing Dolphin.
This PR clarifies the root cause of the issue, which is the Yama Linux Security Module. Some Linux distributions (such as Arch) set their
ptrace_scopeto1, which in most cases prevents Dolphin Memory Engine (or any other debugger) from accessing the Dolphin process, as they are typically not in a parent-child process relationship.Suggested fixes:
ptrace_scopeto0.unshare -Ur dolphin-emu(this runs Dolphin in a new user namespace. Because Dolphin Memory Engine remains in the parent user namespace, capability checks for ptrace are evaluated differently, allowing access even with Yama restrictions enabled)