← Back to team overview

desktop-packages team mailing list archive

[Bug 1504387] Re: [regression] Software client windows appear all-black on wily desktop

 

Launchpad has imported 15 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=92265.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2015-10-03T02:36:50+00:00 Calezoj wrote:

Description:
After update mesa from 11.0.1-1 to 11.0.2-1 in Weston (launched from the console or 'X') all the windows black (see screenshot: https://i.imgur.com/Oe5X0en.png). After downgrading mesa package weston work fine.

Additional info:
* Problem mesa version: 11.0.2-1
* Weston 1.9
* Weston running from the 'X': http://pastebin.com/jksF4DT4
* ArchLinux
* Intel I4700HQ + Intel Graphics HD 4600 + NVIDIA 850m

Assumption:
I think that to blame the following correction in mesa:
http://mesa3d.sourceforge.net/relnotes/11.0.2.html
> i965: Respect stride and subreg_offset for ATTR registers

Reply at: https://bugs.launchpad.net/mir/+bug/1504387/comments/0

------------------------------------------------------------------------
On 2015-10-03T11:59:57+00:00 Stu-dby wrote:

My mesa snapshot happened to have the commit mentioned above, but weston
was okay. Updated mesa to current HEAD, and the problem described
happened.

Reverting 5edd996 (mesa: Use the effective internal format instead for
validation) helps, so it should be the problematic commit.

Reply at: https://bugs.launchpad.net/mir/+bug/1504387/comments/1

------------------------------------------------------------------------
On 2015-10-03T15:21:44+00:00 2-jason-v wrote:

There appear to be two potential problems here.  One is that Weston
tries to use GL_EXT_abgr in ES even though it is not an ES extension.
The second is that mesa advertises it and then falls over when you try
to use it.  If we weren't advertising it, Weston would fall back to
other paths and be OK.  I see two options:

 1) Actually support the extension even though it isn't technically an ES extension.
 2) Stop advertising it.

I'm going to hazard a guess and say that mesa is probably the only ES
driver to support GL_EXT_abgr.

Thoughts?

Reply at: https://bugs.launchpad.net/mir/+bug/1504387/comments/2

------------------------------------------------------------------------
On 2015-10-03T15:41:27+00:00 Emil-l-velikov wrote:

(In reply to Jason Ekstrand from comment #2)
> I'm going to hazard a guess and say that mesa is probably the only ES driver
> to support GL_EXT_abgr.
> 
Sounds about right according to ilia's glxinfo list

http://people.freedesktop.org/~imirkin/glxinfo/

Reply at: https://bugs.launchpad.net/mir/+bug/1504387/comments/3

------------------------------------------------------------------------
On 2015-10-04T03:33:19+00:00 Michel-daenzer wrote:

*** Bug 92242 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/mir/+bug/1504387/comments/4

------------------------------------------------------------------------
On 2015-10-04T14:14:02+00:00 Fabio-coatti wrote:

Spotted this report after bisecting :(

So, I can confirm the same behaviour under kde5/gentoo/qt-5.4.2: black
windows, and the commit that cause the problem seems to be

commit f15a7f3c6e1bb802ae8c2a29a2dc35ff530aea4d
Author: Eduardo Lima Mitev <elima@xxxxxxxxxx>
Date:   Thu Sep 24 10:57:43 2015 +0200

    mesa: Use the effective internal format instead for validation
[...]

Reply at: https://bugs.launchpad.net/mir/+bug/1504387/comments/5

------------------------------------------------------------------------
On 2015-10-05T06:52:59+00:00 Ppaalanen wrote:

*** Bug 92247 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/mir/+bug/1504387/comments/6

------------------------------------------------------------------------
On 2015-10-05T07:03:27+00:00 Ppaalanen wrote:

I don't think you mean GL_EXT_abgr, I don't see Weston using that.

Weston is using GL_BGRA_EXT format, when GL_EXT_texture_format_BGRA8888
extension is available. Weston's GL-renderer refuses to start without
this extension.

I believe this is because GL_BGRA_EXT, GL_UNSIGNED_BYTE matches the
WL_SHM_FORMAT_XRGB8888 and WL_SHM_FORMAT_ARGB8888 layouts, so we can
avoid a conversion.

Reply at: https://bugs.launchpad.net/mir/+bug/1504387/comments/7

------------------------------------------------------------------------
On 2015-10-07T14:27:15+00:00 Emil-l-velikov wrote:

Eduardo, the faulty commit (breaking KDE/kwin and weston) has landed a
week+ ago. Will you have a chance to look into it soon ? Alternatively
I'll revert this for stable - 11.0.3 (coming in 2-3 days).

Reply at: https://bugs.launchpad.net/mir/+bug/1504387/comments/8

------------------------------------------------------------------------
On 2015-10-07T21:54:11+00:00 John Dulaney wrote:

Created attachment 118744
Stderr from running weston-launch

Also hitting something like this, black screen on weston-launch.  I
believe this may be the same thing?  Attaching stderr output for
verification.  I'm running on Centos 7, same versions of weston and mesa
I can build an older version of mesa if necessary to test.

Reply at: https://bugs.launchpad.net/mir/+bug/1504387/comments/9

------------------------------------------------------------------------
On 2015-10-07T22:58:46+00:00 2-jason-v wrote:

I just sent a patch to the list that fixes this bug:

http://lists.freedesktop.org/archives/mesa-dev/2015-October/096511.html

Reply at: https://bugs.launchpad.net/mir/+bug/1504387/comments/10

------------------------------------------------------------------------
On 2015-10-08T00:31:12+00:00 Elima-d wrote:

(In reply to Emil Velikov from comment #8)
> Eduardo, the faulty commit (breaking KDE/kwin and weston) has landed a week+
> ago. Will you have a chance to look into it soon ? Alternatively I'll revert
> this for stable - 11.0.3 (coming in 2-3 days).

I'm currently on holidays and away from my dev laptop until next
Tuesday. I will tell somebody from my team to keep an eye on this.

I took a quick look at Jason patch and it looks good. Thought I would
have preferred to avoid adding the check for GL_BGRA_EXT inside the
block that resolves the effective internal format. I wish there was a
way to do the same either inside _mesa_base_tex_format() or later down
in _mesa_es3_error_check_format_and_type. But I would need more time to
think on another way. So I would go ahead with that patch now.

Since I cannot test it here, I would let somebody else review it (if it
is not done already).

Sorry for the regression and the bad timing with me on holidays.

Reply at: https://bugs.launchpad.net/mir/+bug/1504387/comments/11

------------------------------------------------------------------------
On 2015-10-08T04:45:43+00:00 2-jason-v wrote:

I pushed the fix. Thanks to Ian for a quick review!

Reply at: https://bugs.launchpad.net/mir/+bug/1504387/comments/12

------------------------------------------------------------------------
On 2015-10-08T06:01:13+00:00 2-jason-v wrote:

*** Bug 92342 has been marked as a duplicate of this bug. ***

Reply at: https://bugs.launchpad.net/mir/+bug/1504387/comments/13

------------------------------------------------------------------------
On 2015-10-08T17:12:20+00:00 Mark-a-janes wrote:

No piglit, dEQP, or CTS tests indicated this regression.  However, a
major consumer of Mesa was debilitated due to this bug.

This bug cannot be marked fixed until there exists a piglit test which
prevents future regressions of this type.

Reply at: https://bugs.launchpad.net/mir/+bug/1504387/comments/14


** Changed in: mesa
       Status: Unknown => Confirmed

** Changed in: mesa
   Importance: Unknown => Critical

-- 
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/1504387

Title:
  [regression] Software client windows appear all-black on wily desktop

Status in Mesa:
  Confirmed
Status in Mir:
  Invalid
Status in mesa package in Ubuntu:
  Triaged

Bug description:
  [regression] Software client windows appear all-black, as of today on
  wily desktop.

  Although Mir has not changed. It seems like some other part of the OS
  is broken.

  $ sudo mir_proving_server &
  $ sudo mir_demo_client_progressbar

  The bug appeared in:
  mesa (11.0.2-1ubuntu3) wily; urgency=medium

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1504387/+subscriptions


References