Description of problem: (I'm running wine.i686 on top of a f17 x86_64 system.) After having installed a fresh f17 I noticed that some games that previously worked well under wine on f16 were having issues : err:winediag:X11DRV_WineGL_InitOpenglInfo Direct rendering is disabled, most likely your OpenGL drivers haven't been installed correctly (using GL renderer "Mesa DRI Mobile Intel\xc2\xae GM45 Express Chipset ", version "1.4 (2.1 Mesa 8.0.3)"). even if my system DOES direct rendering... So I looked at this : http://www.winehq.org/pipermail/wine-users/2010-February/067958.html it's like wine requires 32b versions of the mesa drivers. So I installed mesa-dri-drivers.i686 and hopefully tried a "export LIBGL_DRIVERS_PATH=/usr/lib/dri/" and... ourrah, my game was working. I'm not sure about if the path override is really needed, but shouldn't wine.i686 come with the mesa-dri-drivers.i686 package for 3D-things to work ? Just asking, thanks ! Romain.
*** Bug 827777 has been marked as a duplicate of this bug. ***
Does it work for you without exporting LIBGL_DRIVERS_PATH?
It does work without "export LIBGL_DRIVERS_PATH=blah" as soon as 32b mesa drivers are here
*** Bug 828195 has been marked as a duplicate of this bug. ***
This is actually not arch specific. We just require libGL in wine-core through build deps. The question is: Do we want to pull in dri for everyone even if the mesa-dri package does not support the specific hardware.
+1 Ran into this yesterday. This was an annoying issue because the error message is confusing, but does evetually lead one to the correct solution i.e. install the 32-bit mesa-dri package.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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.
*** Bug 892175 has been marked as a duplicate of this bug. ***
*** Bug 989515 has been marked as a duplicate of this bug. ***
wine-1.7.1-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/wine-1.7.1-2.fc19
Package wine-1.7.1-2.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing wine-1.7.1-2.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-15685/wine-1.7.1-2.fc19 then log in and leave karma (feedback).
wine-1.7.1-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 855673 has been marked as a duplicate of this bug. ***