canonical/mir

We're missing a way for Mir to report the socket it selects

Open

#1,398 opened on Apr 1, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C++ (137 forks)auto 404
Good first issue

Repository metrics

Stars
 (775 stars)
PR merge metrics
 (PR metrics pending)

Description

We've several launch scripts that try to choose a Wayland socket when launching a Mir server. That's unnecessarily repetitive as Mir is better placed to chose a socket automatically.

What's really missing is a way for Mir to report the socket it selects. (Like --x11-displayfd for the X11 socket.)

Contributor guide

Research direction
Investigate how Mir currently selects a Wayland socket and add a mechanism to report the selected socket via a file descriptor, similar to the existing x11 displayfd for X11.
Tech stack
cpp
Domain
backendcli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++WaylandLinux system programming
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60