Mir EGL platform is gone
** Changed in: mesa (Ubuntu)
Status: Triaged => Won't Fix
--
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/1560498
Title:
Unity8 using vmwgfx_d
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Changed in: canonical-devices-system-image
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in
** Tags added: unity8-desktop
--
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/1560498
Title:
Unity8 using vmwgfx_dri.so crashed in
mir::graphics::nested::detail::DisplayBuffe
No it doesn't seem to be the same issue. Thanks for looking though -- I
recall we copied the hack into another project but I haven't yet found
where that was.
Although removing the original hack from the Mir examples is trivial, I
suspect that's not actually the problem here because mir-demos shou
Or if not (I'm no graphics programmer), that's at least the comparable
snippet, I think?
--
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/1560498
Title:
Unity8 using vmwgfx_dri.
I *think* it looks like there's something similar going on inside QtMir
(http://bazaar.launchpad.net/~mir-
team/qtmir/trunk/view/head:/src/platforms/mirserver/screen.cpp#L60):
enum QImage::Format qImageFormatFromMirPixelFormat(MirPixelFormat
mirPixelFormat) {
switch (mirPixelFormat) {
cas
I chose Medium on the assumption that the only Mir code affected here
was a couple of examples (and that the real problem is Mesa bug
1480755). However the issue affecting Unity8 might be the same mistake
from the examples also made in real_kms_display_configuration.cpp and
elsewhere. So yeah that
can we please roll back the "importance" to high?
i think it meeets the criteria
High: A bug which fulfills any of the following criteria:
Has a severe impact on a small portion of Ubuntu users (estimated)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
nevertheless thanks for the progress on this one. lots of folks
requesting.
--
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/1560498
Title:
Unity8 using vmwgfx_dri.so crashed in
Dropped severity of the Mir tasks to medium since it's only eglapp.c
that's relevant there.
** Changed in: mir
Importance: High => Medium
** Changed in: mir (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Although possibly also real_kms_display_configuration.cpp in Mir is
wrong.
--
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/1560498
Title:
Unity8 using vmwgfx_dri.so crashed in
Thanks for your efforts Thomas.
I recall the cast from ARGB to XRGB is a workaround I did for Mesa bug
1480755.
** Changed in: mir
Status: New => Triaged
** Changed in: mesa (Ubuntu)
Status: Confirmed => Triaged
** Changed in: mir (Ubuntu)
Status: Confirmed => Triaged
--
OK, So I tried to debug this on 17.04 with the mir demos.
What happens is that while the Mir server seems to run fine,
when the EGL mir clients import a surface from the mir server (using fds /
prime) they
typecast the XRGB surface from the mir server to an ARGB surface, which the
svga gallium d
** Tags added: vm
--
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/1560498
Title:
Unity8 using vmwgfx_dri.so crashed in
mir::graphics::nested::detail::DisplayBuffer::make_curr
Yes it's worth getting them involved, although I should point out my own
more recent attempts to get Mir working properly under VMware were
unsuccessful for different reasons (never hit this bug). Either way,
VMware support needs a refresh...
--
You received this bug notification because you are
Guys, is it worth looping in Thomas Hellstrom
and/or Jakob Bornecrantz to this bug? IIRC they were
interested in getting the VMware driving working with Mir a while ago.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in
Status changed to 'Confirmed' because the bug affects multiple users.
** 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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs
Sorry, vmwgfx_dri.so actually belongs to Mesa.
binary package: libgl1-mesa-dri
source package: mesa
** Changed in: mir
Status: Invalid => New
** Changed in: mir (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
Digging into at least the latest 5 incidents, the crash is always from
vmwgfx_dri.so
So VMware's graphics driver is a problem. It should probably work better
than this already so I'm reluctant to make it a duplicate of bug
1118903.
** Summary changed:
- Unity8 crashed in
mir::graphics::nested::
Note that a solution to bug 1118903 would allow us to avoid the
offending vmwgfx_dri.so here.
--
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/1560498
Title:
Unity8 using vmwgf
20 matches
Mail list logo