wine-bugs August 2021

wine-bugs@winehq.org

1 participants
5023 discussions

[Bug 51585] New: Couldn't start debugger L"winedbg --auto 96 64" (1115)
by WineHQ Bugzilla 08 Sep '21

08 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51585 Bug ID: 51585 Summary: Couldn't start debugger L"winedbg --auto 96 64" (1115) Product: Wine Version: 6.14 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: --- Konsole log: ... /root/files/spider.sh & 0024:fixme:htmlhelp:HtmlHelpW HH case HH_INITIALIZE not handled. 0024:fixme:htmlhelp:HtmlHelpW HH_PRETRANSLATEMESSAGE unimplemented wine: Unhandled page fault on write access to 0000000000000000 at address 00007F92D42369BB (thread 0070), starting debugger... 0070:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 96 64" (1115) Read the Wine Developers Guide on how to set up winedbg or another debugger ... wine --version wine-6.14 Vladimir Koković, DP senior(70), Serbia, Belgrade, 10.August 2021 -- 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 51527] New: Seeing and error message after upgrading to 6.13
by WineHQ Bugzilla 08 Sep '21

08 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51527 Bug ID: 51527 Summary: Seeing and error message after upgrading to 6.13 Product: Wine Version: 6.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mikes(a)guam.net Distribution: --- Just did dnf update and it installed wine 6.13. Afterwards I generally run wine notepad from command line to have it do the test of update. This time, it did the update fine, and comes up with the blank screen and I closed the notepad. After a short time, the following comes up on terminal window. wine: Unhandled page fault on write access to 0000000000000000 at address 00007F56D62BE3A1 (thread 0074), starting debugger... 0074:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 100 72" (1115) Read the Wine Developers Guide on how to set up winedbg or another debugger Not sure why it can't start debugger. I can run wine winedbg --auto 100 72 afterwards, but it shows info, but doesn't apply to the previous notepad run. If I run notepad from the menu, you would never see this message at all, so not sure if it is just something to ignore. Thanks. -- 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 50986] New: Rufus does not detect USBs because Wine recognizes mounted pendrives as hard disks
by WineHQ Bugzilla 08 Sep '21

08 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=50986 Bug ID: 50986 Summary: Rufus does not detect USBs because Wine recognizes mounted pendrives as hard disks Product: Wine Version: 6.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: setupapi Assignee: wine-bugs(a)winehq.org Reporter: riky.8(a)outlook.it Distribution: --- Created attachment 69821 --> https://bugs.winehq.org/attachment.cgi?id=69821 The complete Rufus log generated by WineHQ 6.0 stable On Windows the usb are seen correctly by Rufus and going into the driver information I saw that the usb made use of the USBSTOR.SYS and usbstor.inf driver, not present on WineHQ: 0024:fixme:setupapi:CM_Get_Device_ID_List_SizeA 0093EA30 "USBSTOR" 0x00000102: stub My request is to add support for usb mass storage (USBSTOR). The complete Rufus log generated by WineHQ 6.0 stable is attached. The problem persists even on WineHQ 6.6 develop and staging. Unfortunately the setupapi bugfixes did not include this enhancement. -- 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 49795] New: widl dislikes restricted attribute somewhen
by WineHQ Bugzilla 08 Sep '21

08 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=49795 Bug ID: 49795 Summary: widl dislikes restricted attribute somewhen Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: tools Assignee: wine-bugs(a)winehq.org Reporter: kolan_n(a)mail.ru Distribution: --- When compiling SAPI IDL files I have encountered an error, that the attr is 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 5

[Bug 47903] New: Add a NetBSD test VM
by WineHQ Bugzilla 07 Sep '21

07 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=47903 Bug ID: 47903 Summary: Add a NetBSD test VM Product: Wine-Testbot Version: unspecified Hardware: x86 OS: NetBSD Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com A GSoC 2019 student worked on improving Wine support on NetBSD: https://www.phoronix.com/scan.php?page=news_item&px=Wine-NetBSD-GSoC-2019-D… In order to keep Wine in good shape on NetBSD the TestBot should have a NetBSD Wine VM. Currently this is blocked on: 1. A wininet patch: https://www.winehq.org/pipermail/wine-devel/2019-October/151827.html -> Once fixed setting a NetBSD build-only VM should be possible. 2. Setting up a NetBSD with an auto-login X session. -> This will allow the TestBot to automatically recreate the live snapshot when needed. 3. Some RPATH issues that break Wine's WoW support. https://www.winehq.org/pipermail/wine-devel/2019-September/150284.html -- 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 48649] New: Guild Wars 2 / TaCo : unable to start overlay, get only black screen
by WineHQ Bugzilla 04 Sep '21

04 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=48649 Bug ID: 48649 Summary: Guild Wars 2 / TaCo : unable to start overlay, get only black screen Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: aeris+winehq(a)imirhil.fr Distribution: --- It's currently not possible to run an overlay like TaCo (http://www.gw2taco.com/) over the running game. TaCo starts and works be we got a black screen everywhere, instead of a transparent background. See render here: https://www.gamingonlinux.com/forum/topic/3966 Trouble reported here to: https://github.com/doitsujin/dxvk/issues/1225 -- 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 51711] New: Regression in ARM 32-bit compile, does not find unwind functions
by WineHQ Bugzilla 04 Sep '21

04 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51711 Bug ID: 51711 Summary: Regression in ARM 32-bit compile, does not find unwind functions Product: Wine Version: 6.16 Hardware: arm OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: loader Assignee: wine-bugs(a)winehq.org Reporter: mike(a)cchtml.com Distribution: --- Trying to compile wine (NOT staging) in Fedora 34, 35, and 36 (Rawhide) results in a compile error for only ARM 32-bit builds. Error snippet: gcc -o loader/wine-preloader loader/preloader.o loader/preloader_mac.o -static -nostartfiles -nodefaultlibs \ -Wl,-Ttext=0x7d400000 -Wl,-z,relro -Wl,--as-needed /usr/bin/ld: loader/preloader.o:(.ARM.exidx+0x8): undefined reference to `__aeabi_unwind_cpp_pr1' /usr/bin/ld: loader/preloader.o:(.ARM.exidx+0x50): undefined reference to `__aeabi_unwind_cpp_pr0' collect2: error: ld returned 1 exit status make: *** [Makefile:154942: loader/wine-preloader] Error 1 Fedora 34 full build log: https://kojipkgs.fedoraproject.org//work/tasks/7977/74857977/build.log Fedora 34 wine (NOT staging) build task: https://koji.fedoraproject.org/koji/taskinfo?taskID=74857977 -- 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 51634] New: Gaea 1.2.1.8 crashes with a managed stacktrace
by WineHQ Bugzilla 04 Sep '21

04 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51634 Bug ID: 51634 Summary: Gaea 1.2.1.8 crashes with a managed stacktrace Product: Wine Version: 6.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: u8g6kz6t(a)anonaddy.me Distribution: --- Created attachment 70491 --> https://bugs.winehq.org/attachment.cgi?id=70491 Output when running Gaea.exe with wine Gaea 1.2.1.8 (a .NET application) crashes with the following message: [...] Got a UNKNOWN while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. [...] This happens on wine-staging 6.15 on a new clean 64-bit prefix without any MS .NET frameworks or DXVK DLLs installed. -- 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 51694] New: Wine v6.16 build fails when both gcc and clang are available on the build system
by WineHQ Bugzilla 03 Sep '21

03 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=51694 Bug ID: 51694 Summary: Wine v6.16 build fails when both gcc and clang are available on the build system Product: Wine Version: 6.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: reserv0(a)yahoo.com Distribution: --- Created attachment 70565 --> https://bugs.winehq.org/attachment.cgi?id=70565 Sample of the build log Greetings, I have been building quite a few Wine versions in the past on the same build system (with gcc as the system compiler, and clang available as a secondary compiler), and everything always went fine until Wine v6.16 came out: with the latter, for some (weird) reason, the build system seems to use *both* gcc and clang to compile Wine, and fails as a result... Specifying 'export CC=gcc;export CXX=g++' does not suffice to prevent Wine's build system to wrongly pick up clang, and I must uninstall the latter to get Wine v6.16 to build successfully with gcc... Attached is a short sample of the build log (at the point where it fails too) for you to see. -- 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 49931] New: 64-bit Dota 2 randomly crashes, but 32-bit Dota 2 works perfectly
by WineHQ Bugzilla 03 Sep '21

03 Sep '21

https://bugs.winehq.org/show_bug.cgi?id=49931 Bug ID: 49931 Summary: 64-bit Dota 2 randomly crashes, but 32-bit Dota 2 works perfectly Product: Wine Version: 5.18 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- To reproduce: 1. Install Steam for Windows. 2. Install Dota 2 via `wine 'C:\Program Files (x86)\Steam\steam.exe' steam://run/570`. This will install both the 32-bit and the 64-bit version of the game. 3. Start 64-bit Dota via `wine 'C:\Program Files (x86)\Steam\steamapps\common\dota 2 beta\game\bin\win64\dota2.exe'`. 4. In the lower-right corner, click Play Dota, Practice With Bots, Solo, Start Bot Match. 5. Click on any hero, click Lock In, and wait for the game to start. Before the game starts, Dota freezes, then crashes. Sometimes it crashes before you even click Play Dota. Sometimes it crashes right after the map starts rendering. No useful information is written to the console in vanilla Wine. However, in Wine Staging, lines similar to the following are printed repeatedly right before the crash: 04b8:err:virtual:try_map_free_area mmap() error Cannot allocate memory, range 0x7f1522b50000-0x7f1522b53000, unix_prot 0x7. 04b8:err:virtual:try_map_free_area mmap() error Cannot allocate memory, range 0x7f1522c80000-0x7f1522c83000, unix_prot 0x7. 04b8:err:virtual:try_map_free_area mmap() error Cannot allocate memory, range 0x7f1523ad0000-0x7f1523ad3000, unix_prot 0x7. 04b8:err:virtual:alloc_area_in_reserved_or_between_callback Could not map in reserved area. m Files (x86)\Steam\steamapps\common\dota 2 beta\game\bin\win64\dota2.exe: ../wine-staging/dlls/ntdll/unix/virtual.c:1286: create_view: Assertion `!((UINT_PTR)base & page_mask)' failed. If you instead run 32-bit Dota via `wine 'C:\Program Files (x86)\Steam\steamapps\common\dota 2 beta\game\bin\win32\dota2.exe'`, the game runs perfectly. -- 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

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