March 2020 - Wine-Bugs - list.winehq.org

[Bug 45400] eden* (VN) some font characters display with the wrong glyph (capitals/spaces)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=45400 --- Comment #5 from Aexander <kq3thih(a)mailnesia.com> --- (In reply to Nikolay Sivov from comment #4) > > P.S. could someone verify if bug occurs for current wine 5.x builds Still occurs with 5.3 and the GOG version. -- 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.

March 2, 2020

[Bug 48693] New: Startup Wine and got: "Segmentation fault: 11"

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=48693 Bug ID: 48693 Summary: Startup Wine and got: "Segmentation fault: 11" Product: Wine-staging Version: 5.3 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: avenjames(a)live.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Updated Wine Staging from 5.2.2 to 5.3 with PKG in Mac OSX 10.13 High Sierra, input "Winecfg" or any others command via Terminal, got: 0009:fixme:esync:do_esync eventfd not supported on this platform. Segmentation fault: 11 startup 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.

March 2, 2020

[Bug 48172] 32-bit wine is unable to allocate a continuous 1.5GB block of memory under 64-bit Linux with a lot of RAM

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=48172 --- Comment #5 from Artem S. Tashkinov <aros(a)gmx.com> --- (In reply to Stefan Dösinger from comment #4) > A 32 bit process has only 4GB of available address space no matter how much > physical RAM you have. Even if you have less than that a process can > theoretically alloc 4 GB, it might just lead to heavy swapping. My PC currently has 64GB of RAM with usually over 60GB free. > If you want 1.5 gb continuous memory it is vital that the free space is not > fragmented. Windows (and thus wine) have a fixed allocation around 2gb at > 0x7ffe0000 (KSHARED_USER_DATA), so you won't be able to get an allocation > > 2GB no matter what. The area below 2 GB is sprinkled with Windows DLLs at > fixed load addresses. The area above 2 GB will likely have a pile of Linux > libs loaded. Address space layout randomization (a security feature) is > likely to sprinkle libs everywhere. > > /proc/<pid>/maps shows you what is loaded where. I guess disable ASLR will > help, at the cost of making your system more vulnerable to buffer overflow > attacks. On 32 bit Windows ASLR is somewhat limited because many windows > libs have a hardcoded load address and applications depend on it. Is it the same for 32bit and 64bit host OS'es? I'm running a 64bit Linux distro, so seemingly there should be no troubles with 32bit memory allocations. I'd prefer to leave all default protections in place. -- 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.

March 1, 2020

[Bug 48677] Exact Audio Copy (EAC) 1.4 plugins don't function with Wine-Mono

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=48677 --- Comment #4 from bastian.dev(a)gmail.com --- Sorry Anastasius Focht for not specifiying the plugin issues more precisely. You can check whether the plugins work or not by goint to the Menu EAC->EAC Options->Audio Plugins. There should be AcoustID Plugin and CUETools DB Plugin. Under Menu EAC->Metadata Options there should be more than the "Build-in freedb engine": "CueTools...", "MusicBrainz..." and "GD3...". To make them work I had to install dotnet20 and dotnet40 via winetricks. -- 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.

March 1, 2020

[Bug 48172] 32-bit wine is unable to allocate a continuous 1.5GB block of memory under 64-bit Linux with a lot of RAM

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=48172 Stefan Dösinger <stefan(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stefan(a)codeweavers.com --- Comment #4 from Stefan Dösinger <stefan(a)codeweavers.com> --- A 32 bit process has only 4GB of available address space no matter how much physical RAM you have. Even if you have less than that a process can theoretically alloc 4 GB, it might just lead to heavy swapping. If you want 1.5 gb continuous memory it is vital that the free space is not fragmented. Windows (and thus wine) have a fixed allocation around 2gb at 0x7ffe0000 (KSHARED_USER_DATA), so you won't be able to get an allocation > 2GB no matter what. The area below 2 GB is sprinkled with Windows DLLs at fixed load addresses. The area above 2 GB will likely have a pile of Linux libs loaded. Address space layout randomization (a security feature) is likely to sprinkle libs everywhere. /proc/<pid>/maps shows you what is loaded where. I guess disable ASLR will help, at the cost of making your system more vulnerable to buffer overflow attacks. On 32 bit Windows ASLR is somewhat limited because many windows libs have a hardcoded load address and applications depend on 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.

March 1, 2020

[Bug 40430] Multiple NVIDIA installers abort due to failure to process xml config (PhysX 9.x, GeForce Now, GeForce Experience 3.x)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=40430 --- Comment #10 from Anastasius Focht <focht(a)gmx.net> --- *** Bug 45799 has been marked as a duplicate of this bug. *** -- 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.

March 1, 2020

[Bug 45799] NVIDIA GeForce Experience 3.x installer fails to process xml config 'MSVCRuntime_2017.NVX'

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=45799 --- Comment #4 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, resolving as dupe of bug 40430 Regards *** This bug has been marked as a duplicate of bug 40430 *** -- 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.

March 1, 2020

[Bug 45796] Nvidia GeForce Now installer aborts due to missing 'advapi32.RegQueryReflectionKey' export

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=45796 Bug 45796 depends on bug 45795, which changed state. Bug 45795 Summary: Nvidia GeForce Now installer aborts due to failure to process xml config https://bugs.winehq.org/show_bug.cgi?id=45795 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- 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.

March 1, 2020

[Bug 45795] Nvidia GeForce Now installer aborts due to failure to process xml config

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=45795 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, resolving as dupe of bug 40430 Regards *** This bug has been marked as a duplicate of bug 40430 *** -- 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.

March 1, 2020

[Bug 40430] Multiple NVIDIA installers abort due to failure to process xml config (PhysX 9.x, GeForce Now, GeForce Experience 3.x)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=40430 --- Comment #9 from Anastasius Focht <focht(a)gmx.net> --- *** Bug 45795 has been marked as a duplicate of this bug. *** -- 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.

March 1, 2020