wine-bugs November 2019

wine-bugs@winehq.org

1 participants
7562 discussions

[Bug 36071] New: kernel32/pipe tests fail under valgrind
by wine-bugs＠winehq.org 27 Nov '19

27 Nov '19

https://bugs.winehq.org/show_bug.cgi?id=36071 Bug ID: 36071 Summary: kernel32/pipe tests fail under valgrind Product: Wine Version: 1.7.17 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase Severity: minor Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Depends on: 26119 The tests have several valgrind warnings (bug 26119), but also fail under valgrind: austin@aw25 ~/wine-valgrind/dlls/kernel32/tests $ rm *ok ; make pipe.ok rm: cannot remove ‘*ok’: No such file or directory ../../../tools/runtest -q -P wine -T ../../.. -M kernel32.dll -p kernel32_test.exe.so pipe && touch pipe.ok preloader: Warning: failed to reserve range 00110000-68000000 preloader: Warning: failed to reserve range 7f000000-82000000 pipe.c:459: Test failed: ConnectNamedPipe pipe.c:469: Test failed: ReadFile pipe.c:470: Test failed: short read pipe.c:473: Test failed: WriteFile pipe.c:480: Test failed: DisconnectNamedPipe pipe.c:459: Test failed: ConnectNamedPipe pipe.c:469: Test failed: ReadFile pipe.c:470: Test failed: short read pipe.c:473: Test failed: WriteFile pipe.c:480: Test failed: DisconnectNamedPipe pipe.c:938: Test failed: client opening named pipe pipe.c:943: Test failed: WriteFile to client end of pipe pipe.c:944: Test failed: write file len pipe.c:946: Test failed: ReadFile from client end of pipe pipe.c:947: Test failed: read file len pipe.c:951: Test failed: CloseHandle pipe.c:938: Test failed: client opening named pipe pipe.c:943: Test failed: WriteFile to client end of pipe pipe.c:944: Test failed: write file len pipe.c:946: Test failed: ReadFile from client end of pipe pipe.c:947: Test failed: read file len pipe.c:951: Test failed: CloseHandle pipe.c:612: Test failed: overlapped ConnectNamedPipe pipe.c:629: Test failed: GetOverlappedResult ConnectNamedPipe pipe.c:640: Test failed: overlapped ReadFile pipe.c:658: Test failed: overlapped ReadFile pipe.c:664: Test failed: overlapped WriteFile pipe.c:682: Test failed: overlapped WriteFile pipe.c:687: Test failed: DisconnectNamedPipe pipe.c:938: Test failed: client opening named pipe pipe.c:943: Test failed: WriteFile to client end of pipe pipe.c:944: Test failed: write file len pipe.c:946: Test failed: ReadFile from client end of pipe pipe.c:947: Test failed: read file len pipe.c:951: Test failed: CloseHandle pipe.c:734: Test failed: overlapped ConnectNamedPipe got 0 err 231 pipe.c:761: Test failed: overlapped ReadFile, err=233 pipe.c:938: Test failed: client opening named pipe pipe.c:943: Test failed: WriteFile to client end of pipe pipe.c:944: Test failed: write file len pipe.c:946: Test failed: ReadFile from client end of pipe pipe.c:947: Test failed: read file len pipe.c:951: Test failed: CloseHandle pipe.c:938: Test failed: client opening named pipe pipe.c:943: Test failed: WriteFile to client end of pipe pipe.c:944: Test failed: write file len pipe.c:946: Test failed: ReadFile from client end of pipe pipe.c:947: Test failed: read file len pipe.c:951: Test failed: CloseHandle pipe.c:938: Test failed: client opening named pipe pipe.c:943: Test failed: WriteFile to client end of pipe pipe.c:944: Test failed: write file len pipe.c:946: Test failed: ReadFile from client end of pipe pipe.c:947: Test failed: read file len pipe.c:951: Test failed: CloseHandle pipe.c:764: Test failed: ReadFile GetQueuedCompletionStatus failed, errno=258 pipe.c:776: Test failed: overlapped WriteFile failed, err=233 pipe.c:427: Test failed: alarm Makefile:529: recipe for target 'pipe.ok' failed make: *** [pipe.ok] Error 1 note that this is a separate issue from bug 35781. -- 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 46342] New: kernel32/tests/ pipe.c shows uninitialized memory use in test_TransactNamedPipe()
by wine-bugs＠winehq.org 27 Nov '19

27 Nov '19

https://bugs.winehq.org/show_bug.cgi?id=46342 Bug ID: 46342 Summary: kernel32/tests/pipe.c shows uninitialized memory use in test_TransactNamedPipe() Product: Wine Version: 4.0-rc3 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Gentoo ../../../tools/runtest -q -P wine -T ../../.. -M kernel32.dll -p kernel32_test.exe.so pipe && touch pipe.ok ==8919== Syscall param writev(vector[...]) points to uninitialised byte(s) ==8919== at 0x4356813: writev (writev.c:26) ==8919== by 0x7BC75457: send_request (server.c:228) ==8919== by 0x7BC76158: server_call_unlocked (server.c:288) ==8919== by 0x7BC916EC: virtual_locked_server_call (virtual.c:2083) ==8919== by 0x7BC41C1A: server_ioctl_file (file.c:1533) ==8919== by 0x7BC447A5: NtFsControlFile (file.c:1733) ==8919== by 0x7B470FA4: TransactNamedPipe (sync.c:1747) ==8919== by 0x4B26CCC: _overlapped_transact_failure (pipe.c:3118) ==8919== by 0x4B2748E: test_TransactNamedPipe (pipe.c:3346) ==8919== by 0x4B27817: func_pipe (pipe.c:3735) ==8919== by 0x4B6E8E4: run_test (test.h:617) ==8919== by 0x4B6F322: main (test.h:701) ==8919== Address 0x4eafd22 is on thread 1's stack ==8919== in frame #8, created by test_TransactNamedPipe (pipe.c:3341) ==8919== Uninitialised value was created by a stack allocation ==8919== at 0x4B27446: test_TransactNamedPipe (pipe.c:3341) ==8919== -- 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 48182] New: Jasc Paint Shop Pro 8 crash when using some tools
by WineHQ Bugzilla 27 Nov '19

27 Nov '19

https://bugs.winehq.org/show_bug.cgi?id=48182 Bug ID: 48182 Summary: Jasc Paint Shop Pro 8 crash when using some tools Product: Wine Version: 4.0.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: myrvina(a)caramail.fr Distribution: --- Created attachment 65820 --> https://bugs.winehq.org/attachment.cgi?id=65820 Detail of error message in Paint Shop Pro 8 after using smudge tool Update from ppa from latest stable version of WineHq to version 4.03. Jasc Paint Shop Pro 8 (English version) was working fine but now crashes on using some tools such as preset shape tool, smudge, lighten/darken, soften brushes, magic wands while other tools including filters work fine. Enclosing the message I got from crash. -- 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 1

[Bug 48179] New: When trying to buy gems from the store on MtGArena application crashes complaining about ZFGameBrowser.exe
by WineHQ Bugzilla 26 Nov '19

26 Nov '19

https://bugs.winehq.org/show_bug.cgi?id=48179 Bug ID: 48179 Summary: When trying to buy gems from the store on MtGArena application crashes complaining about ZFGameBrowser.exe Product: Wine Version: 4.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alecfvn(a)gmail.com Distribution: --- Created attachment 65814 --> https://bugs.winehq.org/attachment.cgi?id=65814 Backtrace for trying to buy gems from the store In MtGArena, when I try to buy gems from the store, it tries to load the store and then crashes the app complaining about ZFGameBrowser.exe with the attached backtrace. I'm running Kubuntu 18.04 and Wine 4.0.2. System information for the app: Wine build: wine-3.20 Platform: i386 (WOW64) Version: Windows 10 Host system: Linux Host version: 4.15.0-70-generic -- 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 10

[Bug 48166] New: test.winehq.org Provide a way to track individual failures
by WineHQ Bugzilla 26 Nov '19

26 Nov '19

https://bugs.winehq.org/show_bug.cgi?id=48166 Bug ID: 48166 Summary: test.winehq.org Provide a way to track individual failures Product: WineHQ.org Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- A test unit may have multiple unrelated test failures. Some may fail on recent Windows 10 machines while others may only happen in certain locales or some graphics cards. Untangling these can actually be automated. The root is to merge the failures of two reports together while associating each failure with the tag or the report(s) it originates from. To do so diff the two error lists. * Failures that are present in both get both tags. * Failures that are only present in the first report get only that tag. * Same thing for failures that are present only in the second report. And all failures are integrated in the merged list in the order they are returned in by Algorithm::Diff. Once two failure lists have been merged together, it's possible to continue merging more failure lists. This allows getting a unified list of the failures of a given commitid, and appending that commitid to the tags allows building a complete list of all the available history. Then one can group all failures that have the exact same set of tag+commitids combinations together. Then, since the failures in different groups don't all happen together they must depend on different factors. Intermittent failures, timeouts, crashes ---------------------------------------- If two failures are related but a random timeout or crash sometimes occurs between them they might end up being incorrectly split in two separate groups. So if a crash or a timeout occurs, any other failure in that run should be ignored when grouping failures together. This can be achieved by prefixing the tag with a '*' if a crash or timeout occured. Then, when grouping failures together, ignore the entries where the tag starts with a '*'. But when building the occurence pattern, do use the entries starting with a '*' to show all the test runs where at least one of the failures in the group occurred. Because entries starting with a '*' are ignored when building failure groups, failures that cause a crash/timeout and the crash/timeout line itself will be part of no failure group. So do a second pass over the unassigned failures, this time not ignoring the entries with a '*'. This will create groups composed of the crash/timeout and any related failures. New failures ------------ This analysis indicates where and when a given failure group happened. This means it can also detect new failures. It would not be useful to define a new failure as one that never happened before the latest commit: blink and you might miss it. Instead it should be expanded to all failures that only happened in the first half of the available history. This may sometimes falsely treat rare intermittent failures as new but that should be rare enough. Presentation of the results --------------------------- The results can be presented on a page with one box per test unit like the 'Full Report' pages. A 'details' link under the test unit name on the test failrues pattern page would link to the relevant section of the full page. Inside each box there would be a sequence of lines showing the failures in a group, followed by the usual pattern showing which machines the failure happens on; then the next failure group, etc. For instance: console.c:270: Test failed: got 16, expected 6 console.c:275: Test failed: got 16, expected 6 .....F..F...F..F.mmm Win8 vm1 ......FF.e...FF.e..F Win8 vm1-ja 096c:console: unhandled exception c0000005 at 6F384E33 .....CC Win8 vm2-new As usual the items in the pattern would link to the relevant pages, allowing to dig deeper into the issue. The same color coding would be used for the pattern but since failure groups always have the same number of failures only one color would be used for the F code. The failure line number will change from one run to the next so zero it out or only retain one value at random. Similarly, if the failure contains timing information (see bug 48094), remove the timing information. If a failure is identified as new, put its lines in bold orange, like on the TestBot. This will allow quick identification of the new failures on the page. -- 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 1

[Bug 48177] New: Microsoft SQL Server Management Studio 18.4 installer silently exits
by WineHQ Bugzilla 26 Nov '19

26 Nov '19

https://bugs.winehq.org/show_bug.cgi?id=48177 Bug ID: 48177 Summary: Microsoft SQL Server Management Studio 18.4 installer silently exits Product: Wine Version: 4.20 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: damjan.jov(a)gmail.com Distribution: --- $ wine SSMS-Setup-ENU.exe 0009:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub 0009:fixme:ntdll:NtQueryInformationToken QueryInformationToken( ..., TokenElevation, ...) semi-stub (exits immediately, no UI) $ md5sum SSMS-Setup-ENU.exe 65d034096b63c6ec9051951bcf10088c SSMS-Setup-ENU.exe -- 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 48151] New: AceMoney (or any other non-unicode program): can't enter cyrillic letters into text fields when using custom keyboard layout
by WineHQ Bugzilla 26 Nov '19

26 Nov '19

https://bugs.winehq.org/show_bug.cgi?id=48151 Bug ID: 48151 Summary: AceMoney (or any other non-unicode program): can't enter cyrillic letters into text fields when using custom keyboard layout Product: Wine Version: 4.20 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ttyusupov(a)gmail.com macOS version: 10.14.6 (18G1012) Link to a free version of the app: http://cdn.mechcad.net/downloads/AceMoneyLiteSetup.exe How to reproduce: 1) Install custom keyboard layout with Cyrillic support, for example: https://github.com/asizikov/osx-russian-keyboard 2) Setup AceMoneyLite under Wine. Actually you don't need even complete setup - you can just run the installer and try to type Cyrillic letter using custom keyboard layout into a text field where it asks for the path to install. Expected result: - Cyrillic letters entered and shown correctly. Actual result: - Cyrillic letters are entered and displayed as question marks '?'. Note: I've used LANG, LC_ALL and other variables with different values including ru_RU.UTF-8 - this help with showing text labels, but doesn't affect entering Cyrillic letters into text field for non-unicode apps. -- 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 18985] New: Two bugs in HTML-kit
by wine-bugs＠winehq.org 26 Nov '19

26 Nov '19

http://bugs.winehq.org/show_bug.cgi?id=18985 Summary: Two bugs in HTML-kit Product: Wine Version: 1.1.23 Platform: PC URL: http://htmlkit.com/download/ OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: comctl32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: xerox_xerox2000(a)yahoo.co.uk Hi, a user reported trouble with this app here: http://ubuntuforums.org/showthread.php?t=1190483 I gave it a try and actually there seem to be two bugs: 1. All icons in toolbar are black. In the console the line appears: err:imagelist:IMAGELIST_InternalExpandBitmaps creating new image bitmap (x=25600 y=16)! 2. After doing from the menu: Edit->Prefernces->OK an access violation occurs and the app is no longer usable. Both bugs are gone using native comctl32 -- 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 30

[Bug 47706] New: ntdll: Compiler warnings regression on x86_64 [stable]
by wine-bugs＠winehq.org 25 Nov '19

25 Nov '19

https://bugs.winehq.org/show_bug.cgi?id=47706 Bug ID: 47706 Summary: ntdll: Compiler warnings regression on x86_64 [stable] Product: Wine Version: 4.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: kakurasan(a)gmail.com Regression SHA1: 95f94568158caaf4fefe2e14f21bb3f0701577c9 Distribution: --- Created attachment 65177 --> https://bugs.winehq.org/attachment.cgi?id=65177 Warning messages I'll submit a patch to wine-devel. --- Architecture --- x86_64, Win64 build --- Compiler --- gcc (Ubuntu 8.3.0-6ubuntu1) 8.3.0 --- Result of "git bisect" --- 95f94568158caaf4fefe2e14f21bb3f0701577c9 is the first bad commit commit 95f94568158caaf4fefe2e14f21bb3f0701577c9 Author: Vijay Kiran Kamuju <infyquest(a)gmail.com> Date: Tue Apr 16 11:27:16 2019 +0200 ntdll: Report system information SystemPerformanceInformation info class. Based on patch from Michael Müller. Signed-off-by: Vijay Kiran Kamuju <infyquest(a)gmail.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> (cherry picked from commit 99ba65a1ea2c1546a61c3ed40996cbfee9d25f69) Signed-off-by: Michael Stefaniuc <mstefani(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.

2 4

[Bug 12332] New: driver dev kit won't install
by wine-bugs＠winehq.org 25 Nov '19

25 Nov '19

http://bugs.winehq.org/show_bug.cgi?id=12332 Summary: driver dev kit won't install Product: Wine Version: 0.9.58. Platform: PC-x86-64 URL: http://download.microsoft.com/download/9/0/f/90f019ac- 8243-48d3-91cf-81fc4093ecfd/1830_usa_ddk.iso OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: setupapi AssignedTo: wine-bugs(a)winehq.org ReportedBy: htl10(a)users.sourceforge.net This seems to be a problem with setupapi rather than msi... in an case, I am just after the documentations and the examples, so I just like it to unpack nicely, the result doesn't need to be functional... -- 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 18

Jump to page:

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 November 2019