December 2017 - Wine-bugs - list.winehq.org

[Bug 44161] New: Possible incorrect string message in "dlls/kernel32/tests /volume.c" line 263
by wine-bugs＠winehq.org 29 Dec '17

29 Dec '17

https://bugs.winehq.org/show_bug.cgi?id=44161 Bug ID: 44161 Summary: Possible incorrect string message in "dlls/kernel32/tests/volume.c" line 263 Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: petrum(a)gmail.com Distribution: --- While experimenting with a CodeSonar plugin we develop, we automatically detected a potential bug in file "dlls/kernel32/tests/volume.c" line 263, function test_GetVolumeNameForVolumeMountPointW if (!pGetVolumeNameForVolumeMountPointW) { win_skip("GetVolumeNameForVolumeMountPointW not found\n"); return; } ret = pGetVolumeNameForVolumeMountPointW(path, volume, 0); ok(ret == FALSE, "GetVolumeNameForVolumeMountPointA succeeded\n"); //HERE ok(GetLastError() == ERROR_FILENAME_EXCED_RANGE || GetLastError() == ERROR_INVALID_PARAMETER, /* Vista */ "wrong error, last=%d\n", GetLastError()); Shouldn't the string be "GetVolumeNameForVolumeMountPoint[W] succeeded\n" (i.e. with a 'W' instead of 'A')? Thanks, Petru Florin Mihancea -- 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 3

[Bug 41070] New: "Call of Duty 4" does not start: heap issues
by wine-bugs＠winehq.org 29 Dec '17

29 Dec '17

https://bugs.winehq.org/show_bug.cgi?id=41070 Bug ID: 41070 Summary: "Call of Duty 4" does not start: heap issues Product: Wine Version: 1.9.15 Hardware: x86 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: hardy.schumacher(a)gmx.de After upgrade of FreeBSD port emulators/i386-wine-devel to v1.9.15 "Call of Duty 4" does not start, but shows following messages on the console: fixme:win:EnumDisplayDevicesW ((null),0,0x32f870,0x00000000), stub! err:heap:GlobalFree (0x196de8): Page fault occurred ! Caused by bug ? err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main process heap section" wait timed out in thread 002f, blocked by 0009, retrying (60 sec) The last line is continously repeated until the process is getting killed. -- 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 3

[Bug 13319] New: In dlls/user32/edit. c EDIT_EM_ReplaceSel Clobbers Important Var When Buffer Overflows
by wine-bugs＠winehq.org 29 Dec '17

29 Dec '17

http://bugs.winehq.org/show_bug.cgi?id=13319 Summary: In dlls/user32/edit.c EDIT_EM_ReplaceSel Clobbers Important Var When Buffer Overflows Product: Wine Version: unspecified Platform: All OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: bsmith(a)sudleyplace.com Please don't hate me, but I don't have git or anything like it installed to make a formal patch, but I have benefited greatly from your work, so I'd like to repay the effort by reporting a bug even though I realize it's not in the correct format. In a Windows app, I am using edit.c as a replacement for the EDIT control in Windows. I don't use any of the other WineHQ files. Here's a short description of the bug: The handler EDIT_EM_ReplaceSel misbehaves when an insertion triggers a buffer overflow. The code correctly calls EDIT_NOTIFY_PARENT(es, EN_MAXTEXT), but shortly thereafter clobbers an important variable (strl) by using it instead of a temporary. The relevant OLD code in EDIT_EM_ReplaceSel is as follows: -------------------------------------------------------------- if ((honor_limit) && (size > es->buffer_limit)) { EDIT_NOTIFY_PARENT(es, EN_MAXTEXT); /* Buffer limit can be smaller than the actual length of text in combobox */ if (es->buffer_limit < (tl - (e-s))) strl = 0; else strl = es->buffer_limit - (tl - (e-s)); } if (!EDIT_MakeFit(es, tl - (e - s) + strl)) return; -------------------------------------------------------------- the NEW code is as follows: -------------------------------------------------------------- if ((honor_limit) && (size > es->buffer_limit)) { EDIT_NOTIFY_PARENT(es, EN_MAXTEXT); /* Buffer limit can be smaller than the actual length of text in combobox */ if (es->buffer_limit < (tl - (e-s))) strl2 = 0; else strl2 = es->buffer_limit - (tl - (e-s)); } else strl2 = strl; if (!EDIT_MakeFit(es, tl - (e - s) + strl2)) return; -------------------------------------------------------------- The calculation inside the honor_limit bracket of the value to use with the call to EDIT_MakeFit uses strl as if it were a temp var. This variable actually holds strlenW (lpsz_replace) and is used in later code as if it still had the original value. Using a (new) variable strl2 solves that problem -- this variable is declared as a UINT in the prologue. Perhaps you would prefer a name different from strl2 to better reflect its temporary nature. If you agree with the above analysis, I would greatly appreciate it if someone would make this into a patch and take it from there. I have make the above changes in my copy of edit.c and it works just fine when the buffer overflows which is how I stumbled on this bug in the first place. -- 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 46

[Bug 3200] wineconsole width/height settings not handled properly
by wine-bugs＠winehq.org 29 Dec '17

29 Dec '17

https://bugs.winehq.org/show_bug.cgi?id=3200 igor <ihormcd+wine(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ihormcd+wine(a)gmail.com -- 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 0

[Bug 42063] New: SCP Containment breach only displays top left of window
by wine-bugs＠winehq.org 27 Dec '17

27 Dec '17

https://bugs.winehq.org/show_bug.cgi?id=42063 Bug ID: 42063 Summary: SCP Containment breach only displays top left of window Product: Wine Version: 2.0-rc2 Hardware: x86 URL: http://www.scpcbgame.com/ OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: ArchLinux Created attachment 56554 --> https://bugs.winehq.org/attachment.cgi?id=56554 Broken launcher The launcher of the of the game displays only the left top part of the window, cutting off a lot of of the UI. The same happens to the actual game when running it in windowed mode, fullscreen works fine. The game is written in Blitz3D, and source-code is included in the free download. Probably not related to Bug 40919, since downgrading wine doesn't fix the issue. -- 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 42432] New: WinUAE 3.4.0: Networking over Slirp in AmigaOS 4.1 works bad.
by wine-bugs＠winehq.org 27 Dec '17

27 Dec '17

https://bugs.winehq.org/show_bug.cgi?id=42432 Bug ID: 42432 Summary: WinUAE 3.4.0: Networking over Slirp in AmigaOS 4.1 works bad. Product: Wine Version: 2.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: bobben(a)wigilius.se Distribution: --- Created attachment 57263 --> https://bugs.winehq.org/attachment.cgi?id=57263 Wine (devel) log with +winsock When using WinUAE (3.4.0) with slirp networking (only way when running AmigaOS 4.1), network transfers gets damaged (md5 and file size doesn't match) whether it's downloaded from internet or from local file server. This happens both on 32bit and 64bit Wine and WinUAE. Changing the MTU value on the AmigaOS side doesn't help either. Opening a new report since it seems to affect Linux as well. -- 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 11

[Bug 44140] New: Use less misleading language
by wine-bugs＠winehq.org 27 Dec '17

27 Dec '17

https://bugs.winehq.org/show_bug.cgi?id=44140 Bug ID: 44140 Summary: Use less misleading language Product: WineHQ Bugzilla Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: bugzilla-unknown Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com CC: austinenglish(a)gmail.com Distribution: --- There are several places in our bugzilla that use misleading language. Time and time again I have seen users complain about a label, or attempt to modify it, to be patiently reminded that the label doesn't actually mean what it appears to mean. Thus: * The status NEW for confirmed bugs. Almost useless in its intended meaning since bugs are almost never assigned, and causes complaints when bugs several years old are marked NEW. CONFIRMED, or possibly OPEN, would be better. * The version field is supposed to be the first reported version, but this is not obvious to users, who often change it to a more recent version, whereupon a bugzilla admin changes it back and informs them of this. This happens far, far too often. IMO, this field should be renamed to something more specific like "first reported version" or "earliest known version". I think we could also benefit from a second field "latest known version", which would then obviate the repeated "still present in..." comments that bugs often get. * Severity is often misunderstood by users as being severity with respect to the applicaton (i.e. a bug causing a program to crash is a "blocker", etc.) I'm not sure that I can think of a good thing to rename this to, though. If something comes to mind, it might be worthwhile to have one field represent the severity as relating to Wine, and one as relating to the application. -- 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 4

[Bug 43641] New: World of Warcraft crashes when liquid details are more than low
by wine-bugs＠winehq.org 27 Dec '17

27 Dec '17

https://bugs.winehq.org/show_bug.cgi?id=43641 Bug ID: 43641 Summary: World of Warcraft crashes when liquid details are more than low Product: Wine Version: 2.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: theodorstormgrade(a)googlemail.com Distribution: --- Created attachment 59065 --> https://bugs.winehq.org/attachment.cgi?id=59065 log with +tid,seh,virtual As the title says wow crashes for me when loading water/liquid when the settings are set to more than low for this. wow version: 7.3 build 24931. Using the overwatch staging branch. -- 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 11

[Bug 44083] New: I couldn't able to execute windows executable files
by wine-bugs＠winehq.org 27 Dec '17

27 Dec '17

https://bugs.winehq.org/show_bug.cgi?id=44083 Bug ID: 44083 Summary: I couldn't able to execute windows executable files Product: Wine Version: unspecified Hardware: x86 OS: Windows Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: swaroop.a(a)zoho.com Created attachment 59800 --> https://bugs.winehq.org/attachment.cgi?id=59800 Attachment shows the actual error message got while executing command. Command: wine notepad.exe Also tried following command: sudo wine notepad.exe After executing the above command getting following error message.Kindly provide us solution as soon as possible. Error Message: err:winediag:nulldrv_CreateWindow Application tried to create a window, but no driver could be loaded. err:winediag:nulldrv_CreateWindow Make sure that your X server is running and that $DISPLAY is set correctly. -- 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 44065] New: Worms 2 crashes on launch in clean wine prefix version 2.21
by wine-bugs＠winehq.org 27 Dec '17

27 Dec '17

https://bugs.winehq.org/show_bug.cgi?id=44065 Bug ID: 44065 Summary: Worms 2 crashes on launch in clean wine prefix version 2.21 Product: Wine Version: 2.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sve-bass(a)web.de Distribution: --- Created attachment 59782 --> https://bugs.winehq.org/attachment.cgi?id=59782 terminal output after launch crashes on launch -- 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 27