wine-bugs November 2020

wine-bugs@winehq.org

1 participants
7093 discussions

[Bug 19624] New: winspool.drv needs to properly handle local printer server config data queries (XPSEPSC update/installer)
by wine-bugs＠winehq.org 08 Jan '21

08 Jan '21

http://bugs.winehq.org/show_bug.cgi?id=19624 Summary: winspool.drv needs to properly handle local printer server config data queries (XPSEPSC update/installer) Product: Wine Version: 1.1.27 Platform: PC URL: http://go.microsoft.com/fwlink/?LinkId=96332 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: spooler AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, that component is a needed prerequisite for .NET 3.0 Framework SP1, 3.5, 3.5 SP1 Fortunately can be reproduced without all the .NET installer mess: clean WINEPREFIX, run the installer from link. Local printer server has no name associated with it (NULL), leading to later problem when querying for registry data. --- snip --- 0032:Call KERNEL32.CreateProcessA(00000000,0015a5e8 "C:\\windows\\system32\\spool\\prtprocs\\w32x86\\printfilterpipelinesvc.exe /RegServer C:\\3b6becc6d220eb7bdd60153c\\update\\",00000000,00000000,00000000,00000000,00000000,00000000,0033ba98,0033badc) ... 003b:Call winspool.drv.OpenPrinterW(00000000,0033f8a0,00000000) ret=0102ed15 003b:trace:winspool:OpenPrinterW ((null), 0x33f8a0, (nil)) ... 003b:trace:winspool:OpenPrinterW returning 1 with 0 and 0x1 003b:Ret winspool.drv.OpenPrinterW() retval=00000001 ret=0102ed15 003b:Call winspool.drv.GetPrinterDataW(00000001,01004ad8 L"DefaultSpoolDirectory",00000000,00000000,00000000,0033f8a8) ret=0102ed82 003b:trace:winspool:GetPrinterDataExW (0x1, L"PrinterDriverData", L"DefaultSpoolDirectory" (nil), (nil), 00000000, 0x33f8a8) 003b:Ret winspool.drv.GetPrinterDataW() retval=00000006 ret=0102ed82 ... 003b:Call KERNEL32.GetLastError() ret=01021138 003b:Ret KERNEL32.GetLastError() retval=00000000 ret=01021138 ... 003b:Call KERNEL32.MultiByteToWideChar(00000000,00000008,0033f718 "Unexpected return value.",00000100,0033f518,00000100) ret=0105ec7c 003b:Ret KERNEL32.MultiByteToWideChar() retval=00000100 ret=0105ec7c ... 003b:Call KERNEL32.RaiseException(e06d7363,00000001,00000003,0033f810) ret=0101e688 003b:trace:seh:raise_exception code=e06d7363 flags=1 addr=0x7b84303a ip=7b84303a tid=003b 003b:trace:seh:raise_exception info[0]=19930520 003b:trace:seh:raise_exception info[1]=0033f83c 003b:trace:seh:raise_exception info[2]=01086754 003b:trace:seh:raise_exception eax=7b82cb69 ebx=7b8d091c ecx=00000000 edx=0033f7fc esi=0033f7fc edi=0033f770 003b:trace:seh:raise_exception ebp=0033f758 esp=0033f6f4 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00000246 ... 003b:Call KERNEL32.OutputDebugStringA(01002aec "Invalid parameter passed to C runtime function.\n") ret=01022579 003b:Ret KERNEL32.OutputDebugStringA() retval=ffffffff ret=01022579 --- snip --- 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 14

[Bug 50048] New: qmgr:job test has been failing on Windows 10 Pro for several weeks
by WineHQ Bugzilla 08 Jan '21

08 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=50048 Bug ID: 50048 Summary: qmgr:job test has been failing on Windows 10 Pro for several weeks Product: Wine-Testbot Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: aa1ronham(a)gmail.com Distribution: --- The 'qmgr:job' test has been failing on all of the Windows 10 VMs for the past several weeks. The most recent failure can be seen at https://test.winehq.org/data/e533a26dcff611f312e5bfce47061d2155476c42/ (for example, https://test.winehq.org/data/e533a26dcff611f312e5bfce47061d2155476c42/win10…) The failure message is always the same: Several tests which create background jobs get stuck in the BG_JOB_STATE_TRANSIENT_ERROR state (which is printed as state '5'). On https://test.winehq.org/data/, this pattern of failure appears to have started with https://test.winehq.org/data/432858b285d2b63eca6f99a162c9a13dd6e6ac71/ (Semptember 4th, https://source.winehq.org/git/wine.git/?a=shortlog;h=432858b285d2b63eca6f99…) Interestingly, the first failure always occurs in `test_CompleteLocal`. This tests transferring a local file using BITS - there's no network issue that could be causing a BG_JOB_STATE_TRANSIENT_ERROR. I've been unable to reproduce this failure locally, or on a Windows 10 Pro VM (created on Azure). I'm not familiar with how these VMS are set up, but my guess is that something went wrong with the BITS background service, which is causing `BG_JOB_STATE_TRANSIENT_ERROR` to be reported to the test program. -- 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 48354] New: Some patches may require forcing a wineprefix update
by WineHQ Bugzilla 08 Jan '21

08 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=48354 Bug ID: 48354 Summary: Some patches may require forcing a wineprefix update 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 updates the wineprefixes when it updates its base Wine source from the daily Wine commits. The rest of the time it lets Wine deal with updating the wineprefix is necessary. Furthermore Wine only updates the wineprefix when wine.inf changes, which is the case for every Wine release. The problem is that the wineprefix should also be updated when a patchset adds a WINE_REGISTRY resource to an existing dll. Failing to do so may cause the patchset tests to fail because the wineprefix is out of date. See: https://www.winehq.org/pipermail/wine-devel/2019-December/156914.html Wineprefix updates are relatively slow compared to the execution time of most tests (about 30s vs. < 1s) so it would be good not to have to do that for every task. An alternative would be to force a wineprefix update when a task has failures and gets rerun as a result (pass an option to the relevant VM-side scripts). -- 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 49939] New: Clive Barker's Jericho Demo claims not enough room on C: (NtMapViewOfSection returns STATUS_NOMEMORY)
by WineHQ Bugzilla 07 Jan '21

07 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=49939 Bug ID: 49939 Summary: Clive Barker's Jericho Demo claims not enough room on C: (NtMapViewOfSection returns STATUS_NOMEMORY) Product: Wine Version: 5.18 Hardware: x86-64 URL: https://www.gamepressure.com/download.asp?ID=17454 OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gijsvrm(a)gmail.com Blocks: 34747 Distribution: ArchLinux Created attachment 68320 --> https://bugs.winehq.org/attachment.cgi?id=68320 logs I wanted to retest bug 34747, but the demo won't install. The last test in that bug is from the 1.9 era and seems to imply that the demo used to install. I also checked on Windows 10 and it installs fine there. For multiple reasons bisecting this might be challenging. Attached is an archive containing +relay,+virtual logs from both vanilla wine and wine-staging (The ForceBottomUpAlloc patchset changes/adds tracing). I tried in both a 64bit and 32bit prefix, same result. Logs are from a 32bit 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 13

[Bug 45117] New: paf5.exe not working with wine 2.0 or 3.0 but works ok with wine 1.9
by wine-bugs＠winehq.org 07 Jan '21

07 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=45117 Bug ID: 45117 Summary: paf5.exe not working with wine 2.0 or 3.0 but works ok with wine 1.9 Product: Wine Version: 3.0-rc1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hollywood188(a)live.com Distribution: --- paf5.exe works with wine 1.9 but with 2.0 and 3.0 rectangular boxes are shown instead of charactors I am using Knoppix 8.1 linux which had wine 2.0 and I upgraded to wine 3.0 but same problem. it worked fine with Knoppix 7.7.1 and wine 1.9?? -- 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 8

[Bug 48903] New: App shutdowns
by WineHQ Bugzilla 07 Jan '21

07 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=48903 Bug ID: 48903 Summary: App shutdowns Product: Wine Version: 4.0.1 Hardware: Other OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: higuyhi1234(a)gmail.com Created attachment 66858 --> https://bugs.winehq.org/attachment.cgi?id=66858 ScreenShot (translated in description) Once I open the .exe file via wine, after a few seconds the app collapses with the following reason: Translation to pic that's attached: "The program encountered a serious error. It must shut down, we apologize for the inconvenience". -- 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 49793] New: untapped.gg tracker fails to start
by WineHQ Bugzilla 06 Jan '21

06 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=49793 Bug ID: 49793 Summary: untapped.gg tracker fails to start Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winehq_bugzilla(a)lxlz.space Distribution: --- Created attachment 68109 --> https://bugs.winehq.org/attachment.cgi?id=68109 log on 5.16-staging Possible regression. I did not investigate this throughly, but it works for me on 5.12 and does not work on 5.16-staging. Log is in attachment. -- 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 50000] New: wineconsole F8
by WineHQ Bugzilla 05 Jan '21

05 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=50000 Bug ID: 50000 Summary: wineconsole F8 Product: Wine Version: 5.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vladimir.kokovic(a)gmail.com Distribution: --- Created attachment 68408 --> https://bugs.winehq.org/attachment.cgi?id=68408 Exception backtrace Start wineconsole Type next cmds: ver dir echo %path% d & F8 --> Unhandled exception Unhandled exception: page fault on read access to 0x00000000 in 64-bit code (0x0000000000401cbe). Vladimir Koković, DP senior(70), Serbia, Belgrade, 13.October 2020 -- 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 38966] New: force close after hitting install usb drivers on lg mobile support tool and when enter cell carrier
by wine-bugs＠winehq.org 04 Jan '21

04 Jan '21

https://bugs.winehq.org/show_bug.cgi?id=38966 Bug ID: 38966 Summary: force close after hitting install usb drivers on lg mobile support tool and when enter cell carrier Product: Wine Version: 1.7.37 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: catsetname(a)yahoo.com Created attachment 51910 --> https://bugs.winehq.org/attachment.cgi?id=51910 backtrace.txt after loading lg mobile support tool i hit install usb drivers, list of cell carriers pop to select once selected box comes up stating program needs to close and options to close or show details -- 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 27502] New: app freezes when WM_KILLFOCUS creates modal dialog
by wine-bugs＠winehq.org 03 Jan '21

03 Jan '21

http://bugs.winehq.org/show_bug.cgi?id=27502 Summary: app freezes when WM_KILLFOCUS creates modal dialog Product: Wine Version: unspecified Platform: All OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: efrias(a)syncad.com Created an attachment (id=35159) --> (http://bugs.winehq.org/attachment.cgi?id=35159) simple example which produces the error When a program brings up a modal dialog box in response to a WM_KILLFOCUS message, the program will freeze. I've attached a simple test case, all boilerplate except for: case WM_KILLFOCUS: MessageBox(hWnd, _T("Killing Focus"), _T("Note"), MB_OK); in the main event loop. If you run the program and then give focus to another application, the messagebox will pop up and then the program will become unresponsive. What is happening is: - x11drv gets a FocusOut event and calls the event handler, which ends up SendMessage-ing a WM_KILLFOCUS to the program. - The programs's code creates a modal dialog like the MessageBox above, and enters the dialog's event loop, which winds up calling GetMessage which calls MsgWaitForMultipleObjectsEx to get more X11 events. - X11DRV_MsgWaitForMultipleObjectsEx executes this: if (data->current_event) mask = 0; /* don't process nested events */ where data->current_event is true since we're still handling the FocusOut event. Since we're not processing nested events, we'll never be able to process the usual events like keys or mouse events which could exit this nested event loop. This type of error occurs in a few places in our application, where a WM_KILLFOCUS message to an edit box triggers some input validation and displays an error on failure. This works correctly in the normal case, where the user tabs out or clicks on another control in the dialog box containing the edit control -- since everything stays in the same top-level window, there is no FocusOut event from X11 and the WM_KILLFOCUS is generated internally by wine in response to, say, a KeyEvent. I think these key or mouse events are just posted to the windows message queue, and the X11 event handler has already exited by the time the application gets around to processing the ensuing WM_KILLFOCUS. But in the case where focus is lost by clicking outside the dialog containing the edit control, the WM_KILLFOCUS is generated by the FocusOut handler which is still executing, and we lock up. I suspect this is related to bug 11595 "Notepad++ freezes if native application changes a file it has open (dogfood)". My guess is in that case, a FocusIn event triggers something like a WM_ACTIVATE, in which notepad++ notices a file is changed and displays a messagebox asking if you want to reload. Since wine is still processing the FocusIn event, the modal message loop's call to MsgWaitForMultipleObjectsEx will never process any useful events because it's a nested event. Our application's built-in text editor has this same problem. I don't understand the event handling code well enough to propose a solution. As a test, I allowed nested event processing and it solved the problem without introducing any obvious errors, but I'm sure that check was in there for a reason. It's probably better to keep the application code from being executed from inside the event handler, if that's possible. Note: this bug was also posted as a message to wine-devel here: http://www.winehq.org/pipermail/wine-devel/2011-June/090652.html -- 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 14

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