Public bug reported:

People have reported the unity8 session snap to fail to start, with a
log excerpt (http://pastebin.ubuntu.com/24000769/):

ERROR: 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/src/common/sharedlibrary/shared_library.cpp(33):
 Throw in function mir::SharedLibrary::SharedLibrary(const char*)
Dynamic exception type: 
boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error>
 >
std::exception::what: 
/snap/unity8-session/439/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.12:
 cannot open shared object file: No such file or directory

Mir 0.26 is trying to load the mesa graphics v12, which only came in Mir
0.26.1. It seems Mir is somehow expecting for the system-installed
graphics v12 to be there in the snap.

** Affects: mir
     Importance: Undecided
         Status: New

** Affects: unity8-session-snap
     Importance: High
         Status: Triaged

** Also affects: mir
   Importance: Undecided
       Status: New

** Package changed: unity8 (Ubuntu) => unity8-session-snap

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1665123

Title:
  Mir graphics platform determined based on host system instead of snap

Status in Mir:
  New
Status in Unity8 Session Snap:
  Triaged

Bug description:
  People have reported the unity8 session snap to fail to start, with a
  log excerpt (http://pastebin.ubuntu.com/24000769/):

  ERROR: 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/src/common/sharedlibrary/shared_library.cpp(33):
 Throw in function mir::SharedLibrary::SharedLibrary(const char*)
  Dynamic exception type: 
boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error>
 >
  std::exception::what: 
/snap/unity8-session/439/usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.12:
 cannot open shared object file: No such file or directory

  Mir 0.26 is trying to load the mesa graphics v12, which only came in
  Mir 0.26.1. It seems Mir is somehow expecting for the system-installed
  graphics v12 to be there in the snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1665123/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to