wine-bugs February 2021

wine-bugs@winehq.org

1 participants
6923 discussions

[Bug 50622] New: wldap32 calls Linux libraries with wrong conventions
by WineHQ Bugzilla 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=50622 Bug ID: 50622 Summary: wldap32 calls Linux libraries with wrong conventions Product: Wine Version: 6.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wldap32 Assignee: wine-bugs(a)winehq.org Reporter: gmascellani(a)codeweavers.com Distribution: --- The code generated by dlls/wldap32/ber.c calls liblber with wrong calling conventions. For example, looking at the object disassembly I see stuff like: 1d5bf: 48 8d 54 24 26 lea 0x26(%rsp),%rdx 1d5c4: 48 89 d9 mov %rbx,%rcx 1d5c7: e8 e4 9c ff ff callq 172b0 <ber_printf@plt> Clearly it is trying to call the Linux ber_printf with Microsoft calling conventions (while liblber expects SYSV calling conventions, using RDI, RSI and such). This causes adsldp tests to fail on my computer, in a 64-only Wine build: ../../../../libraries/liblber/encode.c:513: ber_printf: asserzione "LBER_VALID( ber )" non riuscita. wine: Assertion failed at address 00007FAF632F8CE1 (thread 0024), starting debugger... 185335.931000:00f8:00fc:trace:gio:dlls/ntdll/unix/loader.c:1463:dump_argv Starting command winedbg --auto 32 132 Unhandled exception: assertion failed in 64-bit code (0x00007faf632f8ce1). Register dump: rip:00007faf632f8ce1 rsp:000000000031f630 rbp:00007faf605dd5e1 eflags:00000246 ( - -- I Z- -P- ) rax:0000000000000000 rbx:00007faf632ba740 rcx:00007faf632f8ce1 rdx:0000000000000000 rsi:000000000031f630 rdi:0000000000000002 r8:0000000000000000 r9:000000000031f630 r10:0000000000000008 r11:0000000000000246 r12:00007faf609614f8 r13:0000000000000201 r14:00007faf60961033 r15:000000007d9dc330 Stack dump: 0x000000000031f630: 0000000000000000 00007faf6333a6c6 0x000000000031f640: 01000000fbad8000 000000007dad2f10 0x000000000031f650: 000000007dad2f75 000000007dad2f10 0x000000000031f660: 000000007dad2f10 000000007dad2f75 0x000000000031f670: 000000007dad303c 000000007dad2f10 0x000000000031f680: 000000007dad303c 0000000000000000 0x000000000031f690: 0000000000000000 0000000000000000 0x000000000031f6a0: 0000000000000000 0000000000000000 0x000000000031f6b0: fffffffe7fffffff ffffffffffffffff 0x000000000031f6c0: ffffffffffffffff ffffffffffffffff 0x000000000031f6d0: ffffffffffffffff ffffffffffffffff 0x000000000031f6e0: ffffffffffffffff ffffffffffffffff Backtrace: =>0 0x00007faf632f8ce1 execlp+0xffffffffffffffff() in libc.so.6 (0x00007faf605dd5e1) 1 0x00007faf632e2537 execlp+0xffffffffffffffff() in libc.so.6 (0x00007faf605dd5e1) 2 0x00007faf632e240f execlp+0xffffffffffffffff() in libc.so.6 (0x00007faf605dd5e1) 3 0x00007faf632f1662 execlp+0xffffffffffffffff() in libc.so.6 (0x00007faf60961033) 4 0x00007faf6095c60a ber_write+0xffffffffffffffff() in liblber-2.4.so.2 (0x00007faf60a5e75e) 5 0x00007faf60a356f6 WLDAP32_ber_printf+0x2f5(berelement=0x7d9dc330, fmt="i}") [Z:\home\giovanni\progetti\windows\wine\build64-simple\..\wine\dlls\wldap32\ber.c:392] in wldap32 (0x000000000031fa90) 6 0x0000000064342bcd search_SetSearchPreference+0x30c(iface=0xc7f010, prefs=<is not available>, count=<is not available>) [Z:\home\giovanni\progetti\windows\wine\build64-simple\..\wine\dlls\adsldp\adsldp.c:1197] in adsldp (0x0000000000c7f010) 7 0x00000000004023f8 func_ldap+0xbd7() [Z:\home\giovanni\progetti\windows\wine\build64-simple\include\iads.h:2777] in adsldp_test (0x000000000031fc20) 8 0x000000000040562e main+0x21d(argc=<is not available>, argv=<is not available>) [Z:\home\giovanni\progetti\windows\wine\build64-simple\..\wine\include\wine\test.h:569] in adsldp_test (0x0000000000c61160) 9 0x0000000000404577 mainCRTStartup+0x66() [Z:\home\giovanni\progetti\windows\wine\build64-simple\..\wine\dlls\msvcrt\crt_main.c:58] in adsldp_test (0x0000000000000000) 10 0x000000007b62dd49 BaseThreadInitThunk+0x8(unknown=<is not available>, entry=<is not available>, arg=<is not available>) [Z:\home\giovanni\progetti\windows\wine\build64-simple\..\wine\dlls\kernel32\thread.c:59] in kernel32 (0x0000000000000000) 11 0x000000007bc5c043 RtlUserThreadStart+0x82(entry=0x404510, arg=0x7fffffdaf000) [Z:\home\giovanni\progetti\windows\wine\build64-simple\..\wine\dlls\ntdll\thread.c:179] in ntdll (0x0000000000000000) 0x00007faf632f8ce1 execlp+0xffffffffffffffff in libc.so.6: movq 0x0000000000000108(%rsp),%rax -- 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 49849] New: system("CLS") don't work
by WineHQ Bugzilla 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=49849 Bug ID: 49849 Summary: system("CLS") don't work Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: antoni.przybylik(a)wp.pl Distribution: --- In my Windows console program, I'm using system("CLS") to clear the screen. Unfortunately, when I try to run this program with wine, the screen doesn't clear. This isn't this program specific bug. system("CLS") doesn't work in any of my programs. I don't think an attachment is needed. The bug is easy to reproduce. -- 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 39993] New: OllyDbg fails to change some registers
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=39993 Bug ID: 39993 Summary: OllyDbg fails to change some registers 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: b7.10110111(a)gmail.com Distribution: --- If you try to set some registers in OllyDbg while debugging an application, it'll reset them to original values after single step. This must mean that its write request has failed. To reproduce: 1. Run OllyDbg (2.x) 2. File->Open, choose any PE file, e.g. Test.exe from OllyDbg distribution 3. Press space bar, assemble something like `dw 0xfeeb` to make sure no registers are changed on single step 4. Try to change any of the following registers (others work correctly): * ST2 or any other FPU data register * FST * FCW * MXCSR * data register tags via right clicking on "empty" and selecting "zero" 5. Single step (pressing F7) 6. See the changed registers return to original values, i.e. fail to actually change -- 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 42353] New: OllyDbg Step In on a "jump to self" instruction never stops if it' s the first instruction executed by debuggee
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=42353 Bug ID: 42353 Summary: OllyDbg Step In on a "jump to self" instruction never stops if it's the first instruction executed by debuggee Product: Wine Version: 2.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: dbghelp Assignee: wine-bugs(a)winehq.org Reporter: b7.10110111(a)gmail.com Distribution: --- To reproduce 1. Launch OllyDbg (tested on 2.01) 2. Open an application, e.g. Test.exe coming in the OllyDbg distribution 3. After it loads, press <Space>, then in Assemble dialog type dw 0xfeeb and press <Enter> (or click Assemble button). This should assemble a `jmp short <ModuleEntryPoint>` instruction. 4. Close Assemble dialog 5. Press F7 (shortcut for Step In) 6. See that right-bottom corner of the window (right-hand side of status bar) has "Step in" text, which never switches back to Paused. This result is wrong: the Step In action should set TF in EFLAGS, so that next pass of control to debuggee will trap after executing one instruction. In Windows XP OllyDbg gets control back immediately after pressing F7, while in Wine this never happens at all with `jmp short $` instruction unless EIP changes. The same happens if instead of `EB FE` instruction you use `E9 FB FF FF FF`, which is `jmp near $`. Note that if you press F7 before step 3, everything works as expected. -- 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 27248] New: cannot unpack *.crx (extensions or themes) in Chrome
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=27248 Summary: cannot unpack *.crx (extensions or themes) in Chrome Product: Wine Version: 1.3.20 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fracting(a)gmail.com Created an attachment (id=34835) --> (http://bugs.winehq.org/attachment.cgi?id=34835) log: unpack crx file with chrome 1. Download the Chrome installer from http://www.google.com/chrome?platform=win&hl=en 2. make sure bug 14864 is fixed, install Chrome: wine-1.3.20-230-g456e48e $ wine ChromeSetup.exe 3. start chrome with --no-sandbox == without --no-sandbox, chrome can not open any web site. is this a know bug? or should I submit a separate bug? == $ wine chrome.exe --no-sandbox 4. open https://chrome.google.com/webstore/detail/faamegfkmmdnkpdipihbehibalfjpmpk , install the theme package . then there will be a message box says: Can not unpack extension. To safely unpack an extension, there must be a path to your profile directory that starts with a drive letter and does not contain a junction, mount point, or symlink. No such path exists for your profile. full log is attached . -- 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 8692] Multiple applications have non-working shell32 ShellView context menu items (Directory Opus 9 with Amiga Explorer Shell Extension, Total Commander 7.x)
by WineHQ Bugzilla 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=8692 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #22 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 6.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.

1 0

[Bug 50647] New: i386 DLL image icudt59.dll causes trouble on load even since COR header update.
by WineHQ Bugzilla 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=50647 Bug ID: 50647 Summary: i386 DLL image icudt59.dll causes trouble on load even since COR header update. Product: Wine Version: 6.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: loader Assignee: wine-bugs(a)winehq.org Reporter: spambox1(a)koolhoven-home.net Distribution: --- Commit 7203ad0ecd06b451116fcfe3b08e4d620e853bd5 changes out some of the testing and method of unpacking cor headers. Specifically this file would not have been run through convert_to_pe64 because it would have failed tests for code inclusion. -- 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 50565] New: Hitman: Absolution has broken rendering with Vulkan renderer
by WineHQ Bugzilla 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=50565 Bug ID: 50565 Summary: Hitman: Absolution has broken rendering with Vulkan renderer Product: Wine Version: 6.0 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 69239 --> https://bugs.winehq.org/attachment.cgi?id=69239 example Using the scope. wine-6.0-201-g2d4dd4252b0 -- 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 2

[Bug 23999] New: EMS SQL Manager 2010 Lite for PostgreSQL crashes after 10 min
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=23999 Summary: EMS SQL Manager 2010 Lite for PostgreSQL crashes after 10 min 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: adamb(a)info-s.pl Created an attachment (id=30142) --> (http://bugs.winehq.org/attachment.cgi?id=30142) wine output Wine 1.2 Linux Ubuntu 09.10 or Linux Ubuntu 10.04 EMS SQLManager Lite for PostgreSQL v.4.7.08, freeware version, downloaded from http://www.sqlmanager.net/en/products/postgresql/manager/download/5/134 To reproduce bug: 1. Install SQLManager 2. Start application and wait about 10 min Application works fine. I not found other bugs. But after 10 min wine crashes. -- 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 34

[Bug 17289] New: Slingplayer 2.0 fails with MSI error -1603: Fatal error during installation
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=17289 Summary: Slingplayer 2.0 fails with MSI error -1603: Fatal error during installation Product: Wine Version: 1.1.14 Platform: PC URL: http://downloads.slingmedia.com/go/slingbox-desktop-us OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk Created an attachment (id=19297) --> (http://bugs.winehq.org/attachment.cgi?id=19297) "Feature transfer error" screenshot Slingplayer 2.0 US tries to install the dotnet 2.0 SDK during installation but fails. Using "winetricks dotnet20" the installation continues slightly further but exits with error "-1603: Fatal error during installation". -- 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

[Bug 35562] New: Slingplayer 2 crashes when starting stream
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=35562 Bug ID: 35562 Summary: Slingplayer 2 crashes when starting stream Product: Wine Version: 1.7.10 Hardware: x86-64 URL: http://download.slingmedia.com/player/pc/SlingPlayer_2 .0.4522_Setup-Global.exe OS: Linux Status: NEW Keywords: download, regression Severity: minor Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com CC: julliard(a)winehq.org Classification: Unclassified Regression SHA1: e54503f7085a5b62dfc373aaa6b98116bde784d4 Created attachment 47489 --> http://bugs.winehq.org/attachment.cgi?id=47489 Wine 1.7.12 console output Slingplayer 2 crashes when starting to stream. This is a recent regression. e54503f7085a5b62dfc373aaa6b98116bde784d4 is the first bad commit commit e54503f7085a5b62dfc373aaa6b98116bde784d4 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Mon Dec 23 18:16:51 2013 +0100 ntdll: Allocate TLS data in all running threads on module load. :040000 040000 05e070154bacf55eb493a1aa46f61be3e89fa5e9 b23a82c25dcd2cd8ef325a53ac24adb8380d0ae0 M dlls This commit can be reverted in latest git (Wine 1.7.12) and the crash goes away. However, native qcap also works around the crash. Workarounds: 1. Ignore crash from Bug 17289 during install. 2. Native quartz (Bug 18556) 3. Native gdiplus (Bug 30899) 4. WMP10 (Bug 28669) Slingbox required to test (AFAIK). This is not Bug 34765 as that bug is too old. -- 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 30899] New: SlingPlayer 1.5 UI broken
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

http://bugs.winehq.org/show_bug.cgi?id=30899 Bug #: 30899 Summary: SlingPlayer 1.5 UI broken Product: Wine Version: 1.5.6 Platform: x86-64 URL: http://download.slingmedia.com/player/pc/SlingPlayer-S etup-EU-1.5.1.343.exe OS/Version: Linux Status: NEW Keywords: download, regression Severity: minor Priority: P4 Component: gdiplus AssignedTo: wine-bugs(a)winehq.org ReportedBy: kennybobs(a)o2.co.uk CC: madewokherd(a)gmail.com Classification: Unclassified Regression SHA1: dc3a08d840186c7692cc3cae45bdd517ab099e07 Created attachment 40512 --> http://bugs.winehq.org/attachment.cgi?id=40512 Corrupt UI in Wine 1.5.6 In Wine 1.5.6 the SlingPlayer UI appears broken (see attached screenshot). Problem not present in Wine 1.4. This is a regression. dc3a08d840186c7692cc3cae45bdd517ab099e07 is the first bad commit commit dc3a08d840186c7692cc3cae45bdd517ab099e07 Author: Vincent Povirk <vincent(a)codeweavers.com> Date: Tue Feb 14 13:50:59 2012 -0600 gdiplus: Rewrite SOFTWARE_GdipFillRegion to call brush_fill_pixels less. Reverting this commit fixes the problem. Workaround is native gdiplus. The only relevant output with built-in gdiplus is: fixme:gdiplus:resample_bitmap_pixel Unimplemented interpolation 7 A +gdiplus trace is enormous. -- 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 21

[Bug 42502] New: SlingPlayer 1.5.1 crashes on load (Assertion failure)
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=42502 Bug ID: 42502 Summary: SlingPlayer 1.5.1 crashes on load (Assertion failure) Product: Wine Version: 2.2 Hardware: x86 URL: http://download.slingmedia.com/player/pc/SlingPlayer-S etup-EU-1.5.1.343.exe OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com CC: stefan(a)codeweavers.com Blocks: 17972, 18010, 31651, 38938 Regression SHA1: 34d8b987c493544f640bf5ca0a5a6cbb3d3f4e7b Distribution: Ubuntu Created attachment 57376 --> https://bugs.winehq.org/attachment.cgi?id=57376 Wine 2.1 console output SlingPlayer 1.5.1 crashes around 98% of the time with an assertion failure, 1% of the time with a page fault, and 1% of the time it loads, but crashes later in a similar manner. The attached log shows an assertion failure, though the debugger doesn't run. wine: Assertion failed at address 0xb77df428 (thread 0009), starting debugger... *** Error in `/home/test/.wine/drive_c/Program Files/Sling Media/SlingPlayer/SlingPlayer.exe': corrupted double-linked list: 0x7c3ba500 *** This is a regression. 34d8b987c493544f640bf5ca0a5a6cbb3d3f4e7b is the first bad commit commit 34d8b987c493544f640bf5ca0a5a6cbb3d3f4e7b Author: Stefan Dösinger <stefan(a)codeweavers.com> Date: Thu Jul 30 18:50:15 2015 +0200 wined3d: Try to detect the polygon offset scale value. FEAR draws the same geometry twice, the second time using zfunc=equal. In both cases it sets a huge depth bias of -0.5, presumably to get better precision for the fragile Z comparison. The GL polygon offset we set ends up being so large that it pulls the geometry into the negative Z range. It isn't clipped (or no longer, older NV drivers probably had a separate bug there), but the Z value gets clamped to 0.0 in the first draw and doesn't match the incoming Z in the second draw. This commit cannot be automatically reverted in latest git. No known workaround. The crash is avoided by running it under Valgrind. Optional native gdiplus to work around Bug 30899. -- 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 16

[Bug 44201] New: Unimplemented function mf.dll.MFGetService
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=44201 Bug ID: 44201 Summary: Unimplemented function mf.dll.MFGetService Product: Wine Version: 3.0-rc2 Hardware: x86 URL: http://download.slingmedia.com/player/pc/SP2/SlingPlay er-2.0.3508-Setup-EMEA.exe OS: Linux Status: NEW Keywords: download, regression Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Regression SHA1: a679caedf6ebbce0e193afb200d1d888c2b9776d Distribution: Ubuntu Created attachment 59970 --> https://bugs.winehq.org/attachment.cgi?id=59970 Wine 3.0-rc2 console output SlingPlayer 2.0 crashes with unimplemented function mf.dll.MFGetService Although this is a new crash I don't feel that a regression test will achieve anything, as it is probably obvious where the issue lay. https://source.winehq.org/source/dlls/mf/mf.spec#0075 Workaround is "winetricks -q mf". -- 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 44142] New: steamwebhelper.exe crashes on wine-stagining 2.21 because NtQueryInformationFile fails
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=44142 Bug ID: 44142 Summary: steamwebhelper.exe crashes on wine-stagining 2.21 because NtQueryInformationFile fails Product: Wine-staging Version: 2.21 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: twunknown(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 59890 --> https://bugs.winehq.org/attachment.cgi?id=59890 backtrace steamwebhelper.exe crashes on wine staging 2.21 but not vanilla wine because querying FileNameInformation on a named pipe has been implemented. If NtQueryInformationFile is called after CreateFileW has been called on the named pipe (Which is what happens in the case of steamwebhelper.exe) Then it will return STATUS_BAD_DEVICE_TYPE which is unexpected and the process crashes. This is different to Windows 7 in which the call will succeed and the information will be returned. -- 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 50660] New: The "job result" emails sent to developers are too big
by WineHQ Bugzilla 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=50660 Bug ID: 50660 Summary: The "job result" emails sent to developers are too big Product: Wine-Testbot Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- When a job completes WineSendLog sends an email to the developer who submitted it. This email contains every log and test report. When the patch causes a full recompilation of Wine the resulting email can be pretty big: more than 10 MB (before base64 encoding). We could compress the logs which may make the attachments a bit less practical to read. We could also may skip the build logs if the build was sucessful, but the test reports could be big too. And all this information is available from the TestBot's Job Details page anyway. So is it really necessary to email it? Wouldn't it be sufficient to just have a link to the Job Details page and a summary of the result like in the email sent to wine-devel? -- 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 50447] New: DeSmuME-VS2019-x64-Release crash
by WineHQ Bugzilla 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=50447 Bug ID: 50447 Summary: DeSmuME-VS2019-x64-Release crash Product: Wine Version: 6.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Bertrand_mainville(a)protonmail.com Distribution: --- Created attachment 69061 --> https://bugs.winehq.org/attachment.cgi?id=69061 Terminal logs DeSmuME-VS2019-x64-Release crash. Download links: Official download link: https://ci.appveyor.com/project/zeromus/desmume/build/artifacts Archived link (direct link): https://web.archive.org/web/20210103213512/https://appveyorcidatav2.blob.co… SHA1: 4B48AD259A7C760D90F2322494BCEAED349A8BD9 -- 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 44709] New: Take live/regular screenshots
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=44709 Bug ID: 44709 Summary: Take live/regular screenshots Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The TestBot used to have a 'live screenshot' feature. This feature had to be disabled due to Libvirt/QEmu issues and because it required the TestBot server to make a long blocking call. It would be nice to bring back this feature in some form. However it may be even better to bring it in a different form and simply take screenshots every 10 or 30 seconds and timestamp them. For a lot of tests the screenshots are likely to all be identical so this could be used for deduplication so that the storage footprint would not be too large. Then the JobDetails.pl page would allow the user to browse through the screenshots for each test run (making this nice would likely require some JavaScript). >From a technical standpoint an advantage of taking regular screenshots is that it would not involve the web server. Instead it would happen in a separate thread or a fork of WineRunTask.pl (see TakeScreenshot()). So this would side-step the blocking call issue. >From a developer point of view, all long-running tests would have multiple screenshots, even after they are completed (which is not the case for 'live screenshots'). -- 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 48353] New: Use In-Reply-To when identifying patch series
by WineHQ Bugzilla 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=48353 Bug ID: 48353 Summary: Use In-Reply-To when identifying patch series Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The TestBot detects patchsets from the n/N pattern in the subject and then matches the different parts together based on the From email address and the total number of parts. This means if the TestBot receives the parts of two patchsets with the same number of parts and from the same developer at the same time it is likely to mix elements of the two patchsets, and thus fail to test them. However it is customary for patches in a series to all reference the first email in the patch series through the In-Reply-To and Message-ID fields. This could be used to resolve ambiguities in such a case. However we may not want to use this as the sole way to attach parts to the patchset in case setting In-Reply-To is not possible for some reason. -- 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 5

[Bug 41582] New: We need a different case for pathnames to detect case dependant tests as failure
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=41582 Bug ID: 41582 Summary: We need a different case for pathnames to detect case dependant tests as failure Product: Wine-Testbot Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: wine.dev(a)web.de Distribution: --- We need a different case for pathnames to detect case dependant tests as failure. My Win7 on the Laptop is using "tmp" and has failures because of such bugs. Example: http://test.winehq.org/data/e6e8ed47e6d6d245e4bbda13691eb714cf95a675/win7_d… Test fixed by: http://source.winehq.org/git/wine.git/commit/1ebbfb1a1d54c4573d79367261030d… I did not test with 'desktop' yet. -- 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 2

[Bug 40832] New: MultiSpec 2.8.2016 32-Bit: Installs fine but crashes while opening tif images
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=40832 Bug ID: 40832 Summary: MultiSpec 2.8.2016 32-Bit: Installs fine but crashes while opening tif images Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kara067(a)gmail.com Distribution: --- Created attachment 54792 --> https://bugs.winehq.org/attachment.cgi?id=54792 Backtrace log of crash. MultiSpec is an free program for multi channel images (Satellite images etc..). Program runs first. But when I try to open a tif image it crashes. Crash log is in the attachment. I use Debian 64bit. -- 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 29

[Bug 50659] New: Allow creating multiple WineTest jobs in the Special Jobs page
by WineHQ Bugzilla 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=50659 Bug ID: 50659 Summary: Allow creating multiple WineTest jobs in the Special Jobs page Product: Wine-Testbot Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The Special Jobs page allows creating one 32-bit and one 64-bit WineTest job at a time. That's usually ok but it becomes cumbersome when one wants to trigger a WineTest run on all the locale and multi-screen snapshots of a given VM after a configuration change. So it would be nice to modify the page to present the VM configurations a bit like the Submit Jobs page does. An improvement may be to present one column for each of the reconfig, win32, wow32 and wow64 configurations, as applicable to the VM on that line so one can select the precise mix of jobs to run. The could also be an extra column as a shortcut to select all the options on the line in one go. Then rather than creating one job per WineTest run it could also create just one for reconfigs, one for 32-bit WineTest, etc. -- 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 50658] New: The Special Jobs page does not take MissionCaps into account
by WineHQ Bugzilla 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=50658 Bug ID: 50658 Summary: The Special Jobs page does not take MissionCaps into account Product: Wine-Testbot Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- A lot of Windows VM configurations have the following: Role=base|winetest Missions=exe64 MissionCaps=exe32 These VMs typically mirror a base VM for which we already run both 32- and 64-bit WineTest daily. Since these configurations typically only differ in the locale, running both bitnesses again would be redundant. So the above results in only the 64-bit WineTest being run, but still allows developers to submit 32-bit jobs if desired (e.g. if they want to run a 32-bit binary). But this configuration throws the "Special Jobs" page off and causes it to create an empty job when trying to run the 32-bit WineTest. It should really see that MissionCaps allows running 32-bit tests. However the issue comes from the shared AddWindowsTestJob() function: it should take MissionCaps into account without changing the behavior of CheckForWinetestUpdate.pl. -- 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 38939] New: u-blox U-center 8,17 crashes when attempting to open view->Packet Console
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=38939 Bug ID: 38939 Summary: u-blox U-center 8,17 crashes when attempting to open view->Packet Console Product: Wine Version: 1.6.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: david.t.kerns(a)gmail.com Distribution: --- Created attachment 51875 --> https://bugs.winehq.org/attachment.cgi?id=51875 stack trace Cent-OS 6.4 yum install wine (from epel) wine u-center.exe select com port most things work as expected View-> Packet Console crashes every time -- 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 47800] New: Better detect Windows reboots
by WineHQ Bugzilla 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=47800 Bug ID: 47800 Summary: Better detect Windows reboots Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- When a test crashes Windows in a VM we get typically get an error like this: channel 2: open failed: connect failed: Connection refused channel 2: open failed: connect failed: Connection refused channel 2: open failed: connect failed: Connection refused An error occurred while waiting for the test to complete: network read got a premature EOF (wait2/connect:AgentVersion.h:0/9) The test VM has crashed, rebooted or lost connectivity (or the TestAgent server died) The previous 2 run(s) terminated abnormally Nowadays most VMs autologin and autostart the TestAgent server with the --show-restarts option. What this does is pop up a dialog saying: TestAgentd.exe was restarted (2). Did Windows reboot? This is a telltale sign that Windows indeed rebooted (or that the TestBot administrator incorrectly set up the VM but then you'd see that dialog in all screenshots of that VM). The way this works is that when given the --show-restarts option the TestAgent server increases a persistent counter every time it starts. Normally the TestBot administrator will have reset that counter so it will be set to one such that a reboot will push it to 2 prompting this dialog. What's interesting is that this counter is accessible from the client with getproperties("start.counter"). So the WineRun*.pl script can know if the VM was indeed rebooted. But from the log above we also notice that they don't leave enough time for the VM to reboot and thus fail to reestablish the connection to the TestAgent server. This could be solved by adding a call to SetConnectionTimeout(,,$WaitForBoot) in the strategic places. Then in most cases the WineRun*.pl scripts could conclusively say that Windows crashed and rebooted. -- 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

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 2021