wine-bugs March 2021

wine-bugs@winehq.org

1 participants
6208 discussions

[Bug 49583] New: Assassin's Creed Odyssey displays black bars on top and bottom.
by WineHQ Bugzilla 26 May '21

26 May '21

https://bugs.winehq.org/show_bug.cgi?id=49583 Bug ID: 49583 Summary: Assassin's Creed Odyssey displays black bars on top and bottom. Product: Wine Version: 5.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: GloriousEggroll(a)gmail.com Distribution: --- Created attachment 67739 --> https://bugs.winehq.org/attachment.cgi?id=67739 AC Odyssey black bar fix It's been a long known issue that AC: Odyssey renders with black bars on the top and bottom of the screen (see screenshot 1). Derek Lesho came up with a stub patch that both fixed this -and- allowed STEEP to run (it would not display previously). That patch can be found here: https://github.com/GloriousEggroll/proton-ge-custom/blob/5.12-GE-1/patches/… Recently, the relevant function QueryDisplayConfig was implemented, however it did not contain some of the changes Derek's patch adds. This allowed steep to work, however AC: Odyssey still retained the black bar issue. I modified Derek's patch by adding the relevant parts to QueryDisplayConfig, and removing the relevant flag checks (Derek's patch did this previously), and this allowed AC: Odyssey to render properly without the black bars. (see screenshot 2). The patch is hacky but may provide more information towards fixing this properly. -- 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 8

[Bug 49748] New: Multisim 14.2 installer fails with "Directory name invalid"
by WineHQ Bugzilla 25 May '21

25 May '21

https://bugs.winehq.org/show_bug.cgi?id=49748 Bug ID: 49748 Summary: Multisim 14.2 installer fails with "Directory name invalid" Product: Wine Version: 5.15 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- When running the installer, it terminates with a MessageBox showing "Directory name invalid". -- 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 8

[Bug 49788] New: mountmgr is no longer detecting SCSI devices
by WineHQ Bugzilla 25 May '21

25 May '21

https://bugs.winehq.org/show_bug.cgi?id=49788 Bug ID: 49788 Summary: mountmgr is no longer detecting SCSI devices Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mountmgr.sys Assignee: wine-bugs(a)winehq.org Reporter: winebugzilla(a)tasossah.com Regression SHA1: 19549d11a72f63efe0d689374446a56a68264a1f Distribution: --- Created attachment 68104 --> https://bugs.winehq.org/attachment.cgi?id=68104 regedit screenshot Commit 19549d11a72f63efe0d689374446a56a68264a1f switched to using udisks2 to detect devices, however this no longer detects SCSI devices. This results in ASPI_GetNumControllers always returning 0, and ASPI applications not detecting any optical drives. Compiling wine one commit before the one mentioned above (8388ea840fedbb9b646213a26cd59ceb3a48680b) restores the ability to detect and use SCSI devices. Tested on two different Ubuntu 20.04 installations, both with fully functional udisks2. Steps to reproduce: Start up wine regedit Navigate to HKLM\Hardware\DEVICEMAP\Scsi Observe that it is empty When functioning correctly, it should report all SCSI devices, including hard disks and optical drives. In general, all devices that exist in /proc/scsi/scsi should show up in the registry. https://bugs.winehq.org/show_bug.cgi?id=31592 was opened presumably to move away from /proc/scsi, however it is now a regression. -- 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 49825] New: GetNamedSecurityInfoA with LABEL_SECURITY_INFORMATION returns ERROR_ACCESS_DENIED
by WineHQ Bugzilla 25 May '21

25 May '21

https://bugs.winehq.org/show_bug.cgi?id=49825 Bug ID: 49825 Summary: GetNamedSecurityInfoA with LABEL_SECURITY_INFORMATION returns ERROR_ACCESS_DENIED Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: vladimir.kokovic(a)gmail.com Distribution: --- Created attachment 68159 --> https://bugs.winehq.org/attachment.cgi?id=68159 wine log file Hi, I don't understand at all what this is all about even though I have a complete WINEDEBUG log, when it comes to GetNamedSecurityInfoA with LABEL_SECURITY_INFORMATION where ERROR_ACCESS_DENIED returns. Although at first glance everything is normal, it is obvious that I do not know enough wine and that is why I need help to resolve this situation and if possible remove this bug for the sake of others and not just me. Attached are 2 files: 1. TestGetNamedSecurityInfoA.cpp - test program 2. WINEDEBUG.log - part of a very large log file -- 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 50002] New: BlackBerry (Research in Motion) USB and Modem Drivers installs files in the wrong place and fails to install kernel drivers
by WineHQ Bugzilla 25 May '21

25 May '21

https://bugs.winehq.org/show_bug.cgi?id=50002 Bug ID: 50002 Summary: BlackBerry (Research in Motion) USB and Modem Drivers installs files in the wrong place and fails to install kernel drivers Product: Wine Version: 5.19 Hardware: x86-64 URL: https://swdownloads.blackberry.com/Downloads/contactFo rmPreload.do?code=A8BAA56554F96369AB93E4F3BB068C22&dl= F5937D3FABCEC4C05D26AB6F3FEEC891 OS: Linux Status: NEW Keywords: download, Installer Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: z.figura12(a)gmail.com Distribution: --- Created attachment 68409 --> https://bugs.winehq.org/attachment.cgi?id=68409 hack: set CommonFiles64Folder to the 32-bit common files dir The installer is more than a bit of a mess. It seems to be trying to install 64-bit files into the 64-bit "Common Files" folder, and 32-bit files into the 32-bit folder. It has this <trimmed> in its Directory table: Directory Directory_Parent DefaultDir ---------------------------------------------------------- TARGETDIR SourceDir RESEARCH_IN_MOTION ProgramFilesFolder RESEAR~1|Research In Motion BLACKBERRY RESEARCH_IN_MOTION BLACKB~1|BlackBerry INSTALLDIR BLACKBERRY . CommonFiles64Folder TARGETDIR .:Common64 CommonFilesFolder TARGETDIR .:Common CommonFilesRIM.191... CommonFilesFolder RESEAR~1|Research In Motion CommonFilesRIM.07D... CommonFiles64Folder RESEAR~1|Research In Motion On Wine this behaves essentially as expected, and files get installed into 64-bit "Common Files". On Windows, however, for some reason, everything gets installed into the 32-bit "Common Files" directory. This problem is compounded when the program subsequently tries to install PnP drivers (from a 64-bit custom action) using files from the 32-bit "Common Files" folder—working around their own bug, I guess—and on Wine nothing gets installed. I'm more than a little baffled as to how this could possibly break on Windows. It'll probably take some more involved debugging. Anyway, the attached patch works around the bug. The installer successfully creates a couple of root PnP devices, but the driver subsequently fails to load due to missing WDF. (In fact it needs quite a substantial chunk of WDF, which I have partially implemented in my local tree). -- 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 50299] New: Application tried to create a window, but no driver could be loaded.
by WineHQ Bugzilla 25 May '21

25 May '21

https://bugs.winehq.org/show_bug.cgi?id=50299 Bug ID: 50299 Summary: Application tried to create a window, but no driver could be loaded. Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bernhardu(a)mailbox.org Distribution: --- 0050:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. Running e.g. "wine notepad" in a quite slow environment for example within rr-debugger inside a VM leads to the above message. As far as I could follow in above line 0050 is "explorer.exe". Unfotunately winemenubuilder.exe was a little bit earlier with requesting the first window in WIN_CreateWindowEx before explorer.exe reached manage_desktop. Therefore explorer.exe never SetPropW("__wine_display_device_guid") in DesktopWndProc. This race might not show up under normal conditions, but I thought to document it here to be findable. Making winemenubuilder.exe sleep some time in wWinMain before CoInitialize works around it. -- 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 50606] New: Far Manager does not resize when tty console is resized
by WineHQ Bugzilla 25 May '21

25 May '21

https://bugs.winehq.org/show_bug.cgi?id=50606 Bug ID: 50606 Summary: Far Manager does not resize when tty console is resized Product: Wine Version: 6.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: rpisl(a)seznam.cz Distribution: --- Created attachment 69291 --> https://bugs.winehq.org/attachment.cgi?id=69291 Quick fix Far Manager does not resize when tty console is resized. The tty size is only read upon start and remains fixed. Attaching a hack that fixes it for me. Let me know if there is a way how to do it properly and acceptable for upstream. -- 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 50109] New: 0414:fixme:conhost:write_console beep
by WineHQ Bugzilla 25 May '21

25 May '21

https://bugs.winehq.org/show_bug.cgi?id=50109 Bug ID: 50109 Summary: 0414:fixme:conhost:write_console beep Product: Wine Version: 5.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: azraeladdy(a)gmail.com Distribution: --- Created attachment 68600 --> https://bugs.winehq.org/attachment.cgi?id=68600 Output from a simple C program. Along with its code. Occurs when outputting the BEL ASCII character. Nothing huge, but a worthy thing to keep track of? Not much else to say, possibly other ASCII characters that wine has a fix me statement for? -- 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 50187] New: programs/conhost/window.c:2310 - Unhandled exception: divide by zero in 64-bit code
by WineHQ Bugzilla 25 May '21

25 May '21

https://bugs.winehq.org/show_bug.cgi?id=50187 Bug ID: 50187 Summary: programs/conhost/window.c:2310 - Unhandled exception: divide by zero in 64-bit code Product: Wine Version: unspecified 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 68703 --> https://bugs.winehq.org/attachment.cgi?id=68703 backtrace.log When my console application starts, wine reports an exception for which I don't see any real reason. Attached is the backtrace.log of the moment this exception occurs. -- 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 40099] New: IFileOpenDialog with FOS_PICKFOLDERS option
by wine-bugs＠winehq.org 24 May '21

24 May '21

https://bugs.winehq.org/show_bug.cgi?id=40099 Bug ID: 40099 Summary: IFileOpenDialog with FOS_PICKFOLDERS option Product: Wine Version: 1.9.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nozomimasao(a)gmail.com Distribution: --- IFileOpenDialog sometimes returns a bad path if FOS_PICKFOLDERS option is specified. for example, if you selected C:\Windows folder *inside* Windows folder, GetResult method returns C:\Windows\Windows. Steps of the user: 1. Go inside C:\Windows by double-clicking Windows folder. 2. Click select button. Then the path will be C:\Windows\Windows. *The user can avoid this issue by below steps. 1. Select C:\Windows by clicking Windows folder *without* going inside it. 2. Click select button. Then the path will be C:\Windows. For your information, the code is like this; IFileOpenDialog *fo = nullptr; CoCreateInstance(CLSID_FileOpenDialog, NULL, CLSCTX_INPROC_SERVER, IID_PPV_ARGS(&fo)); DWORD opt = 0; fo->GetOptions(&opt); fo->SetOptions(opt | FOS_PICKFOLDERS); fo->Show(hWnd); IShellItem *si = nullptr; fo->GetResult(&si); LPWSTR path = nullptr; si->GetDisplayName(SIGDN_FILESYSPATH, &path); -- 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

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 March 2021