Sounds like this is just an (un)lucky case for bug 1605478. Sometimes it won't
crash if you're either:
(a) lucky enough to have a memory state that doesn't segfault; or
(b) running an X server somewhere else on the system.
In that case I would expect the Mir connection to fail with some error
message. But it could still be bug 1605478 that's the root cause.
Let's get a fix for bug 1605478 released first then see if this one
persists.
** Changed in: canonical-devices-system-image
Status: New => Incomplete
** Changed in: libsdl2 (Ubuntu)
Status: New => Incomplete
** Changed in: supertux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661836
Title:
supertux 2 can't start with SDL_VIDEODRIVER=mir [Couldn't initialize
SDL: Failed to connect to the mir server]
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661836/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
