[regression] Since r2408, legacy clients load two versions of libmircommon simultaneously
Bug #1434422 reported by
Daniel van Vugt
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mir |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Since r2408, legacy clients link to two libmircommon's simultaneously...
For example, running an older client binary against newer Mir works, but it requires:
libmirclient.so.8 => ./lib/libmircli
libmircommon.so.3 => /usr/lib/
libmircommon.so.4 => /home/dan/
This could be risky to maintain two copies of the same library in the same address space.
| summary: |
- [regression] Since r2408, legacy clients link to two libmircommon's - simultaneously + [regression] Since r2408, legacy clients load two versions of + libmircommon simultaneously |
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #1 |
| Changed in mir: | |
| importance: | Medium → Low |
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #2 |
| Changed in mir: | |
| assignee: | nobody → Daniel van Vugt (vanvugt) |
| milestone: | none → 0.13.0 |
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #3 |
| Changed in mir: | |
| assignee: | Daniel van Vugt (vanvugt) → nobody |
| milestone: | 0.13.0 → none |
| Changed in mir: | |
| importance: | Low → High |
| Changed in mir: | |
| importance: | High → Medium |
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #4 |
| Changed in mir: | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
Note this will only happen for "legacy" clients using newish functions like MirEvent 2.0. As outlined in bug 1415321.
So likely only Canonical projects are affected. Less likely that 3rd party projects are up-to-date enough to be affected.