so if the previous code looked like this:
MirWindowSpec *spec = mir_create_normal_window_spec(connection, width, *height);
mir_window_spec_set_pixel_format(spec, pixel_format);
MirWindow* window = mir_create_window_sync(spec);
EGLSurface eglsurface = eglCreateWindowSurface(egldisplay, eglconfig,
after the drivers transition to supporting MirRenderSurface, the egl
creation starts to look like this:
MirRenderSurface* rs = mir_connection_create_render_surface_sync(connection,
width, height);
EGLSurface eglsurface = eglCreateWindowSurface(egldisplay, eglconfig, rs, NULL);
And, since the maj
** Changed in: mir
Milestone: 0.26.2 => None
** Changed in: mir
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1667014
Title:
If no pixel fo
So this has to do about transitioning from creating a window with a
'default' surface to creating both the surface and then coordinating it
with the window.
In this example its using the 'default' surface/bstream creation that
we're phasing out.
The proper transition would be to create MirRenderS
Its even a bit more narrow than that, software clients of android work
(its just ShmBuffer-backed software clients that would be affected).
Furthermore, the nested compositor had to select GL rendering instead of
pasthrough (which is probably common in the wild), and the surface had
to be larger th
** Tags added: mesa
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1663062
Title:
[regression] Software clients of nested servers are all black in Mir
0.25.0 and later
Sta
** Branch linked: lp:~kdub/mir/fix-1661521-0.26.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1661521
Title:
[regression] Windowed clients of nested servers are all black
pixel format was not communicated properly all the way back to the
client buffers. This resulted in the nested server's EGLClientBuffer
image import failing, only in the mesa platform.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
Why this crashes sometimes and other times spams is that wait_for_all()
is sometimes called on a nullptr MirWaitHandle. The first thing that fn
does is grab a lock. Some libc's seem smart enough to recognize that the
memory isn't there and throw system_error, but its pretty conceivable
that this co
yep, was the removal-of waithandle MP. needed some more checks before
waiting for interval configuration.
** Changed in: mir/0.26
Assignee: (unassigned) => Kevin DuBois (kdub)
** Changed in: mir/0.26
Status: Triaged => In Progress
** Branch linked: lp:~kdub/mir/fix-1661508
-
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 th
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 boot
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 t
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 p
I somewhat doubt that quirk would help, iirc, it was added after reports
that it helped from the bringup (but by the time it got released it
didn't seem to do anything in my local testing)
0x505 is GL_OUT_OF_MEMORY, perhaps a leak?
--
You received this bug notification because you are a member o
affects mir 0.24 landing too:
https://launchpadlibrarian.net/279042110/buildlog_ubuntu-yakkety-armhf.mir_0.24.0+16.10.20160815-0ubuntu1_BUILDING.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libhybris in Ubuntu.
https
Have a spike-prototype working of bypassing buffers. Still more work to
do with atomic multi-bufferstream updates, and sorting out the nested
platform, but goal is within reach...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
hmm, seems that I can't target to a released milestone
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1578159
Title:
Performance loss with NBS and overlays on
Status in Mir:
right, this was in 0.23, doesnt affect 0.24.
** No longer affects: mir/0.23
** Changed in: mir
Milestone: 0.24.0 => None
** Changed in: mir
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
install fresh image
click through or disable welcome wizard/edges intro, setup network
navigate to the Ubuntu Store
click on an application, click to install (eg Telegram)
enter username, password, 2fa details
u8-dash hangs at this point (screenshot attached during hang)
u8
** Attachment added: "unity8-dash.log"
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1607047/+attachment/4708262/+files/unity8-dash.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs
lso affects: mir/0.24
Importance: Undecided
Status: New
** Changed in: mir/0.24
Milestone: None => 0.24.0
** Changed in: mir/0.24
Assignee: (unassigned) => Kevin DuBois (kdub)
** Changed in: mir/0.24
Importance: Undecided => High
** Changed in: mir/0.24
Status
seems like a problem where one problem in setup causes a lot of test
failures, not sure what the one problem could be though.
--
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/16
Public bug reported:
When running through the u8 autopilot testing on a fresh install
(krillin, system image 392), I encountered 44 errors in autopilot. (full
log attached). Followed instructions here:
https://wiki.ubuntu.com/Touch/Testing/Autopilot/TestRunners
u8 autopilot testing is recommended
** Changed in: mir
Milestone: 0.25.0 => 0.24.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1593655
Title:
Servers based on Mir need a hook to execute code when the serv
** Changed in: mir
Milestone: 0.25.0 => 0.24.0
** No longer affects: mir/0.24
** Branch unlinked: lp:~kdub/mir/0.24-1599867
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1
** Changed in: mir
Milestone: 0.25.0 => 0.24.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1603080
Title:
mirtest-dev provides an incorrect .pc file
Status in Mir:
F
** Changed in: mir
Milestone: 0.25.0 => 0.24.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1603091
Title:
mir_test_framework::server_platform_path(),
mir_test_framewo
** Changed in: mir
Status: In Progress => Fix Committed
--
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/1565236
Title:
AltGr not working on external keyboards
Status
** Changed in: mir
Milestone: 0.25.0 => 0.24.0
** No longer affects: mir/0.24
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1579866
Title:
Android graphics platform does
** Changed in: mir
Milestone: 0.25.0 => 0.24.0
** No longer affects: mir/0.24
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1603114
Title:
mir_acceptance_tests.bin: doub
** No longer affects: mir/0.24
** Changed in: mir
Milestone: 0.25.0 => 0.24.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1601810
Title:
ftbfs in linking libmir-test-a
** No longer affects: mir/0.24
** Changed in: mir
Milestone: 0.25.0 => 0.24.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1602966
Title:
[regression] The Super/Windows
ution seems to be to use -Wl,--whole-archive to make sure
that the symbols generated from the gmock templates are still available
despite linkage order
** Changed in: mir
Assignee: (unassigned) => Kevin DuBois (kdub)
** Branch linked: lp:~kdub/mir/fix-1601810
--
You received this bug noti
https://launchpadlibrarian.net/272331980/buildlog_ubuntu-
vivid-i386.mir_0.24.0+15.04.20160711-0ubuntu1_BUILDING.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1462033
Ti
hmm, seen again in CI, perhaps from different causes. will file a new
bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1462033
Title:
[testsfail]
NestedInput.nested_event
** Changed in: mir
Milestone: 0.24.0 => 0.25.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1506358
Title:
libmirclient gives up and terminates prematurely with
"std::
** Changed in: mir
Milestone: 0.24.0 => 0.25.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1552371
Title:
Unexpected display on
Status in Canonical System Image:
I
** Changed in: mir
Milestone: 0.24.0 => 0.25.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1495974
Title:
[android] renogotiation of pixel formats is not supported, lea
** Changed in: mir
Milestone: 0.24.0 => None
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1262116
Title:
Nested servers prevent overlays or fullscreen bypass from workin
** Changed in: mir
Milestone: 0.24.0 => 0.25.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1570698
Title:
CI failure in TestClientInput.receives_one_touch_event_per_fra
** Changed in: mir
Milestone: 0.24.0 => 0.25.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1537389
Title:
Unity8 never loads and just stays on a black screen [unity8.lo
** Changed in: libhybris
Status: New => Invalid
--
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/1563287
Title:
[regression] [OTA-10] Spread animation stutters badly w
** No longer affects: mir/0.23
--
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/1565236
Title:
AltGr not working on external keyboards
Status in Canonical System Image:
Fi
** No longer affects: mir/0.23
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1583536
Title:
mirtest-dev is hard to use as the objects used are compiled with LTO
Status in Mi
** Branch linked: lp:~kdub/mir/fix-1590765
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1590765
Title:
OSK flickers and buttons are sometimes invisble
Status in
** Changed in: mir
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1590765
Title:
OSK flickers and buttons are sometimes invisble
S
Seems the sequence that's happening is:
many resize events happen, with the last resize event resizing to the
same size as the keyboard started with. This triggers a reallocation of
a buffer with the same size. The new buffer goes into the driver, and
comes out unfilled.
So, its looking like the
workaround committed to mir 0.23.1 and released to images. Now working
on proper fix for lp:mir
** Changed in: mir
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubu
** Changed in: mir/0.23
Status: In Progress => Fix Released
** 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 ubuntu-keyboard in Ubuntu.
siloed in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/landing-043/+packages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1590765
Title:
OSK flic
most reliable way to see:
start camera and message app. Transition from camera app to message app. Swipe
up to compose a new message. Tap the keyboard to see flickering.
Problem is not permanent; rotating the screen will get the keyboard back
into a good state.
--
You received this bug notifica
Alright, so plan is to land the workaround in lp:~mir-team/mir/nbs-
off-1590765 in mir 0.23.1
In the meantime, changing the options in the unity8.conf file so that
MIR_SERVER_NBUFFERS=3 will correct affected images.
** Branch linked: lp:~mir-team/mir/nbs-off-1590765
--
You received this bug not
** Changed in: mir
Milestone: None => 0.23.1
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1590765
Title:
OSK flickers and buttons are sometimes invisble
Sta
** Also affects: mir
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1590765
Title:
OSK flickers and buttons are sometim
We did change some buffering operations in the mir 0.23.0 release. A good way
to test it would be to set
initctl set-env MIR_SERVER_NBUFFERS=3
in the unity8.conf upstart file.
If it goes away, we'll probably have to turn that option back off. (will
prepare a branch to that effect)
--
You recei
Might be worth trying again in 0.23.0.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1566747
Title:
Mir server with QtUbuntu client can cause system crash or Android GPU
dr
Another instance:
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/1221/consoleFull
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad
** Changed in: mir/0.23
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1584784
Title:
Using NBS, X apps under Unity8 need interacti
I targeted to 0.24, should probably have a look, especially if we're
getting error reports from the 'field'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1506358
Title:
libmi
If there's an issue in the transport in
mclr::MirProtobufRpcChannel::send_message during the sending of the
message, it will trigger the disconnection code.
If the client happens to be mid-mir_buffer_stream_swap_buffers at the
same time that the the connection error trips the disconnection
notific
Hmm, if the server isn't dying, perhaps we're getting a false
disconnection signal from the rpc code?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1506358
Title:
libmirclien
** Branch unlinked: lp:mir/0.23
--
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/1580774
Title:
mouse is getting stuck on a phantom edge
Status in Canonical
fix is wip, still testing... hope to get it out the door Tuesday (Monday
is US holiday)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1584784
Title:
With Mir 0.23.0, X apps u
** Changed in: qtmir
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1584784
Title:
With Mir 0.23.0, X apps under Unity8 need interaction to start
I didn't include an Xmir stack trace yesterday because it didn't appear
stuck, it was submitting buffers (black frames) repeatedly.
I compiled Xmir and added some logs. I caught swap_buffers blocking up
in Xmir (in the pocket desktop scenario only, seems to be a racy,
perhaps on how big the frame
seems matchbox is getting jammed trying to connect to the server too...
I'm guessing this is why the map/realize isn't happing.
** Attachment added: "matchbox.txt"
https://bugs.launchpad.net/mir/+bug/1584784/+attachment/4670915/+files/matchbox.txt
--
You received this bug notification becaus
Its very difficult to get backtraces for X apps when running in pocket
desktop (had to rewrite puritine scripts to break out of confinement),
but got a bt from Xeyes when the problem is occurring; bt is attached.
** Attachment added: "xeyes.txt"
https://bugs.launchpad.net/mir/+bug/1584784/+att
Its also interesting that this only happens in pocket desktop mode. The
applications start up successfully when in phone-mode.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1584
Well, for some reason, this appears to be where the (gedit) window gets
realized in our existing release:
Atom _NET_WM_NAME = 267
Atom _NET_WM_WINDOW_TYPE = 295
Realize window 0xabaa7a98 "": 985x1093 +0+0 parent=0xab8dadc8
depth=24 redir=0 type=0 class=1 visibility=3 viewable=1
ove
also, havent been able to reproduce the behavior with the demo servers,
just qtmir+Xmir on pocket desktop (where its easy to reproduce)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/
I think it might be something going on with the focus causing the window
not to be realized (perhaps). I've checked that the buffers aren't
getting 'stuck'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https:/
right, which is a hybris bug, so 'incomplete' (or making this bug a dup
of 1578461) seems appropriate
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1537389
Title:
The Desktop
untargetted to mir milestones, as the problem is being fixed in hybris
** Changed in: mir
Milestone: 0.24.0 => None
** Changed in: mir/0.22
Milestone: 0.22.1 => None
** Changed in: mir/0.23
Milestone: 0.23.0 => None
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1579076 ***
https://bugs.launchpad.net/bugs/1579076
** This bug has been marked a duplicate of bug 1579076
Potential NBS performance loss after resize
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which i
** Changed in: mir
Milestone: 0.23.0 => 0.24.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1262116
Title:
Nested servers prevent overlays or fullscreen bypass from work
** Changed in: mir
Milestone: 0.23.0 => 0.24.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1570698
Title:
CI failure in TestClientInput.receives_one_touch_event_per_fra
** Changed in: mir
Milestone: 0.23.0 => 0.24.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1552371
Title:
Unexpected display on
Status in Canonical System Image:
C
** Changed in: mir
Status: In Progress => Triaged
** Changed in: mir
Milestone: 0.23.0 => 0.24.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1495974
Title:
[and
** Branch linked: lp:~kdub/mir/avert-1563287
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1563287
Title:
[regression] [OTA-10] Spread animation stutters badly with only a fe
@duflu, If you're testing with rev3297 you're likely to see the same
sort of slowdown on arale. We disabled the fences in arale in 0.20.1, so
our current images, as well as trunk should be fine (with this bug) on
arale by now.
--
You received this bug notification because you are a member of Ubun
arale should not be using egl sync fences.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1563287
Title:
[regression] [OTA-10] Spread animation stutters badly with only a few
@we can live without the synchronization...
This was the suggestion to roll back the use of the sync extensions on mali.
The current plan is to see how far we can get with hybris before OTA-11, and if
we can't fix the performance in time, we'll roll back the sync extensions.
The synchronization
Its looking like the use of the eglCreateImageSyncKHR extension is causing
thread activity (creation/destruction/TLS).
Once mir started using these functions, it caused this timing increase in Mali
cores, and lp: #1524414 in powervr ones. Linked to hybris, as its looking like
this is a hybris/g
** Also affects: libhybris
Importance: Undecided
Status: New
--
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/1563287
Title:
[regression] [OTA-10] Spread animation
Delving a bit deeper, it seems that we're wasting a fair amount of time
in the mali driver during this operation with threading operations,
including some calls to pthread_getspecific (ie, TLS), so it could be a
cost of hybris
--
You received this bug notification because you are a member of Ubun
So to restate simply, the egl synchronization is costing 500us/client.
(which is unreasonable, but a cost we cannot control without MTK/arm
help). Trying to figure out alternatives.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
bit of measuring... the increase seems to average ~500us per map
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1563287
Title:
[regression] [OTA-10] Spread animation stutters
** Changed in: location-service (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1371146
Title:
packaging bug in
** Changed in: mir
Assignee: Kevin DuBois (kdub) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1488232
Title:
server shutdown failure (segfault)
Sta
The 'buffering/GL' logic changes were installation of EGL sync points
during GL draws so that software clients (eg, Xmir) have synchronized
buffer releases. (fix https://bugs.launchpad.net/mir/+bug/1517205).
Poking around this today, it seems that the actual installation of the
sync points has som
Don't actually know of a currently supported device that does this. I
suppose this is in progress with the NBS transition.
** Changed in: mir
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribe
Can be managed more easily with NBS, might be worth working on post 0.23
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1495974
Title:
[android] renogotiation of pixel formats
So, it seems logging the problem and not throwing is an acceptable
solution, although IMO, it merits further investigation as to why the
driver is generating this error during certain scenarios. Will propose
attached branch to lp:mir, and its looking like it'll ride along in
0.20.3 mir release.
**
Was able to do a bit of remote debugging with mzanetti today, latest attempt
packages are here:
https://private-fileshare.canonical.com/~kdub/mir-debs-1554635-attempt3.tar.gz
Seems the driver is failing with EGL_BAD_ALLOC when trying to install
the sync point. Possibly a resource leak, or a loss
debs are at https://private-fileshare.canonical.com/~kdub/mir-
debs-1554635.tar.gz. The subdirectory android-mir-1554635 contains the
debs needed by the phone for the upgrade.
Also, can I see the dmesg and /system/bin/logcat logs from when the
crash occurs? Seeing if the driver is logging errors
Attached a branch that will at least ignore the exception. Without being
able to reproduce myself (mir team doesn't have a turbo) or without
seeing dmesg and logcat, its hard to tell if masking the exception is an
appropriate response. Best guess though with information at this point
in time is tha
@Lorn, could you collect the logs from /system/bin/logcat and dmesg when
this happens? This would help figure out if its a resource leak or some
other transient driver problem that we could potentially fix or ignore.
--
You received this bug notification because you are a member of Ubuntu
Touch s
which device? can a dmesg and logcat be attached? how many contacts are
necessary?
This could be a system resource exhaustion issue.
--
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.ne
** Changed in: mir/0.20
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1544878
Title:
Mir servers crash if I press the side mouse
1 - 100 of 239 matches
Mail list logo