August 2021 - Wine-bugs - list.winehq.org

[Bug 26035] New: ChipGenius cannot detect USB device
by wine-bugs＠winehq.org 11 Sep '21

11 Sep '21

http://bugs.winehq.org/show_bug.cgi?id=26035 Summary: ChipGenius cannot detect USB device Product: Wine Version: 1.3.13 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mountmgr.sys AssignedTo: wine-bugs(a)winehq.org ReportedBy: fracting(a)gmail.com ChipGenius is a small green software for detecting USB pid/vid ,it returns the device name, interface speed, serial number, equipment version, and provides relevant information to download address. See http://translate.google.com/translate?js=n&prev=_t&hl=en&ie=UTF-8&layout=2&… for a google translated introduction. ChipGenius can be download free on its website ( http://dl.mydigit.net/2010/09/chipgenius.html ) , or a personal mirror here: https://docs.google.com/leaf?id=0BxjsxTbiBaUHMDI5OWIxYTktZDBkOS00ODE3LWExOW… Normally on WinXP, while running ChipGenius, it will draw a device tree and auto detect usb devices and redraw device tree whenever a usb device is pluging or unpluging. However, ChipGenius didn't draw any device tree on wine. Here is the log: $ winetricks -q vb6run $ wine '/home/fracting/Wine/USB/ChipGenius/ChipGenius.exe' err:menubuilder:init_xdg error looking up the desktop directory fixme:ole:OleLoadPictureEx (0xa1f5ec,1414,0,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f6d4), partially implemented. fixme:ole:OleLoadPictureEx (0xa1f5ec,830,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f6a4), partially implemented. fixme:ole:OleLoadPictureEx (0xa1f5ec,1354,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f6a4), partially implemented. fixme:ole:OleLoadPictureEx (0xa1f5ec,2238,1,{7bf80980-bf32-101a-8bbb-00aa00300cab},x=0,y=0,f=0,0x32f6a4), partially implemented. fixme:ole:OLEPictureImpl_SaveAsFile (0x18ae50)->(0x198fb8, 0, (nil)), hacked stub. fixme:mountmgr:harddisk_ioctl returning zero-filled buffer for IOCTL_VOLUME_GET_VOLUME_DISK_EXTENTS fixme:mountmgr:harddisk_ioctl unsupported ioctl 2d1400 fixme:win:RegisterDeviceNotificationA (hwnd=0x1006e, filter=0x32f82c,flags=0x00000000) returns a fake device notification handle! fixme:win:UnregisterDeviceNotification (handle=0xcafecafe), STUB! fixme:ole:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393} fixme:ole:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4f92-6699-11cf-b70c-00aa0060d393} fixme:ole:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393} fixme:ole:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393} fixme:ole:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393} fixme:ole:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4f92-6699-11cf-b70c-00aa0060d393} fixme:ole:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393} fixme:ole:OLEPictureImpl_FindConnectionPoint no connection point for {33ad4ed2-6699-11cf-b70c-00aa0060d393} I also test chipgenius with Alexander Morozov's USB patchset, but it doesn't work either. Best 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 15

[Bug 51655] New: iphlpapi regression prevents Samsung SDK from working properly
by WineHQ Bugzilla 10 Sep '21

10 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51655 Bug ID: 51655 Summary: iphlpapi regression prevents Samsung SDK from working properly Product: Wine Version: 6.14 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: iphlpapi Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Probably related to 51620. I have a similar issue with the Samsung SDK. Regression SHA 3bace8862f1b49e40574d1c9647e6984f10d026f, but only with a debug version of wine, release seems okay. 32bit WINEPREFIX though, so that patch from there doesn't help. -- 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 51672] New: Imperiums: Greek Wars has small black window on launch (caused by wrong position).
by WineHQ Bugzilla 10 Sep '21

10 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51672 Bug ID: 51672 Summary: Imperiums: Greek Wars has small black window on launch (caused by wrong position). Product: Wine Version: 6.15 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: gabrielopcode(a)gmail.com Distribution: --- The game depends on some specific detail on Windows for Maximized position placement. Windows seems to "forget" the maximized placement for any non-maximized windows, as well as maximized top-level windows that cover the work area. Presumably, since applications typically save window positions via placement (such as on exit) to reload them later, it does this to prevent those apps from having weird maximized window positions when reloaded on a different screen or a screen having a different work area, so in this case it forgets it to simply say "just maximize to the entire work area" like normal maximized windows. The game relies on this implicitly, because it changes styles and borders, which affect its position and size. First, it creates the main game window as hidden with the WS_CLIPCHILDREN | WS_MAXIMIZE | WS_MAXIMIZEBOX styles and the WS_EX_CONTROLPARENT | WS_EX_APPWINDOW exstyles set, so it's actually maximized. Implicitly, it ends up having a border around it, so it's position is something like (-3,-3) on the screen (because it's maximized and not fullscreen), covering the entire screen +3 on other side too. Then, before showing the window, it sets the style on it again to the same thing, which actually removes the implicit border. Since the window is still hidden, it doesn't get updated by anything (WM or not) so its position remains at (-3,-3). This is still correct even on Windows, despite the fact it's in the wrong position technically speaking, so there's nothing wrong here. The problem comes next: it shows the window with SW_MAXIMIZE. On Windows, this resets its position to (0,0) since there is no border now. Wine currently keeps its position at (-3,-3), although it does size the window down to be the size of the work area / screen. So for example for 1920x1080 size, this would have its rect be (-3,-3)-(1917,1077) instead of (0,0)-(1920,1080) as it is on Windows. This completely confuses the game, rendering a small black window, which makes it unplayable. -- 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 23979] New: SMSDV's main window is empty
by wine-bugs＠winehq.org 10 Sep '21

10 Sep '21

http://bugs.winehq.org/show_bug.cgi?id=23979 Summary: SMSDV's main window is empty Product: Wine Version: 1.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: b7.10110111(a)gmail.com Here's the screenshot: http://appdb.winehq.org/appimage.php?iId=31576 If i click on the empty space on the window or even in the text enter widget, i can drag the window. Choosing "About wine" after right-clicking the window makes About dialog behave the same as the main window. -- 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 13

[Bug 51702] New: AFxW: the working directory of launched Unix application isn't set
by WineHQ Bugzilla 10 Sep '21

10 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51702 Bug ID: 51702 Summary: AFxW: the working directory of launched Unix application isn't set Product: Wine Version: 6.15 Hardware: x86-64 URL: https://web.archive.org/web/20210811072930if_/http://a kt.d.dooo.jp/lzh/afxw32_165.zip OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: sagawa.aki+winebugs(a)gmail.com Distribution: Ubuntu Created attachment 70575 --> https://bugs.winehq.org/attachment.cgi?id=70575 Configuration file for AFxW to launch Unix application AFxW[1], aka あふｗ in Japanese, is an ultra-low functionality two-pane file manager. With Wine 6.13 or later, working directory of launched Unix application is always '/'. This is a regression because the working directory corresponds to AFxW's active directory pane with Wine 6.12. @kusyan, a reporter on Twitter, wrote up the following scenario in Japanese. Thanks to the scenario, I can confirm this issue. Steps to reproduce: 1. unzip afxw32_165.zip 2. Put attached AFXW.DEF to the directory which AFXW.EXE exists. 3. If you don't have /usr/bin/lxterminal, rewrite line 6 of AFXW.DEF to your favorite Unix terminal software (after KEY_01=). 4. LANG=ja_JP.UTF-8 wine AFXW.EXE 5. Press [F2] to launch the specified terminal software. 6. Type 'pwd' (without quotes) and [Enter] in the new terminal window. Expected result: The terminal shows an Unix directory corresponding to AFxW's active directory pane. For instance, if your AFxW's active directory pane shows 'C:\', the terminal will show '/home/yourname/.wine/drive_c'. Actual result: The terminal shows '/'. It's not a directory corresponding to AFxW's active directory pane. [1] http://akt.d.dooo.jp/akt_afxw.html -- 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 40700] New: Page Scrolling Bar of PDF Ereaser Not Appear
by wine-bugs＠winehq.org 10 Sep '21

10 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=40700 Bug ID: 40700 Summary: Page Scrolling Bar of PDF Ereaser Not Appear Product: Wine Version: 1.9.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: yousifjkadom(a)yahoo.com Distribution: --- Created attachment 54584 --> https://bugs.winehq.org/attachment.cgi?id=54584 (1) Hi. I test PDF Ereaser on Wine 1.9.11 A new bug appear: page scrolling bar not appear! Now I can not use mouse for scrolling across pages. Instead I have to use arrows keys to navigate from page to page. Please look to screenshots: (1) in windows OS & (2) in Linux using Wine 1.9.11 Please look on red arrows that I added in (1) & red & blue oval markers that I added in (2) -- 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 51693] New: ntdll:info fails on Windows 7 64-bit
by WineHQ Bugzilla 10 Sep '21

10 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51693 Bug ID: 51693 Summary: ntdll:info fails on Windows 7 64-bit Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com ntdll:info fails on Windows 7 64-bit: info.c:891: Test failed: 63: got 0x0 and 12 (expected STATUS_SUCCESS and 24) info.c:891: Test failed: 62: got 0x0 and 12 (expected STATUS_SUCCESS and 24) ... info.c:891: Test failed: 24: got 0x0 and 12 (expected STATUS_SUCCESS and 24) info.c:899: Test failed: 23: got 0x0 and 12 (expected STATUS_INFO_LENGTH_MISMATCH and 24) https://test.winehq.org/data/patterns.html#ntdll:info This failure has been confirmed to be caused by the commit below: commit 37ed43a1717fd7a58b8d6733dc65783bd5c57709 Author: Alexandre Julliard <julliard(a)winehq.org> AuthorDate: Mon Aug 2 14:53:11 2021 +0200 ntdll: Fix the SYSTEM_CACHE_INFORMATION structure definition. Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> -- 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 45133] New: NewProcessFromToken tool (.NET app) from Google sandbox-attacksurface-analysis-tools v1.1.x wants ' ntdll.NtQueryInformationProcess' to support 'ProcessSessionInformation'
by wine-bugs＠winehq.org 10 Sep '21

10 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=45133 Bug ID: 45133 Summary: NewProcessFromToken tool (.NET app) from Google sandbox-attacksurface-analysis-tools v1.1.x wants 'ntdll.NtQueryInformationProcess' to support 'ProcessSessionInformation' Product: Wine Version: 3.7 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, needed by 'NewProcessFromToken' .NET-based app from https://github.com/google/sandbox-attacksurface-analysis-tools --- quote --- sandbox-attacksurface-analysis-tools (c) Google Inc. 2015, 2016, 2017, 2018 Developed by James Forshaw This is a small suite of tools to test various properties of sandboxes on Windows. Many of the checking tools take a -p flag which is used to specify the PID of a sandboxed process. The tool will impersonate the token of that process and determine what access is allowed from that location. Also it's recommended to run these tools as an administrator or local system to ensure the system can be appropriately enumerated. CheckExeManifest: Check for specific executable manifest flags. CheckNetworkAccess: Check access to network stack. NewProcessFromToken: Create a new process based on existing token. TokenView: View and manipulate various process token values. NtApiDotNet: A basic managed library to access NT system calls and objects. NtObjectManager: A powershell module which uses NtApiDotNet to expose the NT object manager. ViewSecurityDescriptor: View the security descriptor from an SDDL string or an inherited object. --- quote --- It's actually a pretty neat "testsuite" for native API, Wine could benefit from it. Prerequisite: * 32-bit WINEPREFIX * .NET Framework 4.5 -> 'winetricks -q dotnet45' NOTE: needs at least one running process (Windows pids -> command line) --- snip --- Wine-dbg>info process pid threads executable (all id:s are in hex) 00000033 1 'notepad.exe' 00000013 4 'explorer.exe' 0000000e 5 'services.exe' 00000028 4 \_ 'winedevice.exe' 00000023 3 \_ 'plugplay.exe' 0000001b 4 \_ 'winedevice.exe' --- snip --- --- snip --- $ WINEDEBUG=+seh,+relay,+ntdll wine ./NewProcessFromToken.exe -p 51 notepad.exe >>log.txt 2>&1 ... 004f:Call ntdll.NtQueryInformationProcess(0000014c,00000018,0011e300,00000004,0032f39c) ret=03f67d78 004f:trace:ntdll:NtQueryInformationProcess (0x14c,0x00000018,0x11e300,0x00000004,0x32f39c) 004f:fixme:ntdll:NtQueryInformationProcess (process=0x14c) Unimplemented information class: ProcessSessionInformation 004f:Ret ntdll.NtQueryInformationProcess() retval=c0000003 ret=03f67d78 004f:Call KERNEL32.RaiseException(e0434352,00000001,00000005,0032f274) ret=00788fdb 004f:trace:seh:raise_exception code=e0434352 flags=1 addr=0x7b446ec7 ip=7b446ec7 tid=004f 004f:trace:seh:raise_exception info[0]=80131600 004f:trace:seh:raise_exception info[1]=00000000 004f:trace:seh:raise_exception info[2]=00000000 004f:trace:seh:raise_exception info[3]=00000000 004f:trace:seh:raise_exception info[4]=00630000 004f:trace:seh:raise_exception eax=7b435589 ebx=00000005 ecx=00000000 edx=0032f220 esi=0032f220 edi=0032f1e0 004f:trace:seh:raise_exception ebp=0032f1b8 esp=0032f154 cs=f7bb0023 ds=32002b es=f7be002b fs=f7be0063 gs=f7be006b flags=00000212 004f:trace:seh:call_vectored_handlers calling handler at 0x7ba398 code=e0434352 flags=1 004f:Call KERNEL32.GetLastError() ret=007ba3c6 004f:Ret KERNEL32.GetLastError() retval=00000000 ret=007ba3c6 ... 004f:Call KERNEL32.CreateProcessW(00000000,010e2280 L"notepad.exe",00000000,00000000,00000000,00080000,00000000,00000000,0032f24c,0032f36c) ret=03f6485b ... --- snip --- The failure to query the process session ID is not critical (it will still launch new process) .. hence "wants" in summary. Source: https://github.com/google/sandbox-attacksurface-analysis-tools/blob/43ab463… $ sha1sum Release-v1.1.14.7z 8cd7991e675a995a3d67ef0aca2a8bf0e1512f6a Release-v1.1.14.7z $ du -sh Release-v1.1.14.7z 384K Release-v1.1.14.7z $ wine --version wine-3.7-65-ge637a6f0bf Regards -- 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 41548] New: draftsight 32bit crashes during registration on ubuntu 14.04 lts
by wine-bugs＠winehq.org 10 Sep '21

10 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=41548 Bug ID: 41548 Summary: draftsight 32bit crashes during registration on ubuntu 14.04 lts Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: scottdickerson1(a)gmail.com Distribution: --- Created attachment 55880 --> https://bugs.winehq.org/attachment.cgi?id=55880 program error details draftsight crashes while trying to register it. using ubuntu 14.04 -- 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 41355] New: Microsoft Access 2007 is not opening a legitimate access file
by wine-bugs＠winehq.org 10 Sep '21

10 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=41355 Bug ID: 41355 Summary: Microsoft Access 2007 is not opening a legitimate access file Product: Wine Version: 1.6-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: santanu_chatterjee59(a)yahoo.co.in Distribution: --- Created attachment 55706 --> https://bugs.winehq.org/attachment.cgi?id=55706 Microsoft Access 2007 is not opening a legitimate access file Microsoft Access 2007 is not opening a legitimate access field -- 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