September 2018 - Wine-Bugs - list.winehq.org

[Bug 42368] New: Lichdom: Battlemage crashes while loading when starting a new game
by wine-bugs＠winehq.org Jan. 9, 2022

Jan. 9, 2022

https://bugs.winehq.org/show_bug.cgi?id=42368 Bug ID: 42368 Summary: Lichdom: Battlemage crashes while loading when starting a new game Product: Wine-staging Version: 2.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fjfrackiewicz(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 57149 --> https://bugs.winehq.org/attachment.cgi?id=57149 Screenshot just before starting the game (For the non-Staging bug, please see bug 40428. I hope my submitting this report to Wine Staging is OK because I can only get this crash while running the game in Wine Staging 2.0) When attempting to run Lichdom: Battlemage in Wine Staging 2.0, the game crashes during the loading screen when starting a new game. I am attempting to play the game in a WoW64 prefix with vcrun2012 installed by the game's installer in Windows 7 mode (the game does not support Windows XP) and I am running the 64-bit binary for the game. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 19

[Bug 43850] New: Wine error with newest mesa driver
by wine-bugs＠winehq.org Jan. 9, 2022

Jan. 9, 2022

https://bugs.winehq.org/show_bug.cgi?id=43850 Bug ID: 43850 Summary: Wine error with newest mesa driver Product: Wine-staging Version: 2.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bellamorte42(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- fixme:d3d:wined3d_dxtn_init Wine cannot find the txc_dxtn library, DXTn software support unavailable. Mesa now incorporates the functionality directly, and the standalone library conflicts with the driver. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 6

[Bug 42324] New: Wine selects wrong OpenGL renderer on macOS
by wine-bugs＠winehq.org Jan. 8, 2022

Jan. 8, 2022

https://bugs.winehq.org/show_bug.cgi?id=42324 Bug ID: 42324 Summary: Wine selects wrong OpenGL renderer on macOS Product: Wine Version: 2.0-rc6 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: critical Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: f.platte(a)platte-web.de Created attachment 57072 --> https://bugs.winehq.org/attachment.cgi?id=57072 example images I'm using a 13 inch 2012 MacBook Pro with a Thunderbolt eGPU (GTX 750Ti). Due to macOS limitations the the eGPU can only accelerate the external monitor. (Some application which support selecting a renderer work on the internal display. e.g openglex4 [OpenGL Extensions Viewer]). To my knowledge the macOS applications else always use the renderer driving the screen where they are launched on. However wine does not respect this behaviour. I tried running several windows executables like the benchmark tools Valley and Heaven which keep using the Mac's internal Intel HD4000 graphics although being used on the external screen. I tried several wine engines from the staging, stable and development tree, which all are affected. To check wether it might be an OS related issue I also ran the Mac-native versions of the benchmarks mentioned above which both worked as expected (using the OpenGL renderer driving the monitor they are launched on). This basically breaks games and other GPU heavy windows programs in my case. I do not know whether hackintoshes are affected as well as they basically are the only other macOS machines having integrated and dedicated GPU driving different monitors. The logical solution seems to be to make wine respect the way macOS assigns renderer while an ideal solution would be implementing a way to select a renderer/always default to the dedicated GPU as this would enable accelerating the internal monitor with the external GPU like it's possible with windows. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 19

[Bug 45354] New: BlazBlue Cross Tag Battle crashes before startup ( Unhandled page fault on read access...)
by wine-bugs＠winehq.org Jan. 8, 2022

Jan. 8, 2022

https://bugs.winehq.org/show_bug.cgi?id=45354 Bug ID: 45354 Summary: BlazBlue Cross Tag Battle crashes before startup (Unhandled page fault on read access...) Product: Wine Version: 3.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: mrniex(a)protonmail.com Distribution: --- Created attachment 61650 --> https://bugs.winehq.org/attachment.cgi?id=61650 The whole log of console output and debugger output BlazBlue Cross Tag Battle crashes before even starting on both latest Wine and Wine-staging. Changing platforms (32/64) didn't help. Debug trace attached. Sorry if I misreported anything, I can't make much sense of Wine debugs. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 11

[Bug 44350] New: Wolfenstein The Old Blood used to work before last kernel 's update.
by wine-bugs＠winehq.org Jan. 8, 2022

Jan. 8, 2022

https://bugs.winehq.org/show_bug.cgi?id=44350 Bug ID: 44350 Summary: Wolfenstein The Old Blood used to work before last kernel's update. Product: Wine-staging Version: 2.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: lukasbownik99(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 60237 --> https://bugs.winehq.org/attachment.cgi?id=60237 Full backtrace of a problem. Wolfenstien The Old Blood worked perfectly until I updated kernel to the newest version which contains the patch for Meltdown. My distro: Linux Mint 18.3. GPU Driver: 384 for nVidia GeForce GTX 970. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 3

[Bug 30940] New: Could not start Tween.exe using wine-mono
by wine-bugs＠winehq.org Jan. 8, 2022

Jan. 8, 2022

http://bugs.winehq.org/show_bug.cgi?id=30940 Bug #: 30940 Summary: Could not start Tween.exe using wine-mono Product: Wine Version: 1.5.6 Platform: x86 URL: http://sourceforge.jp/projects/tween OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: felixonmars(a)gmail.com CC: fracting(a)gmail.com Classification: Unclassified 0. Software Download: http://sourceforge.jp/projects/tween/releases/ It's free and open-source. 1. How to reproduce: $ wine Tween.exe 2. Result: Unhandled Exception: System.InvalidOperationException: WinForms_SeeInnerExceptio n ---> System.TypeInitializationException: An exception was thrown by the type i nitializer for Tween.AppendSettingDialog ---> System.OutOfMemoryException: Not e nough memory to complete operation [GDI+ status: OutOfMemory] at System.Drawing.GDIPlus.CheckStatus (Status status) [0x00000] in <filename u nknown>:0 at System.Drawing.Text.InstalledFontCollection..ctor () [0x00000] in <filename unknown>:0 at System.Drawing.FontFamily.get_Families () [0x00000] in <filename unknown>:0 at System.Windows.Forms.FontDialog.PopulateFontList () [0x00000] in <filename unknown>:0 at System.Windows.Forms.FontDialog..ctor () [0x00000] in <filename unknown>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.FontDialog:.ctor () at Tween.AppendSettingDialog.InitializeComponent () [0x00000] in <filename unk nown>:0 at (wrapper remoting-invoke-with-check) Tween.AppendSettingDialog:InitializeCo mponent () at Tween.AppendSettingDialog..ctor () [0x00000] in <filename unknown>:0 at (wrapper remoting-invoke-with-check) Tween.AppendSettingDialog:.ctor () at Tween.AppendSettingDialog..cctor () [0x00000] in <filename unknown>:0 --- End of inner exception stack trace --- at Tween.TweenMain..ctor () [0x00000] in <filename unknown>:0 at (wrapper managed-to-native) System.Reflection.MonoCMethod:InternalInvoke (S ystem.Reflection.MonoCMethod,object,object[],System.Exception&) at System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags invok eAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globa lization.CultureInfo culture) [0x00000] in <filename unknown>:0 --- End of inner exception stack trace --- at Tween.My.MyProject+MyForms.Create__Instance__[TweenMain] (Tween.TweenMain I nstance) [0x00000] in <filename unknown>:0 at Tween.My.MyProject+MyForms.get_TweenMain () [0x00000] in <filename unknown> :0 at Tween.My.MyApplication.OnCreateMainForm () [0x00000] in <filename unknown>: 0 at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun () [0x00000] in <filename unknown>:0 at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run ( System.String[] commandLine) [0x00000] in <filename unknown>:0 at Tween.My.MyApplication.Main (System.String[] Args) [0x00000] in <filename u nknown>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.InvalidOperationException: WinForms_Se eInnerException ---> System.TypeInitializationException: An exception was thrown by the type initializer for Tween.AppendSettingDialog ---> System.OutOfMemoryEx ception: Not enough memory to complete operation [GDI+ status: OutOfMemory] at System.Drawing.GDIPlus.CheckStatus (Status status) [0x00000] in <filename u nknown>:0 at System.Drawing.Text.InstalledFontCollection..ctor () [0x00000] in <filename unknown>:0 at System.Drawing.FontFamily.get_Families () [0x00000] in <filename unknown>:0 at System.Windows.Forms.FontDialog.PopulateFontList () [0x00000] in <filename unknown>:0 at System.Windows.Forms.FontDialog..ctor () [0x00000] in <filename unknown>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.FontDialog:.ctor () at Tween.AppendSettingDialog.InitializeComponent () [0x00000] in <filename unk nown>:0 at (wrapper remoting-invoke-with-check) Tween.AppendSettingDialog:InitializeCo mponent () at Tween.AppendSettingDialog..ctor () [0x00000] in <filename unknown>:0 at (wrapper remoting-invoke-with-check) Tween.AppendSettingDialog:.ctor () at Tween.AppendSettingDialog..cctor () [0x00000] in <filename unknown>:0 --- End of inner exception stack trace --- at Tween.TweenMain..ctor () [0x00000] in <filename unknown>:0 at (wrapper managed-to-native) System.Reflection.MonoCMethod:InternalInvoke (S ystem.Reflection.MonoCMethod,object,object[],System.Exception&) at System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags invok eAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globa lization.CultureInfo culture) [0x00000] in <filename unknown>:0 --- End of inner exception stack trace --- at Tween.My.MyProject+MyForms.Create__Instance__[TweenMain] (Tween.TweenMain I nstance) [0x00000] in <filename unknown>:0 at Tween.My.MyProject+MyForms.get_TweenMain () [0x00000] in <filename unknown> :0 at Tween.My.MyApplication.OnCreateMainForm () [0x00000] in <filename unknown>: 0 at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun () [0x00000] in <filename unknown>:0 at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run ( System.String[] commandLine) [0x00000] in <filename unknown>:0 at Tween.My.MyApplication.Main (System.String[] Args) [0x00000] in <filename u nknown>:0 Unhandled Exception: System.TypeInitializationException: An exception was thrown by the type initializer for Tween.AppendSettingDialog ---> System.OutOfMemoryEx ception: Not enough memory to complete operation [GDI+ status: OutOfMemory] at System.Drawing.GDIPlus.CheckStatus (Status status) [0x00000] in <filename u nknown>:0 at System.Drawing.Text.InstalledFontCollection..ctor () [0x00000] in <filename unknown>:0 at System.Drawing.FontFamily.get_Families () [0x00000] in <filename unknown>:0 at System.Windows.Forms.FontDialog.PopulateFontList () [0x00000] in <filename unknown>:0 at System.Windows.Forms.FontDialog..ctor () [0x00000] in <filename unknown>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.FontDialog:.ctor () at Tween.AppendSettingDialog.InitializeComponent () [0x00000] in <filename unk nown>:0 at (wrapper remoting-invoke-with-check) Tween.AppendSettingDialog:InitializeCo mponent () at Tween.AppendSettingDialog..ctor () [0x00000] in <filename unknown>:0 at (wrapper remoting-invoke-with-check) Tween.AppendSettingDialog:.ctor () at Tween.AppendSettingDialog..cctor () [0x00000] in <filename unknown>:0 --- End of inner exception stack trace --- at Tween.TweenMain..ctor () [0x00000] in <filename unknown>:0 at (wrapper managed-to-native) System.Reflection.MonoCMethod:InternalInvoke (S ystem.Reflection.MonoCMethod,object,object[],System.Exception&) at System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags invok eAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globa lization.CultureInfo culture) [0x00000] in <filename unknown>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.TypeInitializationException: An except ion was thrown by the type initializer for Tween.AppendSettingDialog ---> System .OutOfMemoryException: Not enough memory to complete operation [GDI+ status: Out OfMemory] at System.Drawing.GDIPlus.CheckStatus (Status status) [0x00000] in <filename u nknown>:0 at System.Drawing.Text.InstalledFontCollection..ctor () [0x00000] in <filename unknown>:0 at System.Drawing.FontFamily.get_Families () [0x00000] in <filename unknown>:0 at System.Windows.Forms.FontDialog.PopulateFontList () [0x00000] in <filename unknown>:0 at System.Windows.Forms.FontDialog..ctor () [0x00000] in <filename unknown>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.FontDialog:.ctor () at Tween.AppendSettingDialog.InitializeComponent () [0x00000] in <filename unk nown>:0 at (wrapper remoting-invoke-with-check) Tween.AppendSettingDialog:InitializeCo mponent () at Tween.AppendSettingDialog..ctor () [0x00000] in <filename unknown>:0 at (wrapper remoting-invoke-with-check) Tween.AppendSettingDialog:.ctor () at Tween.AppendSettingDialog..cctor () [0x00000] in <filename unknown>:0 --- End of inner exception stack trace --- at Tween.TweenMain..ctor () [0x00000] in <filename unknown>:0 at (wrapper managed-to-native) System.Reflection.MonoCMethod:InternalInvoke (S ystem.Reflection.MonoCMethod,object,object[],System.Exception&) at System.Reflection.MonoCMethod.Invoke (System.Object obj, BindingFlags invok eAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globa lization.CultureInfo culture) [0x00000] in <filename unknown>:0 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

2 23

[Bug 45496] New: nights of azure 2 game instantly crash after openning.
by wine-bugs＠winehq.org Jan. 8, 2022

Jan. 8, 2022

https://bugs.winehq.org/show_bug.cgi?id=45496 Bug ID: 45496 Summary: nights of azure 2 game instantly crash after openning. Product: Wine-staging Version: 3.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: fefuxewabo(a)sfamo.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 61853 --> https://bugs.winehq.org/attachment.cgi?id=61853 backtrace error.. Only tested with Wine-Staging Game : nights of azure 2 DX11 doesn`t seem to load instantly crash when starting -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 3

[Bug 43561] New: SimCity 4 crashes when clicking and dragging the cursor
by wine-bugs＠winehq.org Jan. 8, 2022

Jan. 8, 2022

https://bugs.winehq.org/show_bug.cgi?id=43561 Bug ID: 43561 Summary: SimCity 4 crashes when clicking and dragging the cursor Product: Wine Version: 2.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexchandel(a)gmail.com Distribution: --- Created attachment 58966 --> https://bugs.winehq.org/attachment.cgi?id=58966 wine-2.14 crash log Running SimCity 4 and clicking and dragging the cursor into the bottom-right of the screen causes wine to immediately terminate. Console output attached. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 4

[Bug 44078] New: Virtua Fighter PC - CD not recognized
by wine-bugs＠winehq.org Jan. 8, 2022

Jan. 8, 2022

https://bugs.winehq.org/show_bug.cgi?id=44078 Bug ID: 44078 Summary: Virtua Fighter PC - CD not recognized Product: Wine Version: 2.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: legluondunet(a)free.fr Distribution: --- Hello, after installed Virtua Fighter PC 1, launch the game, it doesn't recognize the CD and you can not continue. No usefull information in the terminal. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 3

[Bug 39540] New: DirectInput, Xinput, Overall Controller support messed up on OS X
by wine-bugs＠winehq.org Jan. 8, 2022

Jan. 8, 2022

https://bugs.winehq.org/show_bug.cgi?id=39540 Bug ID: 39540 Summary: DirectInput, Xinput, Overall Controller support messed up on OS X Product: Wine Version: 1.7.54 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: adrian.koehres(a)gmx.net I've tried many games now and nothing really works. I tried a PS3 Dualshock Controller and also a Xbox360 controller. If the game doesn't handle controller support by itself then there is no chance to get it to work. Dinput breaks controller input completely in most cases and xinput doesn't do anything at all. I had games where the buttons were recognized, and the axes not. And games where absolutely nothing was recognized. The controllers I testet worked perfectly with native controller supporting games on OS X. As soon as I'm using wine and the game isn't handling the controller by itself, its a pain. For example Volgarr the Viking (I know there is a OS X port) works perfectly when porting the Windows version with wine. The Controller gets detected flawlessly without any problems. There is no need to install dinput/xinput through winetricks as the game is doing that somehow by itself. There is a game called TowerClimb when portet with wine on OS X, only the buttons work. The axes and throttlers absolutely don't work. No matter if I install dinput/xinput through winetricks. I tried mapping the controller myself through regkey values but you need the name of the divice for doing that. So using "WINEDEBUG=+dinput wine game.exe 2>&1 | grep joydev_enum_device" results in "fixme:dinput:IDirectInputDevice2AImpl_EnumEffects (this=0x7043d00,0x26c1a60,0x2702fb8,0x00000000): stub!" Then I tried PrinceOfPersia: Sands Of Time where it was not possible to get any controller working with it's wine port. Installed dinput/xinput. Nothing seems to work though. The Wine Control Panel Gamecontroller utility seems to recognize the controllers though. Also different Windows Gamecontroller utilities seem to recognize the controllers flawlessly when ported with wine. Programs which handle the controller by themselves with their own dinput/xinput.dll's seem to work well. It's getting problematic when you have to use dinput/xinput through winetricks as they don't seem to work. I've tried many different versions on wine. Nothing works. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 5