wine-bugs June 2023

wine-bugs@winehq.org

1 participants
2480 discussions

[Bug 54959] New: winhttp:notification - test_websocket() times out on Windows and Wine
by WineHQ Bugzilla 03 Sep '23

03 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=54959 Bug ID: 54959 Summary: winhttp:notification - test_websocket() times out on Windows and Wine Product: Wine Version: unspecified Hardware: x86-64 OS: Windows Status: NEW Severity: normal Priority: P2 Component: winhttp Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com winhttp:notification - test_websocket() times out on Windows and Wine: notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000 notification.c:118: Test failed: 994: expected status 0x20000 got 0x1 notification.c:123: Test failed: 994: expected callback 0x1 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x2 notification.c:123: Test failed: 994: expected callback 0x2 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x4 notification.c:123: Test failed: 994: expected callback 0x4 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x8 notification.c:123: Test failed: 994: expected callback 0x8 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x10 notification.c:123: Test failed: 994: expected callback 0x10 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x20 notification.c:123: Test failed: 994: expected callback 0x20 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x40 notification.c:123: Test failed: 994: expected callback 0x40 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x80 notification.c:123: Test failed: 994: expected callback 0x80 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000 notification.c:123: Test failed: 994: expected callback 0x4000 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x10 notification.c:123: Test failed: 994: expected callback 0x10 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x20 notification.c:123: Test failed: 994: expected callback 0x20 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x40 notification.c:123: Test failed: 994: expected callback 0x40 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x80 notification.c:123: Test failed: 994: expected callback 0x80 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000 notification.c:123: Test failed: 994: expected callback 0x4000 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x10 notification.c:123: Test failed: 994: expected callback 0x10 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x20 notification.c:123: Test failed: 994: expected callback 0x20 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x40 notification.c:123: Test failed: 994: expected callback 0x40 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x80 notification.c:123: Test failed: 994: expected callback 0x80 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000 notification.c:123: Test failed: 994: expected callback 0x4000 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x10 notification.c:123: Test failed: 994: expected callback 0x10 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x20 notification.c:123: Test failed: 994: expected callback 0x20 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x40 notification.c:123: Test failed: 994: expected callback 0x40 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x80 notification.c:123: Test failed: 994: expected callback 0x80 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000 notification.c:123: Test failed: 994: expected callback 0x4000 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x10 notification.c:123: Test failed: 994: expected callback 0x10 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x20 notification.c:123: Test failed: 994: expected callback 0x20 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x40 notification.c:123: Test failed: 994: expected callback 0x40 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x80 notification.c:123: Test failed: 994: expected callback 0x80 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000 notification.c:123: Test failed: 994: expected callback 0x4000 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x10 notification.c:123: Test failed: 994: expected callback 0x10 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x20 notification.c:123: Test failed: 994: expected callback 0x20 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x40 notification.c:123: Test failed: 994: expected callback 0x40 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x80 notification.c:123: Test failed: 994: expected callback 0x80 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000 notification.c:123: Test failed: 994: expected callback 0x4000 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x10 notification.c:123: Test failed: 994: expected callback 0x10 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x20 notification.c:123: Test failed: 994: expected callback 0x20 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x40 notification.c:123: Test failed: 994: expected callback 0x40 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x80 notification.c:123: Test failed: 994: expected callback 0x80 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000 notification.c:123: Test failed: 994: expected callback 0x4000 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x10 notification.c:123: Test failed: 994: expected callback 0x10 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x20 notification.c:123: Test failed: 994: expected callback 0x20 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x40 notification.c:123: Test failed: 994: expected callback 0x40 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x80 notification.c:123: Test failed: 994: expected callback 0x80 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000 notification.c:123: Test failed: 994: expected callback 0x4000 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x10 notification.c:123: Test failed: 994: expected callback 0x10 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x20 notification.c:123: Test failed: 994: expected callback 0x20 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x40 notification.c:123: Test failed: 994: expected callback 0x40 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x80 notification.c:123: Test failed: 994: expected callback 0x80 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x4000 notification.c:123: Test failed: 994: expected callback 0x4000 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x10 notification.c:123: Test failed: 994: expected callback 0x10 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x20 notification.c:123: Test failed: 994: expected callback 0x20 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x40 notification.c:123: Test failed: 994: expected callback 0x40 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x80 notification.c:123: Test failed: 994: expected callback 0x80 to be called from the same thread notification.c:118: Test failed: 994: expected status 0x20000 got 0x200000 notification.c:123: Test failed: 994: expected callback 0x200000 to be called from the same thread winhttp:notification:1448 done (258) in 120s 9182B This is not a regression but rather an issue with the server. lsof shows the test stuck with a connection to 104.21.29.32 (but that's a CloudFlare IP). So the server's behavior must have changed recently and if that's not temporary the test will need to be adjusted. -- 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 54795] New: configure fails to find pcap development libraries with libpcap <1.9.0 present
by WineHQ Bugzilla 03 Sep '23

03 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=54795 Bug ID: 54795 Summary: configure fails to find pcap development libraries with libpcap <1.9.0 present Product: Wine Version: 8.2 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: wpcap Assignee: wine-bugs(a)winehq.org Reporter: o.dierick(a)piezo-forte.be Distribution: --- Hello, In my case, Debian 8 "Jessie" ships libpcap 1.6.2. According to the man page, pcap_init was introduced in libpcap 1.9.0. https://man7.org/linux/man-pages/man3/pcap_init.3pcap.html The ~regression~ commit modifies configure to check for pcap_init() in lieu of pcap_create(), which fails on such old OS. 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 7

[Bug 54730] New: EverQuest: game compositor freezes during account switching
by WineHQ Bugzilla 03 Sep '23

03 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=54730 Bug ID: 54730 Summary: EverQuest: game compositor freezes during account switching Product: Wine-staging Version: 8.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: johnherschelfreeman2013(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 74235 --> https://bugs.winehq.org/attachment.cgi?id=74235 log after switching to another account and returning to account with game running During a switch to another account compositor window freezes and when switching back to account executing the wine process video does not update in the compositor window -- 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 46405] New: steam: crashes when opening game
by wine-bugs＠winehq.org 03 Sep '23

03 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=46405 Bug ID: 46405 Summary: steam: crashes when opening game Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: yuettingng(a)gmail.com Distribution: --- Created attachment 63166 --> https://bugs.winehq.org/attachment.cgi?id=63166 program error details Game crashes when I started to play on steam -- 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 6

[Bug 45983] New: Not working gamepad in windows steam games
by wine-bugs＠winehq.org 03 Sep '23

03 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=45983 Bug ID: 45983 Summary: Not working gamepad in windows steam games Product: Wine-staging Version: 3.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nickfaces(a)gmail.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- With 3.18-staging not working gamepad in windows steam games. No errors in terminal. The problems in Arch and Ubuntu 18 -- 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 5

[Bug 45751] New: Sniper Elite V2 has missing objects or invisible textures
by wine-bugs＠winehq.org 03 Sep '23

03 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=45751 Bug ID: 45751 Summary: Sniper Elite V2 has missing objects or invisible textures Product: Wine Version: 3.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: noonetinone(a)gmail.com Distribution: --- Sniper Elite: V2 has missing objects or invisible textures in the main menu. Gameplay is unaffected. The has occurred between 3.10 & 3.11 wine releases. The problems has been present since then. I took the liberty to bisect the offending commit. It is below. ________________________________________________________________________ 537007525a8909a2295bd7cd123f0eb6ce1b77cb is the first bad commit commit 537007525a8909a2295bd7cd123f0eb6ce1b77cb Author: JÃ³zef Kucia <jkucia(a)codeweavers.com> Date: Tue Jun 19 17:15:00 2018 +0200 wined3d: Use WINED3D_LOCATION_DISCARDED before initializing buffers with data. Signed-off-by: JÃ³zef Kucia <jkucia(a)codeweavers.com> Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com> Signed-off-by: Alexandre Julliard <julliard(a)winehq.org> :040000 040000 2dcb8443ae6f5ac506801053163f0b21be4af81d 0e4abd89b101fb9f27c0273cecfb4af3f71a901a M 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 23

[Bug 54770] New: missing check of malloc in loader/main.c
by WineHQ Bugzilla 03 Sep '23

03 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=54770 Bug ID: 54770 Summary: missing check of malloc in loader/main.c Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: loader Assignee: wine-bugs(a)winehq.org Reporter: void0red(a)gmail.com Distribution: --- we put a fault injection fuzzing on wine, and find two potential bugs in loader/main.c. it may miss a malloc check before memcpy the call stack looks like this: main -> load_ntdll -> get_self_exe -> build_path -> memcpy main -> load_ntdll -> remove_tail -> memcpy -- 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 54665] New: Can't install EduPython
by WineHQ Bugzilla 03 Sep '23

03 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=54665 Bug ID: 54665 Summary: Can't install EduPython Product: Wine Version: 8.0-rc5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: villemurclement(a)gmail.com Distribution: --- Created attachment 74180 --> https://bugs.winehq.org/attachment.cgi?id=74180 Crash Report Before with wine 7.x it was working fine. Today I reinstalled my Debian and install Wine 8.0 and when I was trying to install EduPython it was not working. -- 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 54438] New: Wine 8 Stage -> shell32.dll -> wrong icon and hold not the standart of Windows
by WineHQ Bugzilla 03 Sep '23

03 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=54438 Bug ID: 54438 Summary: Wine 8 Stage -> shell32.dll -> wrong icon and hold not the standart of Windows Product: Wine-staging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: blackcrack(a)blackysgate.de CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 73987 --> https://bugs.winehq.org/attachment.cgi?id=73987 Screenshot of the Desktop with running wine and Listerplugin for show the shell32.dll icons I use Fedora 37 (more in the Screenshoot of versioning) i guess there be troubles of over watching the Standards ? okey, i be not a programmer as so in c, c++ and assembler, but i be now more 25 Jears in the net and at 1999 directly at Linux, but this, wonder me sure .. because i have logging me in at WineHQ : the most heart of WinNT API, so in Wine is really wrong.. and you have not note that before you have make a release ? wow.. heavy, this let show how less you have you code under over watching and cleaning up. i have in the last times again install wine in Fedora and have a bit an eye on it.. because i use Total commander from Cris and have use an couple icons into the Buttonbar from shell32.dll as standard Icons, because i have noticed, there be wrong icons in the shell32.dll and i have thing.. wth.. wrong icons what's goes on.. and i work over smbfs down from a server in my basement and i have a serverinfrastructure via fedora(at moment 37) with smbfs and nfs for my linuxclients and use the same Total Commander from Chris for all Win32/64 Systems/API's down from the network, where i have noticed to be something wrong in the wine shell32.dll.. now my question.. do you not check over the files before you get out an version.. okey, in clear text: Shell32.dll have the wrong ICONS (and use no standard), look on the Picture attachemnt. All Version's informations it is see in the Screenshot Attachment. this is my first Bugreport here in WineHQ.. as a old man...oh wrong, old Geek ;) best regards to the Team :) Blacky p.s.: and please, before you release an Wine-release, check also the files and don't give out something ...hmmm (no, i say not crap *g*) we have now a couple time behind us..(Wineteam and i am as user...) and there is not a really making better Wine in Linux like it is now.. a bit wrong... and, me wonder, also Reactos have Wine in the fingers.. and they are have say nothing about shell32.dll and the icons ?| ui... so, all the best :) -- 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 14

[Bug 49839] New: Steamwebhelper.exe crashes when running Steam
by WineHQ Bugzilla 03 Sep '23

03 Sep '23

https://bugs.winehq.org/show_bug.cgi?id=49839 Bug ID: 49839 Summary: Steamwebhelper.exe crashes when running Steam Product: Wine Version: unspecified Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: drnefarius(a)hotmail.com Created attachment 68178 --> https://bugs.winehq.org/attachment.cgi?id=68178 steam webhelper crashing high sierra SteamWebHelper keeps crashing. Steam will run, but the online contents, such as the store, the library, news, etc. are all left blank. I can log into Steam though, and update and download games. But I cannot run the game. This is for Tracks The Train Set Game. -- 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

Jump to page:

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 June 2023