chmod 777 /tmp/mir_socket is no longer sufficient for non-root clients to connect to a root server
Bug #1272143 reported by
Daniel van Vugt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
High
|
Alan Griffiths | ||
mir (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
In our docs it says you can chmod the Mir socket file to connect a non-root client to a root server:
http://
I did this, and it still doesn't work:
$ bin/mir_
Can't get connection
$ bin/mir_
Could not connect to a display server.
It seems even a world-writable socket is not enough. You have to run clients as root for them to work.
Related branches
lp://staging/~alan-griffiths/mir/fix-1272143
- PS Jenkins bot (community): Approve (continuous-integration)
- Alexandros Frantzis (community): Approve
- Andreas Pokorny (community): Approve
-
Diff: 151 lines (+36/-14)5 files modifieddoc/using_mir_on_pc.md (+2/-2)
examples/basic.c (+3/-3)
examples/flicker.c (+3/-3)
examples/multiwin.c (+25/-3)
examples/scroll.cpp (+3/-3)
lp://staging/~vanvugt/mir/fix-flicker-socket-help
- Alan Griffiths: Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 12 lines (+1/-1)1 file modifiedexamples/flicker.c (+1/-1)
Changed in mir: | |
status: | Confirmed → In Progress |
Changed in mir: | |
milestone: | none → 0.1.5 |
Changed in mir: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
It works but the documentation is wrong.
The default socket name depends on the user name.
For non-root this will typically be $XDG_RUNTIME_ DIR/mir_ socket
For root (where XDG_RUNTIME_DIR isn't set) this will typically be /tmp/mir_socket
So you need "bin/mir_ demo_client_ egltriangle -m /tmp/mir_socket"