Bug 92287

Summary:	Display errors in Qt applications after using Android Virtual Devices
Product:	Mesa	Reporter:	Guido Winkelmann <guido>
Component:	Drivers/DRI/nouveau	Assignee:	Nouveau Project <nouveau>
Status:	RESOLVED MOVED	QA Contact:	Nouveau Project <nouveau>
Severity:	major
Priority:	medium
Version:	11.0
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	Screenshot showing the problems dmesg output when the problem occured Xorg logfile from when the problem occured

Description Guido Winkelmann 2015-10-05 14:28:07 UTC

Created attachment 118670 [details]
Screenshot showing the problems

After using an Android Virtual Machine (from Android Studio, https://developer.android.com/sdk/index.html) and stopping it, Qt/KDE application will show weird display errors. Pixmaps get drawn poorly aligned or with parts of them corrupted or just not at all, some windows are translucent when they should not be, drop down menus are not drawn fully (some items do not get drawn, although the space for them is still reserved) and have horizontal bars, either black or of various weird colors, through them. Most applications affected by this become unusable. I will attach a screenshot that shows the problem.

Only Qt/KDE applications seem to be affected by this, as far as I can tell. Only applications that are newly started after this will be affected, not applications that have been running before but have opened new windows. When these problems start to happen, only restarting the computer seems to fix them, simply restarting the X server is not enough.

On two occasions so far, the problems were even worse: The X display froze completely, except for mouse movements, and I could no longer switch the keyboards NumLuck LED on or off by pressing Numlock. I had to reset the machine with a SysRq sequence.

This problem is not always reproducible, but seems to happen more often when running two AVDs simultaneously and then quitting them. The AVDs need to be configured to "Use Host GPU". I have not found any other way to reproduce this.

My system:

Gentoo Linux on x86_64
X server: xorg-server 1.17.2-r1
Display driver: 1.0.11
Mesa: 11.0.2
Kernel version: 4.2.2

This also happened with earlier versions of the X server and Mesa. I upgraded those after this problem first started,

Comment 1 Guido Winkelmann 2015-10-05 14:31:04 UTC

Created attachment 118671 [details]
dmesg output when the problem occured

Comment 2 Guido Winkelmann 2015-10-05 14:31:31 UTC

Created attachment 118672 [details]
Xorg logfile from when the problem occured

Comment 3 Guido Winkelmann 2015-10-05 17:54:58 UTC

Correction:

It just happened again, and this time, even application that have been running the whole time are affected.

Comment 4 Ilia Mirkin 2015-10-05 18:04:13 UTC

Seems like something may have gotten overwritten (like the background texture was made to be fully transparent). Odd.

You might try with mesa-git -- there are a handful of patches on there that deal with resource lifetime issues, but I doubt it will do anything to resolve your problem.

Comment 5 Guido Winkelmann 2015-10-05 18:47:01 UTC

> You might try with mesa-git -- there are a handful of patches on there that deal with resource lifetime issues, but I doubt it will do anything to resolve your problem.

I've installed mesa git, and so far, it looks like that solves the reported problems, although sometimes they take a while to manifest. Will report back tomorrow.

Comment 6 Guido Winkelmann 2015-10-06 12:54:32 UTC

It looked good yesterday, but today the problem is back...

Comment 7 Guido Winkelmann 2015-10-06 13:42:44 UTC

One more addendum:

Since upgrading to mesa-git yesterday, the problem seems to randomly solve itself every once in a while, whereas before, it could only be solved by rebooting...

Comment 8 GitLab Migration User 2019-09-18 20:41:22 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/1086.

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.