wine-bugs February 2018

wine-bugs@winehq.org

1 participants
8011 discussions

[Bug 38364] New: AutoPatcher Updater fails due to missing COM interfaces
by wine-bugs＠winehq.org 09 Jan '22

09 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=38364 Bug ID: 38364 Summary: AutoPatcher Updater fails due to missing COM interfaces Product: Wine Version: 1.7.38 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gerbilsoft(a)gerbilsoft.com Distribution: --- Created attachment 51207 --> https://bugs.winehq.org/attachment.cgi?id=51207 Console output for AutoPatcher Attempting to use the AutoPatcher Updater on Wine results in numerous COM errors due to unimplemented interfaces. AutoPatcher is available for download at: http://www.autopatcher.net/forum/ On startup, it shows the following messages: Object doesn't support this action In mdlInitialization.initFolders At Line 108 Object variable or With block variable not set In mdlInitialization.initFolders At Line 108 Object variable or With block variable not set In mdlInitialization.initFolders At Line 108 Console output shows several unsupported COM interfaces: - {7fd52380-4e07-101b-ae2d-08002b2ec713}: IPersistStreamInit - {37d84f60-42cb-11ce-8135-00aa004bb851}: IPersistPropertyBag - {df0b3d60-548f-101b-8e65-08002b2bd119}: ISupportErrorInfo -- 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 9

[Bug 39777] New: cannot run some of Themida & WinLicense protection software
by wine-bugs＠winehq.org 09 Jan '22

09 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=39777 Bug ID: 39777 Summary: cannot run some of Themida & WinLicense protection software Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gamiljydcome(a)gmail.com Distribution: --- Created attachment 53070 --> https://bugs.winehq.org/attachment.cgi?id=53070 Themida & WinLicense protection, can not run Some of Themida & WinLicense protection software cannot be run, wine auto exit. But some of Themida & WinLicense protection software runs fine. -- 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 10

[Bug 44011] New: page fault in schan_QueryContextAttributesW
by wine-bugs＠winehq.org 09 Jan '22

09 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=44011 Bug ID: 44011 Summary: page fault in schan_QueryContextAttributesW Product: Wine Version: 2.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: secur32 Assignee: wine-bugs(a)winehq.org Reporter: development(a)winomega.com Distribution: --- Created attachment 59672 --> https://bugs.winehq.org/attachment.cgi?id=59672 test program Wine gets a page fault in secur32.dll very often (thought not 100% of the time) when running a trivial program using libmariadb.dll (MariaDB Connector/C 3.0.2): a2b008591f3cb238d1e4410c4d1b9f08 libmariadb.dll Note: libmariadb.dll (MariaDB Connector/C 3.0.2) can be downloaded as win32 binary or source from https://downloads.mariadb.org/connector-c/3.0.2/ Test program is attached (test.c). You need to edit and replace the mysql_real_connect call with actual parameters of a MySQL server with SSL enabled, and copy the ca.pem file to current directory (a trivial setup like https://www.digitalocean.com/community/tutorials/how-to-configure-ssl-tls-f… works). I compiled it with mingw32: i686-w64-mingw32-gcc test.c -o test.exe -I./mariadb-connector-c/include libmariadb.dll -- 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 10

[Bug 38123] New: OneNote 2013 crashes on running setup.exe
by wine-bugs＠winehq.org 09 Jan '22

09 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=38123 Bug ID: 38123 Summary: OneNote 2013 crashes on running setup.exe Product: Wine Version: 1.6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: danikvassin(a)gmail.com Distribution: --- Created attachment 50810 --> https://bugs.winehq.org/attachment.cgi?id=50810 One Note Backtrace OneNote 2013 fails to even begin installation of the program -- 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 12

[Bug 30814] New: Age of Empires II scrolling gets stuck after Alt-Tab away and back
by wine-bugs＠winehq.org 09 Jan '22

09 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=30814 Bug #: 30814 Summary: Age of Empires II scrolling gets stuck after Alt-Tab away and back Product: Wine Version: 1.5.5 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: nemesis(a)icequake.net Classification: Unclassified Wine 1.2 did not have this problem but was much slower. Wine 1.5.5 is much faster and just a much better overall experience with this one caveat. If you start a game and immediately alt-tab away and back, nothing is amiss. You can even click on some things onscreen and there is no problem. However, once you have scrolled the screen either by moving the mouse towards the edges, or by using the arrow keys on the keyboard, if you alt-tab away and back, upon returning the screen will immediately begin to scroll in an apparently random direction and cannot be stopped. I did the WINEDEBUG="+cursor,+dinput,+ddraw" winedbg Age2_x1/age2_x1.exe and did not come up with anything obviously wrong while the problem was occurring. A lot of this kind of stuff: trace:ddraw:surface_lock locked surface returning description : trace:ddraw:DDRAW_dump_members - DDSD_CAPS : DDSCAPS_OFFSCREENPLAIN DDSCAPS_VIDEOMEMORY DDSCAPS_LOCALVIDMEM trace:ddraw:DDRAW_dump_members - DDSD_HEIGHT : 768 trace:ddraw:DDRAW_dump_members - DDSD_WIDTH : 1024 trace:ddraw:DDRAW_dump_members - DDSD_PITCH : 1024 trace:ddraw:DDRAW_dump_members - DDSD_PIXELFORMAT : ( DDPF_PALETTEINDEXED8 DDPF_RGB , RGB bits: 8, R 00 G 00 B 00) trace:ddraw:ddraw_surface1_Unlock iface 0xa2f01a8, data 0xbf44020. trace:ddraw:ddraw_surface7_Unlock iface 0xa2f0198, rect (null). trace:cursor:X11DRV_GetCursorPos pointer at (885,649) server pos 885,649 trace:cursor:SetCursor (nil) trace:ddraw:ddraw_surface1_Blt iface 0xa303ef8, dst_rect (0,0)-(24,32), src_surface 0xa2f01a8, src_rect (885,649)-(909,681), flags 0x1000000, fx (nil). trace:ddraw:ddraw_surface7_Blt iface 0xa303ee8, dst_rect (0,0)-(24,32), src_surface 0xa2f0198, src_rect (885,649)-(909,681), flags 0x1000000, fx (nil). trace:ddraw:ddraw_surface1_GetClipper iface 0xa2f01a8, clipper 0x33c81c. trace:ddraw:ddraw_surface7_GetClipper iface 0xa2f0198, clipper 0x33c81c. trace:ddraw:ddraw_surface1_SetColorKey iface 0xa305188, flags 0x8, color_key 0x33c7f8. trace:ddraw:ddraw_surface7_SetColorKey iface 0xa305178, flags 0x8, color_key 0x33c7f8. trace:ddraw:ddraw_surface7_EnumAttachedSurfaces iface 0xa305178, context 0x33c7b8, callback 0x7e72abb0. trace:ddraw:ddraw_surface7_EnumAttachedSurfaces end of enumeration. trace:ddraw:ddraw_surface1_BltFast iface 0xa2f01a8, dst_x 885, dst_y 649, src_surface 0xa305188, src_rect (0,0)-(24,32), flags 0x11. trace:ddraw:ddraw_surface7_BltFast iface 0xa2f0198, dst_x 885, dst_y 649, src_surface 0xa305178, src_rect (0,0)-(24,32), flags 0x11. trace:ddraw:ddraw_surface1_Blt iface 0xa4777f0, dst_rect (0,0)-(1024,768), src_surface 0xa2f01a8, src_rect (0,0)-(1024,768), flags 0x1000000, fx (nil). trace:ddraw:ddraw_surface7_Blt iface 0xa4777e0, dst_rect (0,0)-(1024,768), src_surface 0xa2f0198, src_rect (0,0)-(1024,768), flags 0x1000000, fx (nil). trace:ddraw:ddraw_clipper_GetClipList iface 0x151748, rect (0,0)-(1024,768), clip_list (nil), clip_list_size 0x33c7b8. trace:ddraw:ddraw_clipper_GetClipList iface 0x151748, rect (0,0)-(1024,768), clip_list 0xa52ab90, clip_list_size 0x33c7b8. trace:ddraw:ddraw_palette_SetEntries iface 0x143150, flags 0, start 0, count 256, entries 0x9192a0. trace:cursor:X11DRV_GetCursorPos pointer at (885,649) server pos 885,649 trace:cursor:X11DRV_GetCursorPos pointer at (885,649) server pos 885,649 trace:cursor:X11DRV_GetCursorPos pointer at (885,649) server pos 885,649 trace:cursor:X11DRV_GetCursorPos pointer at (885,649) server pos 885,649 trace:cursor:X11DRV_GetCursorPos pointer at (885,649) server pos 885,649 trace:cursor:X11DRV_GetCursorPos pointer at (885,649) server pos 885,649 Let me know what I can do to help debug. -- 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 77

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

09 Jan '22

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 09 Jan '22

09 Jan '22

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 09 Jan '22

09 Jan '22

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 44350] New: Wolfenstein The Old Blood used to work before last kernel 's update.
by wine-bugs＠winehq.org 09 Jan '22

09 Jan '22

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 09 Jan '22

09 Jan '22

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 43561] New: SimCity 4 crashes when clicking and dragging the cursor
by wine-bugs＠winehq.org 09 Jan '22

09 Jan '22

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 09 Jan '22

09 Jan '22

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 09 Jan '22

09 Jan '22

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

[Bug 44228] New: prince of persia 3D crashes at play (installes ok)
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=44228 Bug ID: 44228 Summary: prince of persia 3D crashes at play (installes ok) Product: Wine Version: 3.0-rc3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cedric.dewijs(a)telfort.nl Distribution: --- Created attachment 60024 --> https://bugs.winehq.org/attachment.cgi?id=60024 backtrace created by wine itself After installing, Prince of persia 3D crashes with an unhandled exception uname -a Linux archlinux 4.14.8-1-ARCH #1 SMP PREEMPT Wed Dec 20 21:27:44 UTC 2017 x86_64 GNU/Linux -- 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 13

[Bug 44249] New: Can't play Diablo 2 (Battle.net) when Virtualization in BIOS is disabled.
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=44249 Bug ID: 44249 Summary: Can't play Diablo 2 (Battle.net) when Virtualization in BIOS is disabled. Product: Wine Version: 2.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: asriroc(a)gmail.com Distribution: --- 1. I have "Virtualization" as "Enable" in my BIOS (Compaq Presario F763NR Notebook with the most recent BIOS version). 2. I installed a fresh Fedora 27 Cinnamon Spin with Linux 4.14.8-300.fc27.x86_64 kernel. 3. I installed NVIDIA 304.137 4. I installed Diablo 2 using WINE 2.22 At this point, I would be able to play Diablo 2 using Battle.net 5. I rebooted the notebook, and set "Disable" on the "Virtualization" in my BIOS. 6. I tried to play Diablo 2, using WINE 2.22, but I won't be able to use Battle.net Now, if I rebooted and enabled my virtualization in my BIOS, Diablo 2 would work again. Thank you so much. -- 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 9

[Bug 42223] New: I cant install AB Bulkmailer .. Please HELP me ...
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=42223 Bug ID: 42223 Summary: I cant install AB Bulkmailer .. Please HELP me ... Product: Wine Version: 2.0-rc4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bluebird456(a)vfemail.net Distribution: --- Created attachment 56863 --> https://bugs.winehq.org/attachment.cgi?id=56863 AB BulkMailer install BUG I want to install AB BulkMailer . Which is a Windows app . I tried to install the app , But error appears ... I attached the detail in attached TEXT FILE ... Please CHECK and PLEASE HELP ME .. Please Fix the error BUG as soon as possible ... I JUST want to use the app ... -- 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 63

[Bug 39787] New: Lilos Lesewelt 2 crashes
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=39787 Bug ID: 39787 Summary: Lilos Lesewelt 2 crashes Product: Wine Version: 1.8-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alois.schloegl(a)gmail.com Distribution: --- Created attachment 53081 --> https://bugs.winehq.org/attachment.cgi?id=53081 backtrack file, run with WINEDEBUG=+all "Lilos Lesewelt 2" can be installed, but when trying to start it, it crashes. The full debug log with WINEDEBUG=+all is available from (11MB !) http://pub.ist.ac.at/~schloegl/wine-reports/lilo2.debug.all.log.gz A short version for WINEDEBUG=+cdrom in http://pub.ist.ac.at/~schloegl/wine-reports/lilo2.debug.cdrom.log -- 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 15

[Bug 35883] New: Horizon crashes with page fault
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=35883 Bug ID: 35883 Summary: Horizon crashes with page fault Product: Wine Version: 1.7.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jmelton116(a)gmail.com Created attachment 47912 --> http://bugs.winehq.org/attachment.cgi?id=47912 Backtrace generated by crash Horizon seems to crash at random times with a page fault. There seems to be no sort of consistency between what is occuring in game and when these occur, but I could be wrong. These were encountered on the latest git version. Page fault's backtrace is 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 7

[Bug 44146] New: Crysis 2: DX11 is a slideshow
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=44146 Bug ID: 44146 Summary: Crysis 2: DX11 is a slideshow Product: Wine Version: 3.0-rc1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: christian.frank(a)gmx.de Distribution: --- Hi, trying to play Crysis 2 with DX11 is actually impossible, it is a complete slideshow. Switching from DX9 to DX11 the FPS drop from ~ 40 to ~ 8 fps. Tons of fixmes are spit out: 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[31]" might be used before being initialized 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 4. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 5. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 6. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 7. 0048:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #24: 0048:fixme:d3d_shader:print_glsl_info_log Vertex info 0048:fixme:d3d_shader:print_glsl_info_log ----------- 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[1]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[2]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[3]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[4]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[5]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[6]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[7]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[8]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[9]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[10]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[11]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[12]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[13]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[14]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[15]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[16]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[17]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[18]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[19]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[20]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[21]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[22]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[23]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[24]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[25]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[26]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[27]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[28]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[29]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[30]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[31]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0048:fixme:d3d_shader:print_glsl_info_log Fragment info 0048:fixme:d3d_shader:print_glsl_info_log ------------- 0048:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050: "R0.yzw" might be used before being initialized 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 4. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 5. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 6. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 7. 0048:fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x800000c2. 0048:fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x00155543. 0048:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #27: 0048:fixme:d3d_shader:print_glsl_info_log Vertex info 0048:fixme:d3d_shader:print_glsl_info_log ----------- 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[1].zw" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[2]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[3]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[4]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[5]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[6]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[7]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[8]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[9]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[10]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[11]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[12]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[13]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[14]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[15]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[16]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[17]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[18]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[19]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[20]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[21]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[22]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[23]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[24]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[25]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[26]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[27]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[28]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[29]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[30]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[31]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0048:fixme:d3d_shader:print_glsl_info_log Fragment info 0048:fixme:d3d_shader:print_glsl_info_log ------------- 0048:fixme:d3d_shader:print_glsl_info_log 0(26) : warning C7050: "R0.yzw" might be used before being initialized 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 4. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 5. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 6. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 7. My GPU: Nvidia GTX 970 (384.98) Memory: 16GB CPU: Core i5 3570k Opensuse Tumbleweed, latest Snapshot Many thanks ! Christian -- 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 13

[Bug 22755] New: Regression : win16 installer program of "de rouck" freeze
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=22755 Summary: Regression : win16 installer program of "de rouck" freeze Product: Wine Version: 0.9.31. Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: vincent.hardy.be(a)gmail.com Created an attachment (id=28058) --> (http://bugs.winehq.org/attachment.cgi?id=28058) wine-1.1.31 screenshot It works with wine-1.1.30. With wine-1.1.31, see screenshot Regression test says : 3b1186de5aeabd261e70dab8b78a730030075ca1 is the first bad commit commit 3b1186de5aeabd261e70dab8b78a730030075ca1 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Wed Oct 7 17:14:10 2009 +0200 kernel32: Move the 16-bit string functions to kernel16.c. :040000 040000 3412021b8c21c250ee3ccc60ce31c3f3f9365c50 3c5be0f4e2330e28e86e4b839447d40d88bf42f3 M dlls -- 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 11

[Bug 33131] New: taskkill doesn't support /fi (filtering) option
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=33131 Bug #: 33131 Summary: taskkill doesn't support /fi (filtering) option Product: Wine Version: 1.5.25 Platform: x86-64 OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Blocks: 33130 Classification: Unclassified Noticed while looking at bug 33130 0067:Call KERNEL32.CreateProcessW(00000000,008fcb00 L"C:\\windows\\system32\\taskkill.exe /F /Fi \"MODULES eq AutoupdatePlugin.cpl\" /T",00000000,00000000,00000000,00000400,00000000,00000000,008fb1fc,008fb240) ret=7e4d517f -- 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 3

[Bug 24169] New: QuarkXPress version 8.x hangs on start (missing double quoting of browser path in HKCR\htmlfile\shell\open\command)
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=24169 Summary: QuarkXPress version 8.x hangs on start (missing double quoting of browser path in HKCR\htmlfile\shell\open\command) Product: Wine Version: 1.3.1 Platform: x86 URL: http://downloads.quark.com/Details.aspx?fid=163&&mid=2 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, someone in appdb reported QuarkXPress version 8.x (2010 version) hangs on start. Downloaded a 60-day trial ... it does indeed - due to a Wine shortcoming and an application bug. ;-) Basically the app retrieves default browser setting from registry and does some parsing to extract browser (unquoting and splitting '\' '/' path delimiter). Their parsing is broken in a way that it can't cope with missing double quotes around browser path leading to endless looping. HKEY_CLASSES_ROOT\htmlfile\shell\open\command -> C:\windows\system32\winebrowser.exe -nohome With the browser path in double quotes, QuarkXPress 8 starts fine. "C:\windows\system32\winebrowser.exe" -nohome The quoting is most likely present in Windows as the app would loop there too without. Regards -- 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 4

[Bug 31033] New: Multiple apps need IWbemServices::GetObject to retrieve WMI class instances
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=31033 Bug #: 31033 Summary: Multiple apps need IWbemServices::GetObject to retrieve WMI class instances Product: Wine Version: 1.5.7 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: wmi&wbemprox AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Classification: Unclassified Hello, continuation of bug 20651 Multiple apps still fail to query for WMI classes/properties because IWbemServices::GetObject method is not implemented (they use a different method). One app is bug 28682 (Ragnarok downloader) Example .NET code: --- snip --- ManagementClass class2 = new ManagementClass("Win32_Processor"); foreach (ManagementObject obj2 in class2.GetInstances()) { if (str == string.Empty) { str = obj2.Properties["ProcessorId"].Value.ToString(); } } --- snip --- MSDN: http://msdn.microsoft.com/en-us/library/windows/desktop/aa392109%28v=vs.85%… Regards -- 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 8

[Bug 24225] New: provide "taskkill" command line tool to aid installers (Impulse installer and more)
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=24225 Summary: provide "taskkill" command line tool to aid installers (Impulse installer and more) Product: Wine Version: 1.3.1 Platform: x86 OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, various installers use "taskkill" command line tool to terminate running processes, preventing possible sharing/update problems with components to be installed. --- snip --- wine: cannot find L"C:\\windows\\system32\\TASKKILL.exe" --- snip --- Trace logs for "Impulse" installer as example: --- snip --- 0034:Call KERNEL32.CreateProcessA(00000000,0092fab0 "\"C:\\windows\\system32\\TASKKILL.exe\" /f /im impulse.exe",00000000,00000000,00000000,00000010,00000000,00000000,0108e980,0108e970) ret=004e5657 ... wine: cannot find L"C:\\windows\\system32\\TASKKILL.exe" 0034:Ret KERNEL32.CreateProcessA() retval=00000000 ret=004e5657 ... 0037:Call KERNEL32.CreateProcessA(00000000,0092fab0 "\"C:\\windows\\system32\\TASKKILL.exe\" /f /im impulsedock.exe",00000000,00000000,00000000,00000010,00000000,00000000,0118e980,0118e970) ret=004e5657 ... wine: cannot find L"C:\\windows\\system32\\TASKKILL.exe" 0037:Ret KERNEL32.CreateProcessA() retval=00000000 ret=004e5657 ... 003a:Call KERNEL32.CreateProcessA(00000000,0092fab0 "\"C:\\windows\\system32\\TASKKILL.exe\" /f /im impulsemini.exe",00000000,00000000,00000000,00000010,00000000,00000000,00e5e980,00e5e970) ret=004e5657 ... wine: cannot find L"C:\\windows\\system32\\TASKKILL.exe" 003a:Ret KERNEL32.CreateProcessA() retval=00000000 ret=004e5657 ... 003d:Call KERNEL32.CreateProcessA(00000000,0092fab0 "\"C:\\windows\\system32\\TASKKILL.exe\" /f /im impulsenow.exe",00000000,00000000,00000000,00000010,00000000,00000000,0108e980,0108e970) ret=004e5657 ... wine: cannot find L"C:\\windows\\system32\\TASKKILL.exe" 003d:Ret KERNEL32.CreateProcessA() retval=00000000 ret=004e5657 ... --- snip --- Wine should provide such a tool to aid installers. Reference: http://technet.microsoft.com/en-us/library/bb491009.aspx Regards -- 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 5

[Bug 32758] New: TurboTax 2012 fails to run update service
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=32758 Bug #: 32758 Summary: TurboTax 2012 fails to run update service Product: Wine Version: 1.5.22 Platform: x86 OS/Version: Linux Status: NEW Keywords: dotnet, download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com CC: focht(a)gmx.net Depends on: 27991 Classification: Unclassified Using wine-1.5.22, you'll need to workaround bug 27991, and install dotnet40 with winetricks. The installer will then work fine. Try to start it, and you'll get 3 errors on start about the update service not working. The relevant turbotax help links: http://turbotax.intuit.com/support/iq/Update-Product/Error-5639--Can-t-Conf… http://turbotax.intuit.com/support/iq/Connectivity-Errors/Error-5640--Can-t… stdout shows: Operation is not supported on this platform. 3 times, which is probably related. -- 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 35

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs February 2018