dinamic, you are a star...
Unfortunately I can think of a few reasons why this might happen.
1. Unity8 server died (although you would have noticed)
2. Apparmour problems
3. Fullscreen apps may crash the server in Mir 0.26.0 (bug 1661508)
And worse, when I try to test supertux under Mir right now it fails for
a 4th reason:
$ mirrun /usr/games/supertux2
[FATAL] /build/supertux-LmXSob/supertux-0.5.1/src/supertux/main.cpp:510
Unexpected exception: Couldn't initialize SDL: Failed to connect to the mir
server: Failed to connect to server socket: No such file or directory
Which sounds like a known issue with non-root users not being able to
auto-discover the Mir socket path. However then running it as root also
fails (SDL crashes trying to use X11).
I can't tell where the cause of this bug is. Might also be in SDL.
** Also affects: libsdl2 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: supertux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: supertux (Ubuntu)
Importance: Undecided => High
** Changed in: libsdl2 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1661836
Title:
supertux 2 doesn't start
Status in Canonical System Image:
New
Status in Mir:
New
Status in libsdl2 package in Ubuntu:
New
Status in supertux package in Ubuntu:
New
Status in unity8 package in Ubuntu:
New
Bug description:
17.04 / unity8 session
from what i understand this is an SDL2 app and should work on unity8,
it did before
$ journalctl --user-unit
ubuntu-app-launch-application-legacy-supertux2-1486212780752430.service
-- Logs begin at Sat 2017-02-04 14:24:38 EET, end at Sat 2017-02-04 14:55:01
EET. --
Feb 04 14:53:00 pixel-desktop systemd[3969]: Starting
ubuntu-app-launch-application-legacy-supertux2-1486212780752430.service...
Feb 04 14:53:01 pixel-desktop supertux2[8395]: [2017-02-04 14:53:01.377093]
<ERROR> MirConnectionAPI: Caught exception at client library boundary (in
mir_connection_release): /build/mir-1Sl_GZ/mir-0.26.0
Feb 04 14:53:01 pixel-desktop supertux2[8395]: Dynamic exception type:
boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<mir::socket_disconnected_error>
>
Feb 04 14:53:01 pixel-desktop supertux2[8395]: std::exception::what: Failed
to send message to server: Broken pipe
Feb 04 14:53:01 pixel-desktop supertux2[8395]: [boost::errinfo_errno_*] = 32,
"Broken pipe"
Feb 04 14:53:01 pixel-desktop supertux2[8395]: [FATAL]
/build/supertux-LmXSob/supertux-0.5.1/src/supertux/main.cpp:510 Unexpected
exception: Couldn't initialize SDL: Failed to connect to the mir server:
Feb 04 14:53:01 pixel-desktop systemd[3969]:
ubuntu-app-launch-application-legacy-supertux2-1486212780752430.service: Main
process exited, code=exited, status=1/FAILURE
Feb 04 14:53:01 pixel-desktop systemd[3969]: Failed to start
ubuntu-app-launch-application-legacy-supertux2-1486212780752430.service.
Feb 04 14:53:01 pixel-desktop systemd[3969]:
ubuntu-app-launch-application-legacy-supertux2-1486212780752430.service: Unit
entered failed state.
Feb 04 14:53:01 pixel-desktop systemd[3969]:
ubuntu-app-launch-application-legacy-supertux2-1486212780752430.service: Failed
with result 'exit-code'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661836/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
