Libertine X apps crash on start #22

Open
NeoTheThird opened this Issue May 27, 2017 · 5 comments

Comments

Projects
None yet
5 participants
Owner

NeoTheThird commented May 27, 2017

Installing a chroot container with libertine is no problem. Installing apps in the container works as well. However, when I start the X Apps the apps crash immediately.

reported by https://launchpad.net/~firstcome-lastserve.

Owner

Flohack74 commented Jun 3, 2017

Do we really going to focus on libertine at the moment (for this device)?

Owner

NeoTheThird commented Jun 3, 2017

Not right away, but we should soon. We might want to wait for 16.04 though... Fixing libertine will be a lot of work and it might be too much to fix it for legacy. But we need better compatibility with desktop apps as we want to make a convergent OS!

Rom4nB commented Jun 7, 2017

For me, I got first time ever libertine working with Krillin using the UBPorts image.

Firefox works (well, slowly as the hardware is limited, but works). I tried to install a SIP client. Qutecom installs and starts on the phone. But even on the desktop I don't get the configuration done that it connects to my SIP account. Linphone works on the desktop but when I try starting it after installing in a Libertine container on the phone, the app crashes.

So maybe it is only some applications crashing in Libertine. But even that e.g. Firefox works on my Krilin in a web container is more than was possible on the Canonical image before.

tager18 commented Sep 27, 2017

Don' t know if i can add this here, but will try :D. I have the same problem and in every log for desktop application (like application-legacy-container-identifier_firefox_0.0-.log) I got this:
EE)
Fatal server error:
(EE) Failed to connect to Mir: Failed to connect: not accepted by server
(EE)

@NeoTheThird NeoTheThird referenced this issue Nov 6, 2017

Closed

Desktop app #334

I think a long term solution for this would be using Xwayland once our build of Mir has support for Wayland instead of maintaining Xmir which was already tad buggy from last time I was able to use it

Alan's doing some tremendous work and I believe this could be looked at once we have our core components in a more recent build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment