Clients cannot connect when MIR_SOCKET=""
Bug #1634508 reported by
William Hua
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
Medium
|
William Hua | ||
debconf (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
mir (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
unity8 (Ubuntu) |
In Progress
|
Medium
|
William Hua |
Bug Description
Launch a Unity 8 desktop session, log out, then log into a Unity 7 session. Launch a Mir-on-X shell like MirAL and then try to launch a Mir client like mir_demo_
Unity 8's upstart script always sets MIR_SOCKET to its old value when the session ends. If MIR_SOCKET wasn't set, then the post-stop script will still set MIR_SOCKET, setting it to "". Mir should interpret this as if MIR_SOCKET were unset.
Related branches
lp://qastaging/~attente/mir/1634508
- Mir CI Bot: Approve (continuous-integration)
- Alan Griffiths: Approve
- Chris Halse Rogers: Abstain
- Cemil Azizoglu (community): Approve
-
Diff: 12 lines (+1/-1)1 file modifiedsrc/client/mir_connection_api.cpp (+1/-1)
lp://qastaging/~attente/unity8/1634508
- Michał Sawicz: Needs Information
-
Diff: 24 lines (+4/-1)1 file modifieddata/unity8.conf (+4/-1)
Changed in mir: | |
assignee: | nobody → William Hua (attente) |
importance: | Undecided → Medium |
milestone: | none → 0.25.0 |
status: | New → In Progress |
Changed in unity8 (Ubuntu): | |
assignee: | nobody → Lukáš Tinkl (lukas-kde) |
assignee: | Lukáš Tinkl (lukas-kde) → William Hua (attente) |
status: | New → In Progress |
Changed in unity8 (Ubuntu): | |
importance: | Undecided → Medium |
Changed in mir: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.25.0