Compositor
Distribution
If Other, please specify
No response
dms version
v1.4
Description
There is a technical mismatch between the official naming and the current software implementation, which breaks the dms doctor validation:
1.Documentation & Doctor Logic: The official documentation and dms doctor both expect a binary named mangowc and attempt to run mangowc --version for verification.
2.Actual Implementation: The currently installed binary and the active process are named mango.
3.The Result: Even though mango is running correctly, dms doctor fails the "Compositor Checks" because it cannot find the mangowc executable, resulting in the error: No supported Wayland compositor found.
Expected Behavior
No response
Steps to Reproduce & Installation Method
1.Run the mango compositor.
2.Run dms doctor.
3.Observe that "Active" identifies mango, but "Compositor" reports a failure because the mangowc command is missing.
Error Messages/Logs
No response
Screenshots/Recordings
Compositor
Distribution
If Other, please specify
No response
dms version
v1.4
Description
There is a technical mismatch between the official naming and the current software implementation, which breaks the dms doctor validation:
1.Documentation & Doctor Logic: The official documentation and dms doctor both expect a binary named mangowc and attempt to run mangowc --version for verification.
2.Actual Implementation: The currently installed binary and the active process are named mango.
3.The Result: Even though mango is running correctly, dms doctor fails the "Compositor Checks" because it cannot find the mangowc executable, resulting in the error: No supported Wayland compositor found.
Expected Behavior
No response
Steps to Reproduce & Installation Method
1.Run the mango compositor.
2.Run dms doctor.
3.Observe that "Active" identifies mango, but "Compositor" reports a failure because the mangowc command is missing.
Error Messages/Logs
No response
Screenshots/Recordings