1:43 p.m.
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
Bug ID: 1478536
Summary: Blender warnings "X server found. dri2 connection
failed!"
Product: Fedora
Version: 26
Component: blender
Severity: medium
Assignee: luya_tfz(a)thefinalzone.net
Reporter: alex(a)malexmedia.net
QA Contact: extras-qa(a)fedoraproject.org
CC: design-devel(a)lists.fedoraproject.org,
hobbes1069(a)gmail.com, jochen(a)herr-schmitt.de,
kwizart(a)gmail.com, luya_tfz(a)thefinalzone.net,
negativo17(a)gmail.com, promac(a)gmail.com
Description of problem:
When launching Blender, after switching the rendering engine to "Cycles
Render", the terminal displays a large number of errors and warnings:
---- SNIP ----
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
---- SNIP ----
Version-Release number of selected component (if applicable):
blender-2.78c-4.fc26.x86_64
How reproducible:
Every time.
Steps to Reproduce:
1. Launch /usr/bin/blender from within Terminal
2. Switch to "Cycles Render" in upper-right drop down.
3. Observe "dri2 connection failed" error messages repeated several times.
Actual results:
Blender complains over and over that it cannot connect to DRI.
Expected results:
Blender should be able to establish appropriate connections to DRI.
Additional info:
This issue is only reproducible within Wayland. Under Xorg, this issue is not
present.
--
You are receiving this mail because:
You are on the CC list for the bug.
2:38 p.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
--- Comment #1 from Nicolas Chauvet (kwizart) <kwizart(a)gmail.com> ---
(In reply to Alex Markley from comment #0)
Description of problem:
When launching Blender, after switching the rendering engine to "Cycles
Render", the terminal displays a large number of errors and warnings:
---- SNIP ----
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
---- SNIP ----
This doesn't seems a good start for using blender on such hw
environmment.
Can you please report which hardware is this, Desktop environment and if using
Wayland or Xorg ?
--
You are receiving this mail because:
You are on the CC list for the bug.
7:57 a.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
--- Comment #2 from Alex Markley <alex(a)malexmedia.net> ---
Sorry for missing those basic stats.
Uname: Linux obsidian.malexmedia.net 4.11.11-300.fc26.x86_64 #1 SMP Mon Jul 17
16:32:11 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
CPU: Intel® Core™ i7-7500U CPU @ 2.70GHz × 4
RAM: 16GB
Integrated GPU: Intel® HD Graphics 620 (Kaby Lake GT2)
Discrete GPU: NVIDIA Corporation GM107M [GeForce GTX 950M] (rev a2)
I'm using Gnome, and the problem only occurs on Wayland. On Xorg, the errors do
not appear.
I should say also that this issue did *not* appear in FC25 on the same
hardware.
--
You are receiving this mail because:
You are on the CC list for the bug.
3:04 p.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
Luya Tshimbalanga <luya(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alex(a)malexmedia.net,
| |luya(a)fedoraproject.org
Flags| |needinfo?(alex(a)malexmedia.n
| |et)
--- Comment #3 from Luya Tshimbalanga <luya(a)fedoraproject.org> ---
(In reply to Alex Markley from comment #2)
Sorry for missing those basic stats.
Uname: Linux obsidian.malexmedia.net 4.11.11-300.fc26.x86_64 #1 SMP Mon Jul
17 16:32:11 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
CPU: Intel® Core™ i7-7500U CPU @ 2.70GHz × 4
RAM: 16GB
Integrated GPU: Intel® HD Graphics 620 (Kaby Lake GT2)
Discrete GPU: NVIDIA Corporation GM107M [GeForce GTX 950M] (rev a2)
I'm using Gnome, and the problem only occurs on Wayland. On Xorg, the errors
do not appear.
I should say also that this issue did *not* appear in FC25 on the same
hardware.
I failed to reproduce the bug with the hybrid laptop ASUS X550ZE featuring:
Integrated GPU: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R6
Graphics]
Dedicated GPU: Advanced Micro Devices, Inc. [AMD/ATI] Jet PRO [Radeon R5 M230]
The issues seems a regression related to the nouveau driver on Wayland
session. Try to run "DRI_PRIME=1 blender" to use Nvidia and blender for Intel
HD in the terminal and submit the result.
--
You are receiving this mail because:
You are on the CC list for the bug.
8:53 p.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
Alex Markley <alex(a)malexmedia.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(alex(a)malexmedia.n |
|et) |
--- Comment #4 from Alex Markley <alex(a)malexmedia.net> ---
(In reply to Luya Tshimbalanga from comment #3)
The issues seems a regression related to the nouveau driver on
Wayland
session.
I would agree with this assessment, since everything was working previously.
All I did was a dnf system upgrade.
Try to run "DRI_PRIME=1 blender" to use Nvidia and blender
for
Intel HD in the terminal and submit the result.
To confirm, this is the result of using DRI_PRIME in my environment:
---- SNIP ----
[alex@obsidian ~]$ glxinfo | egrep 'renderer string|direct rendering'
direct rendering: Yes
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2)
[alex@obsidian ~]$ DRI_PRIME=1 glxinfo | egrep 'renderer string|direct
rendering'
direct rendering: Yes
OpenGL renderer string: Gallium 0.4 on NV117
[alex@obsidian ~]$
---- SNIP ----
Unfortunately, DRI_PRIME=1 has no positive impact on this issue with Blender:
---- SNIP ----
[alex@obsidian ~]$ DRI_PRIME=1 /usr/bin/blender
Read new prefs: /home/alex/.config/blender/2.78/config/userpref.blend
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
Saved session recovery to '/tmp/quit.blend'
Blender quit
[alex@obsidian ~]$
---- SNIP ----
I should note that I have not observed any *functional* issues associated with
these warnings, except delays during startup.
(I should also note that glxgears reports no issues with direct rendering on
either GPU.)
--
You are receiving this mail because:
You are on the CC list for the bug.
9:54 p.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
Luya Tshimbalanga <luya(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |needinfo?(alex(a)malexmedia.n
| |et)
--- Comment #5 from Luya Tshimbalanga <luya(a)fedoraproject.org> ---
Backup your user preference somewhere then delete it to use the default:
/home/alex/.config/blender/2.78/config/userpref.blend
Start blender both way including with DRI_PRIME=1. Should both method fail, let
assign the issue to nouveau driver for further debugging.
--
You are receiving this mail because:
You are on the CC list for the bug.
7:33 p.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
Alex Markley <alex(a)malexmedia.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(alex(a)malexmedia.n |
|et) |
--- Comment #6 from Alex Markley <alex(a)malexmedia.net> ---
After deleting userpref.blend, here were the results:
---- SNIP ----
[alex@obsidian RenderTemp]$ /usr/bin/blender
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
Blender quit
[alex@obsidian RenderTemp]$
---- SNIP ----
And with DRI_PRIME...
---- SNIP ----
[alex@obsidian RenderTemp]$ DRI_PRIME=1 /usr/bin/blender
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
X server found. dri2 connection failed!
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
Blender quit
---- SNIP ----
--
You are receiving this mail because:
You are on the CC list for the bug.
11:49 p.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
Luya Tshimbalanga <luya(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |ofourdan(a)redhat.com,
| |xgl-maint(a)redhat.com
Component|blender |xorg-x11-server
Assignee|luya_tfz(a)thefinalzone.net |xgl-maint(a)redhat.com
--- Comment #7 from Luya Tshimbalanga <luya(a)fedoraproject.org> ---
Thank you for testing. Let's assign the issue to xorg as the issue seems
affecting hybrid graphic hardware Intel+Nvidia.
--
You are receiving this mail because:
You are on the CC list for the bug.
4:58 p.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
Luya Tshimbalanga <luya(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |needinfo?(alex(a)malexmedia.n
| |et)
--- Comment #8 from Luya Tshimbalanga <luya(a)fedoraproject.org> ---
Hi Alex,
Blender 2.79 is just released. Could you test if the issue get resolved on your
hardware?
Thanks.
--
You are receiving this mail because:
You are on the CC list for the bug.
4:11 p.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
Sergey Bostandzhyan <jin(a)deadlock.dhs.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jin(a)deadlock.dhs.org
--- Comment #9 from Sergey Bostandzhyan <jin(a)deadlock.dhs.org> ---
I seem to have a similar issue, but I have an old ATI card:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
RV635/M86 [Mobility Radeon HD 3650]
Until recently it was working fine, but today I tried with
blender-2.79-1.fc26.x86_64 and I do see a lot of those errors in the console:
DRM_IOCTL_I915_GEM_APERTURE failed: No such file or directory
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: No such file or directory
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
cl_get_gt_device(): error, unknown device: 0
DRM_IOCTL_I915_GEM_APERTURE failed: No such file or directory
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: No such file or directory
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
cl_get_gt_device(): error, unknown device: 0
DRM_IOCTL_I915_GEM_APERTURE failed: No such file or directory
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [22]
param: 4, val: 0
cl_get_gt_device(): error, unknown device: 0
Seems to be repeating.
If I maximize the blender window, then it becomes unusable - the screen starts
flickering and some areas get corrupted, I see bitmaps from other applications
showing up in there; actually I managed to take a screenshot (see attachment).
When I go back to the window size that blender started with, the screen errors
disappear.
Last time I tried was about a month ago and I did not experience such problems
and could work with blender in a maximized window.
--
You are receiving this mail because:
You are on the CC list for the bug.
4:13 p.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
--- Comment #10 from Sergey Bostandzhyan <jin(a)deadlock.dhs.org> ---
Created attachment 1339469
--> https://bugzilla.redhat.com/attachment.cgi?id=1339469&action=edit
screenshot of the corrupt blender screen
The image shows corruption in the blender screen, this happens when the mouse
is being moved around in blender that is running in a maximized window.
--
You are receiving this mail because:
You are on the CC list for the bug.
4:14 p.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
--- Comment #11 from Sergey Bostandzhyan <jin(a)deadlock.dhs.org> ---
I forgot to mention that I am running xorg-x11-server-Xorg-1.19.3-4.fc26.x86_64
and the MATE window manager.
--
You are receiving this mail because:
You are on the CC list for the bug.
4:31 p.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
--- Comment #12 from Sergey Bostandzhyan <jin(a)deadlock.dhs.org> ---
...and I was too early to say that it works in non-maximized window mode,
unfortunately it doesn't :( It just does not corrupt using bitmaps of foreign
applications, instead it messes up itself. It seems that anything related to
tooltips/highliting is causing problems, i.e. when I hover the mouse over
various buttons parts of the screen start to flicker and draw incorrectly.
--
You are receiving this mail because:
You are on the CC list for the bug.
4:49 p.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
--- Comment #13 from Sergey Bostandzhyan <jin(a)deadlock.dhs.org> ---
Sorry for the "spam", one more note: I reviewed my update history and the most
recent relevant changes was an update of mesa libraries from 17.1.7 to 17.2.2.
Unfortunately dnf did not allow me to undo or rollback (it was always saying
that some packages were no longer available), so I was not able to retest
against the mesa version before the update, but suspect that the problem is
related to the new version.
--
You are receiving this mail because:
You are on the CC list for the bug.
5:25 p.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
Luya Tshimbalanga <luya(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ajax(a)redhat.com
Component|xorg-x11-server |wayland
Assignee|xgl-maint(a)redhat.com |ajax(a)redhat.com
--- Comment #14 from Luya Tshimbalanga <luya(a)fedoraproject.org> ---
Lets assign to wayland as it happened the bugs occurred at that component.
--
You are receiving this mail because:
You are on the CC list for the bug.
7:53 a.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
--- Comment #15 from Olivier Fourdan <ofourdan(a)redhat.com> ---
(In reply to Luya Tshimbalanga from comment #14)
Lets assign to wayland as it happened the bugs occurred at that
component.
"wayland" is not a server of any sort, it's more of an ipc library, so it
is
very unlikely the issue is in "wayland".
The issue is either in blender, xorg-x11-server or mesa, but not in wayland.
--
You are receiving this mail because:
You are on the CC list for the bug.
8:10 a.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
--- Comment #16 from Olivier Fourdan <ofourdan(a)redhat.com> ---
Seems that error is coming from beignet's libcl.so
--
You are receiving this mail because:
You are on the CC list for the bug.
8:14 a.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
Olivier Fourdan <ofourdan(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ignatenko(a)redhat.com
Component|wayland |beignet
Assignee|ajax(a)redhat.com |ignatenko(a)redhat.com
--- Comment #17 from Olivier Fourdan <ofourdan(a)redhat.com> ---
Here:
https://github.com/intel/beignet/blob/master/src/intel/intel_driver.c#L219
--
You are receiving this mail because:
You are on the CC list for the bug.
9:47 a.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
--- Comment #18 from Sergey Bostandzhyan <jin(a)deadlock.dhs.org> ---
Please note that in my log output I do not have the dri error line, instead I
have "cl_get_gt_device(): error, unknown device: 0". This is the only
difference between my log and the log from Alex, of course I can't tell if it
originates from the same problem.
I tried to downgrade beignet to 1.3.1-2.fc26.x86_64 from
1.3.1-3.git20170622.36f6a8b.fc26, but this did not make any difference with
blender.
I tried to downgrade blender itself via dnf downgrade, but was not able to run
it, the older version did not start because of some unresolved symbol.
--
You are receiving this mail because:
You are on the CC list for the bug.
1:45 p.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
--- Comment #19 from Sergey Bostandzhyan <jin(a)deadlock.dhs.org> ---
I updated to Fedora 27 and the issue is still there. So basically, blender
became unusable on Fedora on some configurations over half a year ago and
nothing has changed :(
Can I do anything to speed up the fix, do you need more log or more testing?
--
You are receiving this mail because:
You are on the CC list for the bug.
12:35 a.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
--- Comment #20 from Luya Tshimbalanga <luya(a)fedoraproject.org> ---
(In reply to Sergey Bostandzhyan from comment #19)
I updated to Fedora 27 and the issue is still there. So basically,
blender
became unusable on Fedora on some configurations over half a year ago and
nothing has changed :(
Can I do anything to speed up the fix, do you need more log or more testing?
That would be nice.
--
You are receiving this mail because:
You are on the CC list for the bug.
3:11 a.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
--- Comment #21 from Fedora End Of Life <jkurik(a)fedoraproject.org> ---
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
of '26'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
6:54 a.m.
New subject: [Bug 1478536] Blender warnings "X server found. dri2 connection
failed!"
https://bugzilla.redhat.com/show_bug.cgi?id=1478536
Fedora End Of Life <jkurik(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |CLOSED
Resolution|--- |EOL
Last Closed| |2018-05-29 07:54:28
--- Comment #22 from Fedora End Of Life <jkurik(a)fedoraproject.org> ---
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.
Thank you for reporting this bug and we are sorry it could not be fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
2160
days inactive
2458
days old
design-devel@lists.fedoraproject.org
22 comments
1 participants
participants (1)
-
bugzilla＠redhat.com