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
** Tags added: mesa
--
You received this bug notification because you are a member of Desktop
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
Status in Mir:
** Changed in: mir
Milestone: 0.24.0 => 0.25.0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1506358
Title:
libmirclient gives up and terminates prematurely with
** Changed in: mir/0.23
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1584784
Title:
Using NBS, X apps under Unity8 need interaction
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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1506358
Title:
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
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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1506358
Title:
libmirclient
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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1584784
Title:
With Mir 0.23.0, X apps
** Changed in: qtmir
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1584784
Title:
With Mir 0.23.0, X apps under Unity8 need interaction to start in
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
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"
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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1584784
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
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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
** Changed in: mir
Status: Fix Committed => Fix Released
** Changed in: canonical-pocket-desktop
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
** Changed in: mir
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/124440
Title:
[enhancement] Ubuntu needs a way to set
** Changed in: mir/0.18
Status: Fix Committed => Fix Released
** Changed in: mir
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1526209
So my problem noted in #8 was just a mis-match of packages on my system.
Cannot reproduce with xenial + silo 021, nor with on-system builds of
lp:mir, lp:mir/0.18, or lp:mir/0.17.
After standup today, it seems like we weren't able to reproduce the
problem, provided that we had updated systems,
Haven't been able to confirm this specific scenario today, but another
issue (not a crash, rather incorrect platform loading) was noticed
related to rev 3098. Seems best to back out that rev for lp:mir and
lp:mir/0.18 release.
--
You received this bug notification because you are a member of
hmm, and now after doing a reinstall and upgrade of all packages (on
xenial), I can no longer reproduce the issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1526209
Title:
seems to be mesa-specific
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1526209
Title:
[regression] Clients of nested Mir servers silently crash/exit
instantly
Status in Mir:
** Branch linked: lp:~mir-team/mir/revert-3098
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1526209
Title:
[regression] Clients of nested Mir servers silently crash/exit
instantly
I also can see the nested server crash scenario when connecting
mir_demo_client_egltriangle. I haven't seen the client crash yet
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1526209
** Branch linked: lp:~kdub/mir/fix-1406725
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1406725
Title:
Severe graphical corruption (mostly horizontal streaks/lines) running
Testing the EGLSyncFence extensions with xmir still has some corruption.
Using these extensions stabilizes the mir_demo_client_flicker rendering.
So, its looking like there's two problems going on here.
--
You received this bug notification because you are a member of Desktop
Packages, which is
So, we have two issues in this bug.
1) The majority of the xmir corruption was caused by calling
mir_buffer_stream_get_graphics_region() when xmir wanted to know the
buffer size. On android, this would call down into gralloc, and
invalidate/flush the cache when called. Its reasonable to just call
my spike branch that averts the problem is here, based on 0.17.1:
lp:~kdub/mir/0.17.1-fix-1406725
This branch doesnt have unit tests, and needs a bit more work on the new
internal interfaces, so I'll probably have to rework the branch to get it to
land in lp:mir.
** Branch linked:
After today's investigation, I think the cachelines that are appearing
as corruption are not from an lines that should have been invalidated,
but are the flushed lines from the next frame. IE, we're releasing the
buffer too early, and the flushed lines from the backbuffer render are
appearing as
The corruption appears on krillin too, so probably not a specific
chipset problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1406725
Title:
Severe graphical corruption
glFinish and other flushing-commands (eg, eglClientWaitSyncKHR with the
flush bit) seem to be other alternatives that work, but those aren't
very good alternatives either.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in
Its seeming like the gpu-facing cache is the one that needs invalidation
from the GL/gralloc driver, but is not being flushed. This is a CPU/GPU
coordination issue, and the GPU-based scenarios all work through the
same cache and do not experience this problem. If we use overlays, this
is not an
A (bad) workaround is to map the buffer server-side, and then use
glTexImage2D (instead of glTargetTexture2D)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1406725
Title:
Severe
I've been able to trace the calls down into the kernel, and it does look
like the kernel is flushing the cache at the appropriate time before
sending the buffer back to the client.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Changed in: mir
Assignee: (unassigned) => Kevin DuBois (kdub)
** Changed in: mir
Milestone: None => 0.18.0
** Changed in: mir
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xo
re:
Should we be concerned about this?...
no, these comments are a bit stale
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1406725
Title:
Severe graphical corruption (mostly
The problem looks like a cpu cache problem.
We call gralloc's unlock function, and digging through the gralloc code, it
looks like the internal native buffer flag that should trigger a cache flush is
behaving properly. Now seeing what I can find out in the kernel
--
You received this bug
Just for clarity's sake, INTEL_DEBUG=sync doesn't seem to make any
difference, but nbuffers=3 seems to avert the problem
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1377872
Title:
I see the same symptoms on my intel system. The easiest way to reproduce
the systems for me is to have a host (in bypass mode, with nbuffers=2),
a nested server (with nbuffers = 2 or nbuffers = 3), and then run
eglplasma connected to the nested server.
If egltriangle is running, the host server
** Changed in: mir
Milestone: 0.12.0 = 0.13.0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1417581
Title:
[regression] USC - mouse cursor on AMD graphics is drawing incorrectly
we should move include/shared/mir_toolkit/mesa/native_display.h
somewhere upstream, to mesa.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1192908
Title:
Mir/Mesa packaging have a
42 matches
Mail list logo
