Non-root clients can't find /tmp/mir_socket even when it's world-read/writable
Bug #1503971 reported by
Daniel van Vugt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Triaged
|
Low
|
Unassigned | ||
mir (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
Clients can't find /tmp/mir_socket by default when mixing root/non-root:
$ sudo mir_demo_
$ mir_demo_
Can't get connection
$ mir_demo_
*works*
$ sudo mir_demo_
*works*
description: | updated |
summary: |
- Clients can't find /tmp/mir_socket by default when mixing root/non-root + Non-root clients can't find /tmp/mir_socket even when it's world- + writable |
summary: |
- Non-root clients can't find /tmp/mir_socket even when it's world- + Non-root clients can't find /tmp/mir_socket even when it's world-read- writable |
summary: |
- Non-root clients can't find /tmp/mir_socket even when it's world-read- - writable + Non-root clients can't find /tmp/mir_socket even when it's world- + read/writable |
To post a comment you must log in.
This behaviour is correct. A client ought to connect to a session compositor (running as the user) and not to the system compositor (running as root).