Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 665076 - media-libs/mesa-18.2.0_rc5 breaks xfwm4 with "assertion failed" on intel i965
Summary: media-libs/mesa-18.2.0_rc5 breaks xfwm4 with "assertion failed" on intel i965
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal major (vote)
Assignee: Gentoo X packagers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-01 23:09 UTC by Barteks2x
Modified: 2018-09-15 15:36 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Output of emerge --info (emerge-info,17.47 KB, text/plain)
2018-09-01 23:09 UTC, Barteks2x
Details
Mesa-9999 default log (mesa-9999_default.log.tar.gz,143.23 KB, application/gzip)
2018-09-04 18:37 UTC, Maxime Lombard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Barteks2x 2018-09-01 23:09:50 UTC
Created attachment 545752 [details]
Output of emerge --info

When using latest (18.2.0_rc5) mesa, xfwm4 quits with the following messages:


** (xfwm4:16055): WARNING **: 18:36:46.336: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(xfwm4:16055): xfwm4-WARNING **: 18:36:59.554: Failed to connect to session manager: Failed to connect to the session manager: SESSION_MANAGER environment variable not defined
xfwm4: ../mesa-18.2.0-rc4/src/mesa/drivers/dri/i965/intel_mipmap_tree.c:1285: intel_miptree_match_image: Assertion `image->TexObject->Target == mt->target' failed.


Mesa 18.1.6 (stable) works fine. This is most likely the same issue as this: https://bugs.freedesktop.org/show_bug.cgi?id=107117, but even using mesa version 9999 doesn't fix the issue.

I didn't test earlier ~amd64 versions, but it's very likely to also occur on some earlier versions.
Comment 1 Matt Turner gentoo-dev 2018-09-04 18:22:49 UTC
Thanks for the report.

If you wouldn't mind, please file a bug upstream https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa&component=Drivers/DRI/i965 and link it here in the URL field.

Also, please attach a build log of Mesa and tell us what xorg-server version are you using. Are you using xf86-video-intel (discouraged) or the built-in modesetting driver (recommended)?
Comment 2 Maxime Lombard 2018-09-04 18:37:07 UTC
Created attachment 545932 [details]
Mesa-9999 default log

Hello Matt,

I think i know why Barteks2x has an assertion because i have the same thing with Assassin's Creed : Syndicate when i launch it with Wine-Staging + DXVK, see : https://bugs.freedesktop.org/show_bug.cgi?id=107727

In fact, even if "debug" USE flag is not enabled, Mesa is compiled with debug mode. I attach the default mesa-9999 log and you can see this line :

"-Wall -Werror=implicit-function-declaration -Werror=missing-prototypes -fno-math-errno -fno-trapping-math -Wno-missing-field-initializers -fPIC -pthread -Werror=pointer-arith -Werror=vla -fvisibility=hidden -O2 -pipe -march=native -MD -MQ 'src/util/src@util@@mesa_util@sta/debug.c.o' -MF 'src/util/src@util@@mesa_util@sta/debug.c.o.d' -o 'src/util/src@util@@mesa_util@sta/debug.c.o' -c ../mesa-9999/src/util/debug.c"

It seems that since Mesa is build with Meson, this line in the ebuild has not effect :
"--buildtype $(usex debug debug plain)"

If i modify the ebuild, comment the previous line and add this :
"	if ! use debug; then
             emesonargs+=( -D b_ndebug=true )
	fi
"

Mesa is not build with debug mode and my game works correctly.

Cheers,
Maxime
Comment 3 Barteks2x 2018-09-15 08:20:24 UTC
The issue appears to be fixed in mesa 9999 now.