This bug was fixed in the package mir - 0.13.1+15.10.20150520-0ubuntu1 --------------- mir (0.13.1+15.10.20150520-0ubuntu1) wily; urgency=medium
[ Cemil Azizoglu ] * New upstream release 0.13.1 (https://launchpad.net/mir/+milestone/0.13.1) - ABI summary: No ABI break. Servers and clients do not need rebuilding. . Mirclient ABI unchanged at 8 . Mircommon ABI unchanged at 4 . Mirplatform ABI unchanged at 7 . Mirserver ABI unchanged at 31 - Bug fixes: . Can't load app purchase UI without a U1 account (LP: #1450377) . Crash because uncaught exception in mir::events::add_touch (LP: #1437357) -- CI Train Bot <ci-train-...@canonical.com> Wed, 20 May 2015 21:20:15 +0000 ** Changed in: mir (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1414883 Title: [regression] Clients log verbose info on startup: "Loader: Loading module: ..." Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Clients log to stdout (against the wishes of the client/toolkit author): [1422330274.158057] Loader: Loading modules from: bin/../lib/client-modules/ [1422330274.158235] Loader: Loading module: bin/../lib/client-modules/dummy.so [1422330274.158542] Loader: Loading module: bin/../lib/client-modules/mesa.so [1422330274.158658] Loader: Loading module: bin/../lib/client-modules/android.so This is something we need to avoid doing. You should only interrupt someone else's output stream if you have a serious error to report. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1414883/+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
