[Bug 1667352] [NEW] SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync

Launchpad Bug Tracker 1667352 at bugs.launchpad.net
Fri Mar 17 12:27:40 UTC 2017


You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):

ubuntu 17.04 unity8, trying to run neverball game

Feb 23 17:46:43 pixel-desktop systemd[2629]: Starting ubuntu-app-launch-application-legacy-neverball-1487864803635991.service...
Feb 23 17:46:44 pixel-desktop neverball[3591]: Failure to initialize SDL (Failed to connect to the mir server: std::bad_alloc)
Feb 23 17:46:44 pixel-desktop systemd[2629]: ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Main process exited, code=exited, status=1/FAI
Feb 23 17:46:44 pixel-desktop systemd[2629]: Failed to start ubuntu-app-launch-application-legacy-neverball-1487864803635991.service.
Feb 23 17:46:44 pixel-desktop systemd[2629]: ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Unit entered failed state.
Feb 23 17:46:44 pixel-desktop systemd[2629]: ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Failed with result 'exit-code'.

** Affects: canonical-devices-system-image
     Importance: High
     Assignee: Stephen M. Webb (bregma)
         Status: In Progress

** Affects: mir
     Importance: High
     Assignee: Brandon Schaefer (brandontschaefer)
         Status: In Progress

** Affects: mir/0.26
     Importance: High
     Assignee: Brandon Schaefer (brandontschaefer)
         Status: Triaged

** Affects: libsdl2 (Ubuntu)
     Importance: Critical
         Status: Confirmed

** Affects: neverball (Ubuntu)
     Importance: Critical
         Status: Invalid

** Affects: protobuf (Ubuntu)
     Importance: High
     Assignee: Alexandros Frantzis (afrantzis)
         Status: In Progress


** Tags: mir patch
-- 
SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync
https://bugs.launchpad.net/bugs/1667352
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list