Summary: | emulators/i386-wine-devel: broken since quite long time | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Slawomir Wojciech Wojtczak <vermaden> | ||||||||||
Component: | Individual Port(s) | Assignee: | Gerald Pfeifer <gerald> | ||||||||||
Status: | Closed Overcome By Events | ||||||||||||
Severity: | Affects Only Me | CC: | Alexander88207, gerald, grahamperrin, iwtcex | ||||||||||
Priority: | --- | ||||||||||||
Version: | Latest | ||||||||||||
Hardware: | amd64 | ||||||||||||
OS: | Any | ||||||||||||
URL: | https://www.freshports.org/emulators/i386-wine-devel/ | ||||||||||||
See Also: | https://reviews.freebsd.org/D32322 | ||||||||||||
Bug Depends on: | 259589 | ||||||||||||
Bug Blocks: | |||||||||||||
Attachments: |
|
Description
Slawomir Wojciech Wojtczak
2021-11-15 19:36:26 UTC
Hello Slawomir Wojciech Wojtczak, the i386-wine ports are now obsolete since the regular wine ports can now run both (i386 and amd64) at the same time. This port has already been requested for removal and only a few minor improvements are missing. https://reviews.freebsd.org/D32322 Please remove i386-wine and install emulators/wine or emulators/wine-devel. Sorry for your temporary disappointment. (In reply to Alexander Vereeken from comment #1) I now installed emulators/wine and then run these as advertised: % /usr/local/share/wine/pkg32.sh install wine mesa-dri % /usr/local/share/wine/pkg32.sh upgrade I get exactly the same results with emulators/wine version as described for the emulators/i386-wine-devel version in my first message here. Regards. Damjan, I'll be taking care of the removal of i386-wine-devel by tomorrow. It seems, however, the issues reported may not be specific to that, but also plain wine-devel (and WoW there)? How would you like to proceed with this report? Slawomir, how does WoW work for you with the wine-devel port? (In reply to Slawomir Wojciech Wojtczak from comment #2) Unfortunately i can not confirm your problem at the moment I also use emulators/wine and play various steam games mostly without problems which are not related to the port itself. You probably have regressions now since the i386 ports has hardly ever been updated since i took it over. Any chance to give a free example game that fails for you for testing? Does LD_32_LIBMAP="libgcc_s.so.1 /usr/lib32/libgcc_s.so.1" improve any of this? (In reply to Alex S from comment #5) Did not helped. Does black screen happen with software rendering (LIBGL_ALWAYS_SOFTWARE=1)? Does BD's sound issue persist with a fresh wineprefix? (In reply to Alex S from comment #7) Its exactly the same - no sound at BG - black screens at HoMM and CMR. Also the LIBGL_ALWAYS_SOFTWARE=1 did not changed anything - same behavior. (In reply to Alex S from comment #7) > Does BD's sound issue persist with a fresh wineprefix? * BG's I would also check the Audio tab in winecfg as well the volume settings in the game itself just in case. (In reply to Slawomir Wojciech Wojtczak from comment #8) > Also the LIBGL_ALWAYS_SOFTWARE=1 did not changed anything I'd appreciate a log with WINEDEBUG=+wgl for CMR2. (In reply to Alex S from comment #9) Yeah, should be BG indeed. I have sound in the CMR (in the intro movies) and in other non-3D games with WINE so audio works elsewhere. I triple checked in game settings for audio the its put to 'normal' hearable levels. Regards. Created attachment 229559 [details]
wine.log.xz
(In reply to Alex S from comment #10) Sure. Added here: https://bugs.freebsd.org/bugzilla/attachment.cgi?id=229559 Generated in that way: % cd ~/.wine/drive_c/Colin\ McRae\ Rally\ 2.0 % export WINEDEBUG=+wgl % wine explorer /desktop=name,800x600 CMR2.exe &> wine.log % xz -9 wine.log Regards. (In reply to Slawomir Wojciech Wojtczak from comment #13) I actually wanted a log with LIBGL_ALWAYS_SOFTWARE=1 specifically. I don't have a sufficiently old Intel GPU at hand, thus I have nothing to compare this with. Created attachment 229592 [details]
wine.LIBGL_ALWAYS_SOFTWARE.log.xz
(In reply to Alex S from comment #14) Sure. Attached here: https://bugs.freebsd.org/bugzilla/attachment.cgi?id=229592 Regards. (In reply to Slawomir Wojciech Wojtczak from comment #16) > 010c:err:winediag:wined3d_dll_init The GLSL shader backend has been disabled. You get to keep all the pieces if it breaks. That line looks moderately suspicious. Check Software\\Wine\\Direct3D and Software\\Wine\\AppDefaults registry keys. (In reply to Alex S from comment #17) Where exactly I can check that? (In reply to Slawomir Wojciech Wojtczak from comment #18) With regedit (comes with Wine). Created attachment 229595 [details]
wine-appdefaults.png
Created attachment 229596 [details]
wine-direct3d.png
(In reply to Alex S from comment #17) Here. Software\\Wine\\AppDefaults https://bugs.freebsd.org/bugzilla/attachment.cgi?id=229595 Software\\Wine\\Direct3D https://bugs.freebsd.org/bugzilla/attachment.cgi?id=229596 (In reply to Slawomir Wojciech Wojtczak from comment #22) Try disabling both those settings. Also find an OpenGL game (say, Quake 2 demo) and test that. (In reply to Alex S from comment #23) The Quake 2 demo test: https://www.mediafire.com/file/he1z3ykyk5zt68n/wine-quake-2-demo.mp4/file In short: - graphics (in SOFTWARE) seem to work (but sometimes jerky) - sound is broken and jerky (as you can hear) When I change VIDEO settings from SOFTWARE to DEFAULT OPENGL it hangs. There is some progress through ... After installing emulators/wine (6.0.2,1 currently) and installing 32bit wine version under ~/.i386-wine-pkg and starting with fresh ~/.wine dir I got following results: - Colin McRae Rally 2.0 - does not start at all now - Baldur's Gate I: EE - still no sound at all - Fallout 2 (GOG) - everything works along with proper sound - Heroes III: Complete - everything works along with proper sound The Quake 2 demo remains 'broken' as reported a post earlier. Not sure how that makes progress in this PR but just wanted to report it. This bug is a mix of various issues and upstream Wine has been moving in a direction that has been obsoleting the i386-wine-devel port (which has been removed nearly a year ago), so I believe the best course of action here is closing this issue here. For general issues I recommend filing a specific report upstream; if it is FreeBSD-specific, then here. Triage: assignment to the committer who closed the report. Thanks. |