** Also affects: mir-android-platform
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1654536
Title:
** Changed in: mir
Milestone: 0.28.0 => None
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1654536
Title:
unity-system-compositor crashed with
The Android platform was deleted from lp:mir at revision 4155.
** Changed in: mir
Status: In Progress => Won't Fix
** Changed in: canonical-devices-system-image
Status: Confirmed => Won't Fix
** Changed in: mir (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this
** Changed in: mir
Milestone: 0.27.0 => 0.28.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1654536
Title:
unity-system-compositor crashed with
** Changed in: mir
Milestone: 0.26.0 => 1.0.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1654536
Title:
unity-system-compositor crashed with
** Changed in: mir
Milestone: None => 0.26.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1654536
Title:
unity-system-compositor crashed with
It could be that /etc/init/keep-display-on-during-boot.conf needs to be
ported to the systemd services. Not quite sure I understand enough about
the v+o to x+o (and upstart to systemd) to quickly diagnose if the
startup power situation is correct at time of error during bootup.
--
You received
Was able to see the error on startup in the bug in USC.
Confirmed that the quirk affecting fb bits don't affect operation, and
that both the overlay path and gl-rendered path work with the demo
servers and USC (after the system has come up fully).
This only seems to happen when the device is
** Changed in: mir (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1654536
Title:
unity-system-compositor crashed
Is the frieza_arm64 channel in a sane state? (I remember it being usable
about a month or so ago) I can't seem to even get to the dash. The mir
demo stuff is seems to work though.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
re the 600mb available, it could be some other resource than system
memory that the driver cannot access, given the limited enums the gl
driver can return.
** Changed in: mir
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: mir
Assignee: (unassigned) => Kevin DuBois (kdub)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1654536
Title:
** Summary changed:
- unity-system-compositor crashed EGL_BAD_SURFACE
+ unity-system-compositor crashed with
src/platforms/android/server/gl_context.cpp(233): ...
android::FramebufferGLContext::swap_buffers() ... std::exception::what:
eglSwapBuffers failure: EGL_BAD_SURFACE (0x300d)
**
13 matches
Mail list logo
