Mir

[regression] nested servers do not start

Bug #1353658 reported by Kevin DuBois
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Critical
Kevin DuBois
0.6
Fix Released
Critical
Kevin DuBois
mir (Ubuntu)
Fix Released
Critical
Unassigned

Bug Description

some of the symbol burying hid the create_native_platform symbol, which is just used by nested servers.

root@ubuntu-phablet:/home/phablet# ./mir_demo_server_basic --host-socket /tmp/a --file /tmp/b
ERROR: /home/kdub/source/mir/devel/src/shared/sharedlibrary/shared_library.cpp(53): Throw in function void* mir::SharedLibrary::load_symbol(const char*) const
Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_errorEEEE
std::exception::what: /usr/lib/arm-linux-gnueabihf/libmirplatformgraphics.so: undefined symbol: create_native_platform

Related branches

tags: added: rtm14
Changed in mir:
importance: High → Critical
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:mir/devel at revision None, scheduled for release in mir, milestone Unknown

Changed in mir:
status: In Progress → Fix Committed
Changed in mir:
milestone: 0.7.0 → 0.6.0
no longer affects: mir/0.6
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Fix backported to lp:mir/0.6 at revision 1837.

Changed in mir:
milestone: 0.6.0 → 0.7.0
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Bisected. The problem originated in:
------------------------------------------------------------
revno: 1811 [merge]
author: Alan Griffiths <email address hidden>
committer: Tarmac
branch nick: development-branch
timestamp: Fri 2014-08-01 13:38:40 +0000
message:
  platformgraphics - restrict the exports of the platform libraries.

  Approved by Alexandros Frantzis, Kevin DuBois, PS Jenkins bot.
------------------------------------------------------------

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

mir (0.6.0+14.10.20140811-0ubuntu1) utopic; urgency=medium

Changed in mir (Ubuntu):
importance: Undecided → Critical
status: New → Fix Released
Changed in mir:
milestone: 0.7.0 → none
status: Fix Committed → Fix Released
Changed in mir:
milestone: none → 0.7.0
status: Fix Released → Fix Committed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Sorry for the confusion. Most of the 0.7.0 series got merged into 0.6.0 at a late stage. I've verified everything in 0.6.0 is also fixed in 0.7.0. So although the branched fixes in 0.7.0 have not been "released" yet, the equivalent fixes in 0.6.0 have. No need to mention them in 0.7 any more.

Changed in mir:
milestone: 0.7.0 → none
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.