wine-bugs August 2017

wine-bugs@winehq.org

1 participants
7781 discussions

[Bug 38066] New: Memento Mori (Numen: Contest of Heroes): mouse buttons don't work (needs native dinput8)
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=38066 Bug ID: 38066 Summary: Memento Mori (Numen: Contest of Heroes): mouse buttons don't work (needs native dinput8) Product: Wine Version: 1.7.36 Hardware: x86 URL: http://www.4players.de/4players.php/download_info/Down loads/Download/50673/Memento_Mori/Deutsche_Demo.html OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com Distribution: --- Created attachment 50710 --> https://bugs.winehq.org/attachment.cgi?id=50710 terminal output Keyboard is working in the game because I can skip the intro videos by pressing <Esc> and I can move the mouse pointer when the menu appears. Mouse buttons however are not registered thus I can't select a menu option. 'winetricks dinput8' is a workaround. I know of another game from the same publisher that also needs native dinput8 otherwise mouse buttons don't work: Numen: Contest of Heroes. To test the demo you need to install native d3dx9_36 and Windows Media Player 9 or 10. wine-1.7.36-28-ga679cae Fedora 21 XOrg 1.16.3 XFCE 4.10 Memento_Mori_DEMO_setup_GERMAN.exe md5sum: 8eda283807d43ad2a058c397efde7725 -- 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.

1 7

[Bug 35320] New: wine crash in MSVCRT__mbstowcs_l regarding locale, & other minor locale related problems
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=35320 Bug ID: 35320 Summary: wine crash in MSVCRT__mbstowcs_l regarding locale, & other minor locale related problems Product: Wine Version: 1.7.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcrt Assignee: wine-bugs(a)winehq.org Reporter: htl10(a)users.sourceforge.net Classification: Unclassified Created attachment 47106 --> http://bugs.winehq.org/attachment.cgi?id=47106 The file needed to cause the crash. from r project (http://www.r-project.org/) http://cran.ma.imperial.ac.uk/bin/windows/base/R-2.15.3-win.exe After installing, running: ./wine ~/.wine/drive_c/Program\ Files/R/R-2.15.3/bin/R.exe Then, at the R console prompt, type (having put the attached file at /tmp/1.R): Sys.setlocale("LC_CTYPE", "Chinese") source('z:/tmp/1.R', encoding='UTF8') wine immediately crashes with: -------------------------------------- wine: Unhandled page fault on read access to 0x00000000 at address 0x7eda29af (thread 0030), starting debugger... ... Backtrace: =>0 0x7eda29af MSVCRT__mbstowcs_l+0x5f(wcstr=<couldn't compute location>, mbstr=<couldn't compute location>, count=<couldn't compute location>, locale=<couldn't compute location>) [/home/Nobak-Hin-Tak/tmp-git/wine/dlls/msvcrt/mbcs.c:2140] in msvcrt (0x0440a168) 1 0x7eda2b06 MSVCRT_mbstowcs+0x35(wcstr="as a &Metafile CTRL+W", mbstr=0x0(nil), count=0x64) [/home/Nobak-Hin-Tak/tmp-git/wine/dlls/msvcrt/mbcs.c:2161] in msvcrt (0x0440a198) 2 0x6355b525 in rgraphapp (+0x1b524) (0x00030046) 0x7eda29af MSVCRT__mbstowcs_l+0x5f [/home/Nobak-Hin-Tak/tmp-git/wine/dlls/msvcrt/mbcs.c:2140] in msvcrt: movzbl 0x0(%eax),%eax 2140 if(mbstr[size] == '\0') ... ---------------------------------------- I assume this info in the backtrace should be enough to address the crash. FYI, the slightly unusual procedure is because under R under Vista in an English locale doesn't like to plot graphs with non-latin annotations/texts. The above procedure when used under Vista on British English windows would result in R displaying an almost empty plot with a chinese title. Native R on linux does not need the setlocale part to plot utf8-based texts. Also R on Vista accepts 'Sys.setlocale("LC_CTYPE", "Chinese_China.950")'. I only realized that trying to set traditional chinese [950] in a simplified chinese region [china] is wrong when it is rejected on linux; but R on Vista accepts this. ------------ Warning message: In Sys.setlocale("LC_CTYPE", "Chinese_China.950") : OS reports request to set locale to "Chinese_China.950" cannot be honored ------------ When R is running on Vista, it reports the locale as "English_United Kingdom.1252". But under Linux (in en_GB.utf8 locale), R warns of ----------- During startup - Warning messages: 1: Setting LC_TIME=en_GB.utf8 failed 2: Setting LC_MONETARY=en_GB.utf8 failed ----------- So three locale related issue: - a crash in msvcrt - R under Vista accepts "Chinese_China.950" but R under wine does not. - there are locale-related warning messages from R on start up when running under wine. -- 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.

1 13

[Bug 43187] New: OriginWebHelperService.exe crashes
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=43187 Bug ID: 43187 Summary: OriginWebHelperService.exe crashes Product: Wine Version: 2.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: plata(a)mailbox.org Distribution: --- Created attachment 58460 --> https://bugs.winehq.org/attachment.cgi?id=58460 backtrace EA Origin installs with Wine 2.10 staging but then crashes in the update or login window (OriginWebHelperService.exe). As a result, the Origin window shows an infinite loading screen. As far as I can see, this seems to be caused by qt5gui (QScreen::handle). -- 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.

1 18

[Bug 40160] New: cant install mobogenie
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=40160 Bug ID: 40160 Summary: cant install mobogenie Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: madscientistkustomz(a)gmx.com Distribution: --- Created attachment 53662 --> https://bugs.winehq.org/attachment.cgi?id=53662 trace log problem installing MOBOGENIE for ubuntu -- 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.

1 9

[Bug 40208] New: Steup installation of CEGID BUISINESS LINE failed.
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=40208 Bug ID: 40208 Summary: Steup installation of CEGID BUISINESS LINE failed. Product: Wine Version: 1.9.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: christian.briard(a)gmx.com Distribution: --- Created attachment 53723 --> https://bugs.winehq.org/attachment.cgi?id=53723 MSI log Executing an installation of CEGID BUISINESS LINE failed with a log text (see attached files). "Install: C:\windows\System32\msiexec.exe /q /i "Z:\home\cbriard\CBL\PRODUCTS\AIDEBL.MSI" INSTALLDIR="C:\Program Files\Cegid\Cegid Business Line\" /norestart Install : 1603 - C:\windows\System32\msiexec.exe - Erreur en exécution du programme" Here enclosed a trace file to. Any idea of what is going wrong ? 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.

1 15

[Bug 38402] New: glDebugMessageCallback is broken
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=38402 Bug ID: 38402 Summary: glDebugMessageCallback is broken Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: opengl Assignee: wine-bugs(a)winehq.org Reporter: chris.kcat(a)gmail.com Distribution: --- According to the KHR_debug extension spec, the function glDebugMessageCallback takes a function pointer callback with the type: typedef void (APIENTRY *GLDEBUGPROC)(GLenum source, GLenum type, GLuint id, GLenum severity, GLsizei length, const GLchar* message, const void* userParam); https://www.opengl.org/registry/specs/KHR/debug.txt In particular, it notes that the function callback uses the same calling convention as the other GL functions. The problem is that on Windows, GL uses the stdcall calling convention, while on Linux it uses cdecl. Wine's glDebugMessageCallback thunk passes the callback through as-is, so the system's libGL tries to call an stdcall function as though it was cdecl, causing it to crash upon returning. Another problem is that the spec says: "When DEBUG_OUTPUT_SYNCHRONOUS is disabled, the driver is optionally allowed to concurrently call the debug callback routine from potentially multiple threads, including threads that the context that generated the message is not currently bound to." meaning the callback can be called on threads other than the one OpenGL is being used on. This is a problem because it may be called on one or more internal driver threads that were not created using the Windows API, and if the callback function tries to do anything that relies on Windows-related thread information, it won't be there. -- 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.

1 20

[Bug 41419] New: Visio 2013 crashes with unimplemented function msvcp100.dll.? _GetCombinableSize@details@Concurrency@@YAIXZ
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=41419 Bug ID: 41419 Summary: Visio 2013 crashes with unimplemented function msvcp100.dll.?_GetCombinableSize@details@Concurrency@@ YAIXZ Product: Wine Version: 1.9.20 Hardware: x86-64 OS: Linux Status: NEW Severity: minor Priority: P2 Component: msvcp Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- wine: Call from 0x7b43b53c to unimplemented function msvcp100.dll.?_GetCombinableSize@details@Concurrency@@YAIXZ, aborting -- 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.

1 9

[Bug 39051] New: TabbedTextOut() incorrect output on tab character
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=39051 Bug ID: 39051 Summary: TabbedTextOut() incorrect output on tab character Product: Wine Version: 1.7.29 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: wine(a)goabq.org Distribution: --- Created attachment 52021 --> https://bugs.winehq.org/attachment.cgi?id=52021 testcase (tto.exe) and files to build it Tab characters do not output correctly when they are output one at a time. This is much worse using a memory device context than a screen device context. Attached is a testcase. It outputs text to a window using 2 different methods. Clicking in the client area toggles the method. When iterating over each character, TabbedTextOut() produces apparently garbage from the previous line instead of filling the rectangle appropriately as windows does. When drawing the line in a single call, the behavior is as expected. Spaces do not suffer from this problem (illustrated also by the testcase). -- 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.

1 19

[Bug 35504] New: LibreOffice installation creates two wrong files
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=35504 Bug ID: 35504 Summary: LibreOffice installation creates two wrong files Product: Wine Version: 1.7.10 Hardware: x86 URL: http://sourceforge.net/projects/libreoffice.mirror/fil es/LibreOffice%204.2.0/LibreOffice_4.2.0_Win_x86.msi/d ownload OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: t.artem(a)mailcity.com Classification: Unclassified After installing LibreOffice_4.2.0_Win_x86.msi in Wine two illicit files can be found: C:\Win\System\msvcp100.dll C:\Win\System\msvcr100.dll $ sha1sum LibreOffice_4.2.0_Win_x86.msi 0c306a717aff4499b0abe2d2e3caaa63c62dfa0a LibreOffice_4.2.0_Win_x86.msi -- 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.

1 15

[Bug 40303] New: Control Data passed in DIALOGEX Resource passes pointer with offset sizeof(WORD)
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=40303 Bug ID: 40303 Summary: Control Data passed in DIALOGEX Resource passes pointer with offset sizeof(WORD) Product: Wine Version: 1.9.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: vendor2013(a)herdsoft.com Distribution: --- Created attachment 53942 --> https://bugs.winehq.org/attachment.cgi?id=53942 Sourcecode for a test program When DIALOGEX Resources contain Custom data like in: DEFPUSHBUTTON "OK", IDOK, 148, 6, 50, 14 { 1, 2, 3, 4, 5 } The pointer passed in WM_CREATE is two bytes higher than in windows. In Windows (Tested with Vista an Windows 7 64-Bit) it Points to the Number of Words, in Wine it points to the first data byte. Microsoft Specs for this stuff are here: https://msdn.microsoft.com/de-de/library/windows/desktop/ms645389%28v=vs.85… Attached file dialogtest.zip is sourcecode for a test program with a simple custom control that displays the passed control data. Bug is in Version 1.6.2 (Debian Jessie) and 1.9.5 (Last Download). My suggestion for a patch: --- wine-1.6.2.orig/dlls/user32/dialog.c +++ wine-1.6.2/dlls/user32/dialog.c @@ -234,7 +234,8 @@ static const WORD *DIALOG_GetControl32( TRACE("\n"); TRACE(" END\n" ); } - info->data = p + 1; + info->data = p; p += GET_WORD(p) / sizeof(WORD); } else info->data = NULL; -- 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.

1 7

[Bug 41356] New: The Crew(Uplay) won't launch[STAGING]
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=41356 Bug ID: 41356 Summary: The Crew(Uplay) won't launch[STAGING] Product: Wine Version: 1.9.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: spleefer90(a)gmail.com Distribution: --- Created attachment 55708 --> https://bugs.winehq.org/attachment.cgi?id=55708 launching the game Using wine STAGING Absolutely no idea what's the problem. Running the game just stays at the uplay game loading screen 64 bit prefix -- 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.

1 36

[Bug 40264] New: Iris Online cannot connect to login server
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=40264 Bug ID: 40264 Summary: Iris Online cannot connect to login server Product: Wine Version: 1.9.4 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: noscrubs.net(a)gmail.com Created attachment 53881 --> https://bugs.winehq.org/attachment.cgi?id=53881 Winsock trace from Linux and Mac OS X versions of wine. The game client cannot connect to the login server to authenticate the account. This works perfectly when running under the same version of Wine under Linux, and of course Windows. I have attached a short winsock trace that shows the differences when running under Linux and Mac OS X versions of Wine. I am also including a snippet of the client source relating to this log. The game client can be downloaded from http://noscrubs.net/downloads/NoScrubs_Iris_Online_Nov_2015.zip The launcher/patcher works fine apart from some HTML display issues. AppDB page: https://appdb.winehq.org/objectManager.php?sClass=version&iId=33421&iTestin… -- 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.

1 17

[Bug 20104] New: Fujiprint/Fotokasten albums cannot be created due to missing richtext query interface
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=20104 Summary: Fujiprint/Fotokasten albums cannot be created due to missing richtext query interface Product: Wine Version: 1.1.29 Platform: PC URL: http://www.fotokasten.de/index.php?ftkPage=static&ftkV iew=ftksoftware OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: richedit AssignedTo: wine-bugs(a)winehq.org ReportedBy: cweiske(a)cweiske.de Running the "fotokasten" photo album creation software fails to create certain photo books with the following error: > fixme:richedit:fnTextSrv_QueryInterface Unknown interface: > {01c25500-4268-11d1-883a-3c8b00c10000} > fixme:richedit:fnTextSrv_OnTxInplaceDeactivate 0x3a1e8e0: STUB How to reproduce: 1. Run software 2. Click on tab "Fotobücher" 3. Click on "Fotobücher" icon 4. Click on "Fun" 5. Click on "Fun A4" 6. A loading window appears but is hidden soon after. When using Fotobücher->Fotobücher->Soft->A4, the richtext window has not to be shown, and I get to the next window (meaning it works without richtext). -- 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.

1 9

[Bug 10913] New: start.exe doesn't support optional process title argument
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=10913 Summary: start.exe doesn't support optional process title argument Product: Wine Version: CVS/GIT Platform: Other URL: http://jedit.org OS/Version: other Status: NEW Keywords: download Severity: normal Priority: P2 Component: wine-programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com Running real Java apps under the latest Sun win32 JRE on Wine seems like a fine stress test, even though in many cases users should run with the Linux JRE instead. The Sun JRE and jEdit install ok, but jedit has many startup problems. Here's the first one. Invoking it with the batch file provided by jEdit fails. Here's what's in the batch file: start "jEdit startup" "c:\windows\system32\javaw.exe" -Xms64M -Xmx192M -jar "C:\Program Files\jEdit\jedit.jar" -reuseview %* And here's what happens when you run it: $ cd ~/.wine/drive_c/Program Files/jEdit $ ~/wine-git/wine cmd /c jedit.bat fixme:exec:SHELL_execute flags ignored: 0x00000500 trace:process:CreateProcessW app (null) cmdline L"jEdit startup c:\\windows\\system32\\javaw.exe -Xms64M -Xmx192M -jar \"C:\\Program Files\\jEdit\\jedit.jar\" -reuseview" trace:process:find_exe_file looking for L"jEdit" trace:process:find_exe_file Trying native exe L"c:\\windows\\system32\\jEdit.exe" ... trace:process:find_exe_file Trying built-in exe L"c:\\windows\\system32\\jEdit startup.exe" ... trace:process:find_exe_file looking for L"jEdit startup c:\\windows\\system32\\javaw.exe -Xms64M -Xmx192M -jar \"C:\\Program Files\\jEdit\\jedit.jar\" -reuseview" Application could not be started, or no application associated with the specified file. ShellExecuteEx failed: File not found So it seems that start takes an optional process title argument. Sure enough, http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en… documents it. Who knew? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 20

[Bug 42508] New: start.exe does not detect its title argument when it should ( breaking .e.g URL opening in League of Legends)
by wine-bugs＠winehq.org 03 Mar '19

03 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=42508 Bug ID: 42508 Summary: start.exe does not detect its title argument when it should (breaking .e.g URL opening in League of Legends) Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: hydratech(a)gmail.com Distribution: --- Created attachment 57397 --> https://bugs.winehq.org/attachment.cgi?id=57397 Trace showing League of Legends Client attempting to open a URL. When start.exe is invoked, its first argument in quotes that is not an argument of the application to be executed should be interpreted as the console title. Wine's start.exe fails to do so. -- How to reproduce -- Running the following line in Wine's cmd should open a URL in your browser: Z:\>start "" https://winehq.org/ the actual result is an application not found error. On Windows the same line opens the website as expected. -- Why this is a bug -- I know this was marked as fixed in bug 10913 but the reasoning was incorrect. The argument for stating the bug was fixed was, that when \"escaping your quotes\" in cmd to the title was parsed. This is however not consistent with with Windows behaviour. As explained at the end of that bug report, if you escape your quotes in Wine's cmd start.exe parses the argument as the console title, i.e.: Z:\>start \"hello\" cmd I will now clarify why this is incorrect by showing Windows' behaviour. The following command lines are not equivalent on Windows: C:\>start hello.exe vs. C:\>start "hello.exe" The latter will open a new cmd window titled hello.exe whereas the former attempts to execute an application named hello.exe. In other words cmd's start built-in parses its own command-line checking wether quotes where used. In fact escaping the quotes using back-slashes is invalid as it tries start a process named \hello.exe\. I have tested this on both Windows 7 and Windows XP. In other words, this is invalid: C:>start \"hello.exe\" To illustrate how unintuitive this Windows behaviour is: C:>start "C:\Program Files\Application\hello.exe" Few would guess this actually opens a console titled as such, instead of running an application. That's why I can understand the maintainers would think the bug was fixed. Wine will however correctly emulate unescaped quote-senstive behaviour with the echo built-in: Z:\>echo hoi hoi Z:\>echo "hoi" "hoi" We can see echo being "aware" of the quotes and correctly displaying them; behaviour identical to Windows' echo built-in. Looking at the wine source, start.exe relies on its "argv" parameter instead of using GetCommandLine() and thereby accessing the unmodified command-line. As a consequence the difference between a quoted argument and a non-quoted argument is lost as CreateProcess strips the quotes off the parameters when passing them to execve(). To quote the source of Wine's cmd.exe (wcmdmain.c): /* Can't use argc/argv as it will have stripped quotes from parameters * meaning cmd.exe /C echo "quoted string" is impossible */ It should now be evident that start.exe should either become a wrapper around cmd.exe's built-in start function, invoking cmd and let cmd itself implement start.exe's actual behaviour, or implement GetCommandLine() based argument parsing similar to cmd.exe's within start.exe, leading to duplicated command-line parsing code. Both are not ideal solutions. -- Why does this bug matter? -- There are actually Windows applications relying on this behaviour to open URLs in the user's browser. As an example, League of Legends executes the following shell command to open a URL: cmd.exe /c start "" "<url here>" In other words, League instructs start to launch an untitled shell window with a URL as application, effectively causing the shell to pass it to the browser. However, wine's start.exe interprets this as League trying to execute an empty string as executable name, with a URL as argument. I have attached the relevant output running League with WINEDEBUG=cmd,start,process,exec set. I will speculate that more applications will run into this exact same issue. League's client is based on CEF and it might very well be CEF which implements this style of external URL opening, furthermore there is documentation recommending the use of empty quotes as console title argument when invoking start to prevent it from accidentally parsing follow up arguments in quotes as the console title, think "C:\Program Files\etc...", establishing this as a pattern that might well have been adopted by other applications. See: https://ss64.com/nt/start.html I will also say that, given some instruction, I will be glad to help fixing this bug and write any necessary code. There is actually another issue with current start.exe's console title parsing which I will submit as a separate issue. That issue is however, significantly easier to fix. Finally this also means wine's current handling of command-line arguments might need fixing as: $ wine start '""' "http://winehq.og" will break in a fixed version of 'start.exe', while it should work. For this I will file yet another issue, although the necessity of this fix is debatable. -- 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.

1 13

[Bug 31644] New: glMapBufferRange is extremely slow while playing Resident Evil 5 ( happens only on nvidia binary driver )
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=31644 Bug #: 31644 Summary: glMapBufferRange is extremely slow while playing Resident Evil 5 ( happens only on nvidia binary driver ) Product: Wine Version: 1.5.12 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: tizbac2(a)gmail.com Classification: Unclassified Calls to glMapBufferRange are extremely slow on nvidia drivers with resident evil 5, if this should be reported to nvidia instead just close it over 90% of frame time is taken by glMapBufferRange -- 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.

1 20

[Bug 38488] New: Wrong taces in functions *_invalidate_location
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=38488 Bug ID: 38488 Summary: Wrong taces in functions *_invalidate_location Product: Wine Version: 1.7.41 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: isakov-sl(a)bk.ru Distribution: --- I got a plenty of messages like fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00. It rises because the function wined3d_volume_invalidate_location() is used with reversed parameter For example dlls/wined3d/device.c: wined3d_volume_invalidate_location(dst_volume, ~WINED3D_LOCATION_TEXTURE_RGB); The function assumed location and not ~location. ----- void wined3d_volume_invalidate_location(struct wined3d_volume *volume, DWORD location) { TRACE("Volume %p, clearing %s.\n", volume, wined3d_debug_location(location)); volume->locations &= ~location; TRACE("new location flags are %s.\n", wined3d_debug_location(volume->locations)); } ----- Here wined3d_debug_location() will message like above. Same about wined3d_resource_invalidate_location(struct wined3d_resource *resource, DWORD location) -- 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.

1 6

[Bug 18496] New: BREW simulator always shows a black display
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=18496 Summary: BREW simulator always shows a black display Product: Wine Version: 1.1.21 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: jon.dufresne(a)gmail.com Tested with wine-1.1.21 I am attempting to use the Qualcomm BREW simulator under wine. After installing, I attempted to run the example applets. The application launches and I am able to select an applet directory, but the simulated device's screen always shows black and not the usual list of icons that represent available applets. The BREW simulator installer is found here: https://brewx.qualcomm.com/bws/content/gi/products/sdk/3.1/en/3.1.5.179/ins… Steps to reproduce: 1. Download and install BREW SDK simulator 2. Run simulator 3. Use menu to selec "File->Change Applet Dir..." 4. Navigate to c:/Program Files/BREW 3.1.5/sdk/examples/ 5. Hit "OK" 6. Notice screen is black Expected results: Under windows, the BREW simulator will show a listing of the available BREW applets (one for each *.mif file in the directory chosen). This list appears as a series of icons inside the device's display area. -- 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.

1 17

[Bug 15703] New: LEGO Star Wars controller options
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=15703 Summary: LEGO Star Wars controller options Product: Wine Version: 1.1.6 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: infernux(a)web.de Going to "Controller Options" freezes the game, pressing "Esc" does not make it playable again. I don't know what other information / logs would be helpful, if you need anything specific just say so. This only affects the _first_ of the two games - but the 2nd seems to have a different input system anyway (requires xinpit1_2.dll for example). -- 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.

1 17

[Bug 19777] New: Ad Astra game runs very slow glBlitFramebuffer
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=19777 Summary: Ad Astra game runs very slow glBlitFramebuffer Product: Wine Version: 1.1.26 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P3 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: chrisyate+wine(a)gmail.com CC: chrisyate+wine(a)gmail.com Ad Astra is a free space flight sim available at www.a-astra.com. The game runs (as in starts) successfully, with a clean .wine prefix folder. However once it enters 3D mode the disk starts to grind, wine spits out lots of fixmes and the program runs slowly with fps around 3, max maybe 5. The following is output, over and over until you stop the game. <quote> fixme:d3d:stretch_rect_fbo >>>>>>>>>>>>>>>>> GL_INVALID_FRAMEBUFFER_OPERATION_EXT (0x506) from glBlitFramebuffer() @ device.c / 6532 fixme:d3d:state_ckeyblend Render state WINED3DRS_COLORKEYBLENDENABLE not implemented yet (repeated 6 times)... </quote> My System is Athlon XP2400+, a NVidia 6200 clone (the Zotac with 256Mb), 1.5Gb ram. Unfortunately I can't confirm whether it would work on my machine if I was running Windows natively. Any other info, please ask. -- 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.

1 16

[Bug 21023] New: SetupDiOpenDevRegKey() returns wrong HKEY
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=21023 Summary: SetupDiOpenDevRegKey() returns wrong HKEY Product: Wine Version: 1.1.34 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: setupapi AssignedTo: wine-bugs(a)winehq.org ReportedBy: mdealencar(a)gmail.com Created an attachment (id=25222) --> (http://bugs.winehq.org/attachment.cgi?id=25222) bug example In a Windows XP system SetupDiOpenDevRegKey() returns the "Device Parameters" HKEY under the device instance corresponding to the supplied (DeviceInfoSet, &DeviceInfoData) pair. Wine's SetupDiOpenDevRegKey() returns the device instance HKEY instead. The relevant registry keys are not created by Wine, so I had to import them from a Windows XP system Example: Windows HKEY returned corresponds to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_0451&Pid_6951\5&5a20206&0&1\Device Parameters Wine HKEY returned corresponds to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\Vid_0451&Pid_6951\5&5a20206&0&1 The attached registry patches and source code enable the reproduction of the bug. -- 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.

1 12

[Bug 39932] New: bat-script with quotes cann't be called using CreateProcess
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=39932 Bug ID: 39932 Summary: bat-script with quotes cann't be called using CreateProcess Product: Wine Version: 1.9.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: andrej.skvortzov(a)gmail.com Distribution: --- Created attachment 53340 --> https://bugs.winehq.org/attachment.cgi?id=53340 executable with source code to reproduce the problem This problem exists in software to configure HMI panels from OWEN and Xinje. http://www.owen.ru/catalog/graficheskaya_panel_operatora_s_sensornim_upravl… (Russian) To reproduce this problem easily minimal test program is created. See attached archive cmd_call_batch.tar.xz. Here are technical details of the problem. To appear following conditions need to be met: - bat-script is called using CreateProcess - name of bat-script is quoted - some parameters of bat-scrits are quoted. For example, "test2.bat" "param1" param2 wine runs bat-script using cmd. cmd /c "test2.bat" "param1" param2 On Windows cmd fails if name of bat-script and parameters both are quoted. To avoid this problem attached patch always removes quotes from bat-script's name before cmd is called. -- 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.

1 7

[Bug 32374] New: List box with LBS_NODATA set, has very low performance, depending on items count.
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

http://bugs.winehq.org/show_bug.cgi?id=32374 Bug #: 32374 Summary: List box with LBS_NODATA set, has very low performance, depending on items count. Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: johnfound(a)evrocom.net Classification: Unclassified Created attachment 42719 --> http://bugs.winehq.org/attachment.cgi?id=42719 Test application that illustrates the bug. Source code included. List box control, when has LBS_NODATA style set, needs very big time to process LB_SETCOUNT message (this message works only for list box with LBS_NODATA set). On Windows this message is handled for less than 1ms regardless of the count sent by LB_SETCOUNT (because the list box has nothing to allocate/reallocate when LBS_NODATA is set. It only need to set the scroll bar parameters). In WINE (every version but in v1.4 and v1.5 it is really slow) processing this message needs some amount of time, proportional to the item count set by LB_SETCOUNT. As long as this list box style is provided because of its speed, such a behavior can block the execution of the application for very long time. Small test application is attached which measures the time needed for LB_SETCOUNT to be executed on list box with LBS_NODATA set. Source code included. -- 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.

1 9

[Bug 43395] New: Wine intermittently crashes after any program terminates
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=43395 Bug ID: 43395 Summary: Wine intermittently crashes after any program terminates Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- Every so often, I see one of the following two outputs appear after Wine closes: err:ntdll:RtlLeaveCriticalSection section 0x110940 is not acquired and wine: Unhandled page fault on write access to 0x695de019 at address 0x7bc4f41e (thread 0018), starting debugger... err:seh:start_debugger Couldn't start debugger ("winedbg --auto 14 96") (1115) Read the Wine Developers Guide on how to set up winedbg or another debugger In the first message the section 0x110940 is constant; in the second the address 0x7bc4f41e is constant but the written address varies. The critical section message appears because a critical section is deleted while owned. The critical section in question appears to be that of the database in services.exe. The crash address is in ntdll/heap.c:HEAP_CreateFreeBlock. It is probably being triggered by code in RtlLeaveCriticalSection(), although it may have a different source. -- 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.

1 8

[Bug 42370] New: Sniper Elite 3 stuck at "Completing Installation 1%"
by wine-bugs＠winehq.org 01 Mar '19

01 Mar '19

https://bugs.winehq.org/show_bug.cgi?id=42370 Bug ID: 42370 Summary: Sniper Elite 3 stuck at "Completing Installation 1%" Product: Wine Version: 2.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: noonetinone(a)gmail.com Distribution: --- This is basically a repeat of the close bug reported by 'acescopezz'. Bug #41493 describes what is happening with the title SE V2. What is different about SE3 is this game includes its own copy of dllcheck.exe. 'acescopezz' posted screen grabs which relevant here. -- 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.

1 9

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 August 2017