SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
High
|
Stephen M. Webb | ||
Mir |
Invalid
|
High
|
Brandon Schaefer | ||
0.26 |
Invalid
|
High
|
Unassigned | ||
libsdl2 (Ubuntu) |
Invalid
|
Critical
|
Unassigned | ||
protobuf (Ubuntu) |
Fix Released
|
High
|
Alexandros Frantzis |
Bug Description
ubuntu 17.04 unity8, trying to run neverball game
Feb 23 17:46:43 pixel-desktop systemd[2629]: Starting ubuntu-
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-
Feb 23 17:46:44 pixel-desktop systemd[2629]: Failed to start ubuntu-
Feb 23 17:46:44 pixel-desktop systemd[2629]: ubuntu-
Feb 23 17:46:44 pixel-desktop systemd[2629]: ubuntu-
Related branches
- Daniel van Vugt: Approve
- Mir CI Bot: Needs Fixing (continuous-integration)
- Kevin DuBois (community): Approve
-
Diff: 17 lines (+3/-0)1 file modifiedsrc/protobuf/google_protobuf_guard.cpp (+3/-0)
Changed in mir: | |
milestone: | none → 1.0.0 |
assignee: | nobody → Brandon Schaefer (brandontschaefer) |
importance: | Undecided → Critical |
importance: | Critical → High |
status: | Incomplete → In Progress |
summary: |
- Failure to initialize SDL (Failed to connect to the mir server: - std::bad_alloc) + SDL apps "Failed to connect to the mir server: std::bad_alloc" or crash + in + google::protobuf::MessageLite::InternalSerializeWithCachedSizesToArray + from mir_connect_sync |
Changed in protobuf (Ubuntu): | |
importance: | Undecided → High |
status: | New → Confirmed |
summary: |
- 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 |
Changed in canonical-devices-system-image: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Stephen M. Webb (bregma) |
milestone: | none → u8c-1 |
summary: |
- 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: |
- 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 |
Changed in protobuf (Ubuntu): | |
assignee: | nobody → Alexandros Frantzis (afrantzis) |
status: | Confirmed → In Progress |
no longer affects: | neverball (Ubuntu) |
Changed in canonical-devices-system-image: | |
status: | In Progress → Fix Released |
Changed in mir: | |
milestone: | 1.0.0 → none |
Sounds like a snap-specific problem.
neverball seems to run OK (with some other bugs) on Unity8 17.04 (deb) and in Mir demo servers.
Can you run it under gdb and get a stack trace of the crash?