Bug 89019 - [NV30/Gallium] Black texture using Qt5
Summary: [NV30/Gallium] Black texture using Qt5
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/nouveau (show other bugs)
Version: 10.4
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: Nouveau Project
QA Contact: Nouveau Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-07 11:37 UTC by Andrea Scarpino
Modified: 2019-09-18 20:39 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Screenshot of Plasma 2 (29.49 KB, image/png)
2015-02-07 11:37 UTC, Andrea Scarpino
Details

Description Andrea Scarpino 2015-02-07 11:37:46 UTC
Created attachment 113241 [details]
Screenshot of Plasma 2

Hi there,
I don't know where to start because I just migrated to Plasma 2 and got this black texture (see attachment).

Everything is fine using Qt4, so I suppose this could be a Qt issue? But then I used vesa as Xorg driver and the texture is painted correctly.
The same black texture is used in SDDM too, which is also a Qt5 application.

Any idea on where to start?

NVIDIA FX 5500, Xorg 1.16.3, mesa 10.4.4, nouveau 1.0.11, Qt 5.4.0
Comment 1 Andrea Scarpino 2015-02-28 08:39:50 UTC
(In reply to Andrea Scarpino from comment #0)
> NVIDIA FX 5500, Xorg 1.16.3, mesa 10.4.4, nouveau 1.0.11, Qt 5.4.0

Still the same with Xorg 1.17.1, mesa 10.4.5, Qt 5.4.1
Comment 2 Ilia Mirkin 2015-02-28 23:08:08 UTC
The thing immediately coming to mind was the workaround I added for dealing with mismatching color/depth render targets. The "fix" was to just not render to depth at all, but that may mess up other things of course. (Not the least of which is that the depth texture will remain untouched.)

To start, you should get an apitrace (https://github.com/apitrace/apitrace) of the failing application. This should help determine what's going on. Make a debug mesa build and see if the driver outputs any "aaaah, i don't know how to handle this" type messages.
Comment 3 GitLab Migration User 2019-09-18 20:39:57 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1070.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.