** Summary changed:
- SDL apps "Failed to connect to the mir server: std::bad_alloc" or crash in
google::protobuf::MessageLite::InternalSerializeWithCachedSizesToArray from
mir_connect_sync
+ SDL apps either "Failed to connect to the mir server: std::bad_alloc" or
crash in protobuf via mir_connect_sync
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Changed in: canonical-devices-system-image
Status: New => Triaged
** Changed in: canonical-devices-system-image
Importance: Undecided => High
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => Stephen M. Webb (bregma)
** Changed in: canonical-devices-system-image
Milestone: None => u8c-1
** Summary changed:
- SDL apps either "Failed to connect to the mir server: std::bad_alloc" or
crash in protobuf via mir_connect_sync
+ SDL apps either "Failed to connect to the mir server: ..." or crash in
protobuf via mir_connect_sync
** Summary changed:
- SDL apps either "Failed to connect to the mir server: ..." or crash in
protobuf via mir_connect_sync
+ SDL apps either "Failed to connect to the mir server: ..." or segfault in
protobuf via mir_connect_sync
** Changed in: canonical-devices-system-image
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1667352
Title:
SDL apps either "Failed to connect to the mir server: ..." or segfault
in protobuf via mir_connect_sync
Status in Canonical System Image:
In Progress
Status in Mir:
In Progress
Status in Mir 0.26 series:
Triaged
Status in libsdl2 package in Ubuntu:
Confirmed
Status in neverball package in Ubuntu:
Invalid
Status in protobuf package in Ubuntu:
Confirmed
Bug description:
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'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667352/+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
