wine-bugs October 2020

wine-bugs@winehq.org

1 participants
6815 discussions

[Bug 50062] New: Fallout 76 invisible ground textures
by WineHQ Bugzilla 29 Apr '21

29 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=50062 Bug ID: 50062 Summary: Fallout 76 invisible ground textures Product: Wine Version: 5.20 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: o.dierick(a)piezo-forte.be Distribution: --- Created attachment 68518 --> https://bugs.winehq.org/attachment.cgi?id=68518 Screenshot of missing ground textures; wine 5.20 Hello, Fallout 76 has invisible ground textures. See attached screenshot. My setup is: - Debian 8 amd64 16Gb RAM i7-4930 @ 3.4Ghz; - NVidia RTX 2070 8GB VRAM + proprietary driver 450.66; - wine 5.20; - winetricks corefonts xact_x64; - virtual desktop + no WM management/decoration + grab fullscreen; To replicate, install the game (Bethesda.net or Steam windows version), then you have to use an existing character or create a character and get out of the first building. That building has no natural floor and the issue only affects the ground texture, so it's not enough to just start a new game. Note that the game is affected by a bug that makes the game crash when loading a save immediately after launching the program. You have to start a new character first. When character creation is complete, you may return to the main menu and load the save. This is an application bug [1]. Some graphics settings must be disabled in the INI file to avoid major mouse and rendering issues. The details can be found on the lutris website [2]. [1] https://www.reddit.com/r/fo76/comments/a3446i/game_crashes_after_trying_to_… [2] https://lutris.net/games/fallout-76/ The ground is transparent. The game renders the objects behind mountains and the performance is directly affected by the rendering distance set in the option. - Using Ultra or lowest graphic settings makes no difference; - I tried changing some values in the INI file without luck; - The issue occurs with wine-staging 5.20 too. 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.

1 2

[Bug 27117] New: Quake III Arena demo installer spawns Wine File when setting up Start menu items
by wine-bugs＠winehq.org 29 Apr '21

29 Apr '21

http://bugs.winehq.org/show_bug.cgi?id=27117 Summary: Quake III Arena demo installer spawns Wine File when setting up Start menu items Product: Wine Version: 1.3.19 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: tjwt(a)hush.ai The demo is downloadable from ftp://ftp.idsoftware.com/idstuff/quake3/win32/Q3ADemo.exe . During a default installation in Wine, it creates ten files in C:\users\Public\Start Menu\ and ten Wine File windows appear. No Windows Explorer windows open when installing under Windows XP. I see the problem with Wine 1.3.18 and 1.3.19 (I did not try earlier versions). -- 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 8

[Bug 45864] New: wine mono cannot load 64-bit DLLs
by wine-bugs＠winehq.org 29 Apr '21

29 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=45864 Bug ID: 45864 Summary: wine mono cannot load 64-bit DLLs Product: Wine Version: 3.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mscoree Assignee: wine-bugs(a)winehq.org Reporter: paleozogt(a)gmail.com Distribution: --- Created attachment 62358 --> https://bugs.winehq.org/attachment.cgi?id=62358 wine mono project and binaries Attached is an example project that makes a PInvoke call to a custom native function. It produces HelloWorld.exe (from HelloWorld.cs) and HelloWorld.dll (from HelloworldNative.cpp). If I build a 32-bit HelloWorld.dll, I am able to run HelloWorld.exe in Wine with a WINEPREFIX generated from both WINEARCH=wine32 and WINEARCH=wine64. However, if I build a 64-bit HelloWorld.dll, I am unable to run HelloWorld.exe in Wine with a WINEPREFIX generated from either WINEARCH=wine32 or WINEARCH=wine64. I wouldn't expect WINEARCH=wine32 to work for a 64-bit DLL, but its surprising that WINEARCH=wine64 doesn't work. (With WINEARCH=wine64 I'm otherwise able to run 64-bit native executables without a problem.) The failure looks like this: > >HelloWorld.exe > 002f:err:mscoree:LoadLibraryShim error reading registry key for installroot > > Unhandled Exception: > System.DllNotFoundException: HelloWorld > at (wrapper managed-to-native) HelloWorld.Hello:helloWorld () > at HelloWorld.Hello.Main () [0x00001] in <93c08d3d3d384696aa77bc80f6a731c1>:0 > [ERROR] FATAL UNHANDLED EXCEPTION: System.DllNotFoundException: HelloWorld > at (wrapper managed-to-native) HelloWorld.Hello:helloWorld () > at HelloWorld.Hello.Main () [0x00001] in <93c08d3d3d384696aa77bc80f6a731c1>:0 It seems like Wine Mono is either running as a 32-bit process or something is wrong with how Wine Mono's PInvoke DllImport searches for compatible DLLs. -- 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 42563] New: regedit: minor enhancements/ corrections to REG_BINARY edit dialog
by wine-bugs＠winehq.org 28 Apr '21

28 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=42563 Bug ID: 42563 Summary: regedit: minor enhancements/corrections to REG_BINARY edit dialog Product: Wine Version: 2.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: galtgendo(a)o2.pl Distribution: --- Created attachment 57477 --> https://bugs.winehq.org/attachment.cgi?id=57477 patch implementing the changes OK, it took me awhile. As I've written a few weeks ago, due to the display part being unscrollable/unresizable, long values may sometimes not fit into their allocated display space. Also, monospace makes simply much more sense here. The attached patch modifies the default font to monospace variant and tries to enforce it by using ExtTextOutW. A possible further enhancement would be to use the proper value for max 0-9A-F width in address block, instead of the same as in the content block. -- 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 17

[Bug 45587] New: wine fails to install dragon naturally speaking 15
by wine-bugs＠winehq.org 28 Apr '21

28 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=45587 Bug ID: 45587 Summary: wine fails to install dragon naturally speaking 15 Product: Wine Version: 3.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: susancragin(a)earthlink.net Distribution: --- Created attachment 62012 --> https://bugs.winehq.org/attachment.cgi?id=62012 backtrace from failed install Dragon Naturally Speaking 15 does not install. Here's what I do. Start with a 32bit wine prefix. Install dotnet40 When that is finished, set the program version to Windows 7, which is the lowest configuration that will run NatSpeak 15. The program starts out by requesting dotnet 452. This is not a problem provided dotnet 40 is installed. It makes changes and goes on. Then it asks for preliminary information, such as what type of English I want to speak, and so on. Then the installation hangs. Notes: the installation does not work with mono. It also does not work installing dotnet from the installation disk, even though a complete copy is included with the installation disk. And it doesn't work installing dotnet452 with winetricks. I have the feeling that this may not be a bug as much as an issue that hasn't been addressed yet. These are the last lines of the terminal output, and I have attached the dump. 0270:fixme:advapi:DeregisterEventSource (0xcafe4242) stub Unhandled Exception: 0270:fixme:ver:GetCurrentPackageId (0x33b890 (nil)): stub 0270:fixme:ntdll:EtwEventRegister ({8e9f5090-2d75-4d03-8a81-e5afbf85daf1}, 0x33804b6, (nil), 0x10e6844) stub. System.IO.FileNotFoundException: Could not load file or assembly 'System.Management.Automation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. File not found. at customactions.Program.ChangeAppStartingCursor() at customactions.Program.Main(String[] args) wine: Unhandled exception 0xe0434352 in thread 270 at address 0x7b43c7dc (thread 0270), starting debugger... 02e5:err:ntdll:RtlpWaitForCriticalSection section 0x7bd176e0 "virtual.c: csVirtual" wait timed out in thread 02e5, blocked by 02f1, retrying (60 sec) -- 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 47685] New: winecfg: audio test fails with error on cmd line
by wine-bugs＠winehq.org 28 Apr '21

28 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=47685 Bug ID: 47685 Summary: winecfg: audio test fails with error on cmd line Product: Wine Version: 1.6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: normt40pa(a)yahoo.com Distribution: --- When using winecfg and then clicking tab audio, Evering seems good here until I use the test audio button. I don't compile software ie to copile the new version of wine. I use what is available on ubuntu.... The problem arises when I click test audio giving me on the command line error "err:ole:CoInitializeEx Attempt to change threading model of this apartment from multi-threaded to apartment threaded" only. No other info after this since I have looked in the forum for similar errors and none math the solo line as described above (usually combine with a specific error type after this line. Please advise... -- 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 43489] New: Bug on Hi suite that provoc the no connection of the smartphone
by wine-bugs＠winehq.org 27 Apr '21

27 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=43489 Bug ID: 43489 Summary: Bug on Hi suite that provoc the no connection of the smartphone 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: shikaruko-ryukan(a)legtux.org Distribution: --- Created attachment 58871 --> https://bugs.winehq.org/attachment.cgi?id=58871 Bug at launch of Hi suite on Wine 1.6.2 Bug on Hi suite that provoc the no connection of the smartphone -- 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 24624] New: Audacity 1.3.12 treats all file type selections as "all files" when exporting
by wine-bugs＠winehq.org 27 Apr '21

27 Apr '21

http://bugs.winehq.org/show_bug.cgi?id=24624 Summary: Audacity 1.3.12 treats all file type selections as "all files" when exporting Product: Wine Version: 1.3.4 Platform: x86-64 URL: http://audacity.sourceforge.net/ OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: RandomAccountName(a)mail.com Created an attachment (id=31111) --> (http://bugs.winehq.org/attachment.cgi?id=31111) Terminal output In Audacity, open an audio file and then go to file -> export. On this file dialog, any selection from the "files of type" drop-down list will (apparently) be treated as "all files", which leads to two minor annoyances: 1. DLLs and other unrelated file types will be listed while browsing for a destination folder. (This doesn't happen immediately when the dialog opens, only after changing the destination directory and/or file type.) 2. If the file extension isn't specified manually, Audacity will try to append ".*" to the end of the file name and then warn that this is a non-standard extension for this type of file. -- 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 10

[Bug 49138] New: winegcc: argc and argv arguments of main() get corrupted
by WineHQ Bugzilla 26 Apr '21

26 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=49138 Bug ID: 49138 Summary: winegcc: argc and argv arguments of main() get corrupted Product: Wine Version: 5.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: mail(a)robbertvanderhelm.nl Distribution: --- I first came across this issue with winelib compilation in Wine 5.7 while I was working on yabridge, a Wine VST bridge. The issue still persists on the latest commit in the Wine repository as I'm writing this (commit bf1abba, with the release of Wine 5.8). I'm not exactly sure what is going on, but the issue can be reproduced as follows: #include <iostream> int main(int argc, char* argv[]) { std::cout << "argc = " << argc << std::endl; std::cout << "argv[0] = " << argv[0] << std::endl; } If you compile the above (or the C-equivalent) with `wineg++ test.cpp -o test` and run test.exe, then at least on my system it will always print 70624 as the value of argc and some uninitialized looking data for argv[0]. This happens regardless of whether the program receives any command line arguments or not. Winelib applications compiled with the toolchain that comes with Wine 5.6 can be run without problems under Wine 5.7 or 5.8. The winelib compilation issue with Wine 5.7+ exists on Ubuntu 18.04, Ubuntu 20.04, Arch Linux and Manjaro, both when using the distro provided packages and when building Wine from source. -- 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 48449] New: 'CreateProcess(0, "cmd /C [...]' fails when a trailing newline follows a redirect in the cmdline
by WineHQ Bugzilla 24 Apr '21

24 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=48449 Bug ID: 48449 Summary: 'CreateProcess(0, "cmd /C [...]' fails when a trailing newline follows a redirect in the cmdline Product: Wine Version: 5.0-rc5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: timotheecisnard(a)gmail.com Distribution: --- Applications using CreateProcess to invoke "cmd.exe /C" followed by a command, a redirect to a file, and a newline, result in an "Invalid name" error and the command not being run. The expected result on Windows is for the trailing newline to be silently ignored and not treated as part of the file name being redirected into. For example, the CreateProcess cmdline "cmd.exe /C echo OK >> test.log\n" contains a (completely pointless) trailing newline. Note that the newline is a literal trailing 0x0A character in a cmdline and NOT an interactive user pressing Enter at a command prompt. This issue is best reproduced with a 10 line C program: https://paste.debian.net/1125644/ The bug originally affects ALDEC Active-HDL Lattice Edition 32bit version 10.5.216.6767, where compiling a project works but starting a simulation fails at the linking step with cryptic errors like "Generation phase ... fail" and "Error: E8005 : Kernel process initialization failed.". -- 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

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