August 2023 - Wine-Bugs - list.winehq.org

[Bug 40398] New: Aftter context_create "Failed to allocate fragment pipeline context data.", the function referenced NULL pointer.
by wine-bugs＠winehq.org Sept. 3, 2023

Sept. 3, 2023

https://bugs.winehq.org/show_bug.cgi?id=40398 Bug ID: 40398 Summary: Aftter context_create "Failed to allocate fragment pipeline context data.", the function referenced NULL pointer. Product: Wine Version: 1.9.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: blackwingcat2000(a)gmail.com Distribution: --- L63E6DACE: mov edx,[esp+50h] mov eax,[edx+0000C8F8h] mov eax,[eax] mov [esp],eax call SUB_L63F0913E mov ebx,eax <- eax returns zero ! jmp L63E6D69D L63E6D69D: mov eax,ebx call SUB_L63E6739A SUB_L63E6739A: push edi push esi push ebx sub esp,00000020h mov ebx,eax test byte ptr [L63F31078],08h jnz L63E673C6 L63E673AB: mov eax,[ebx+00000FE8h] <- Crash -- 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 4

[Bug 40175] New: bug
by wine-bugs＠winehq.org Sept. 3, 2023

Sept. 3, 2023

https://bugs.winehq.org/show_bug.cgi?id=40175 Bug ID: 40175 Summary: bug 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: regifraga_07(a)hotmail.com Distribution: --- Created attachment 53677 --> https://bugs.winehq.org/attachment.cgi?id=53677 Às vezes quando inicio o jogo apareci essa mensagem bug, quando inicio apareci uma mensagem de erro -- 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 39835] New: Fullscreen Steam popup Flickering
by wine-bugs＠winehq.org Sept. 3, 2023

Sept. 3, 2023

https://bugs.winehq.org/show_bug.cgi?id=39835 Bug ID: 39835 Summary: Fullscreen Steam popup Flickering Product: Wine Version: 1.8-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: masterderth(a)gmail.com Distribution: --- Heyo, so I've been experiencing some screen flickering when I play games in Wine. It happens when I get a popup from Steam (Linux version). To reproduce it. 1. Have Steam (Linux) running. 2. Launch a Wine game in fullscreen. 3. Alt Tab to Steam and get a friend to message you (Game must support alt tabbing). 4. Quickly go back into the Wine Game and watch the corner where popups appear at. 5. When friend messages, the screen will flicker. I've tested it with The Sims 4 and Fallout New Vegas, Origin and Steam (Windows). I am on Linux Mint 17.3 running MATE. -- 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 55498] New: Multiple application and games have difficulties connecting to their online servers
by WineHQ Bugzilla Sept. 3, 2023

Sept. 3, 2023

https://bugs.winehq.org/show_bug.cgi?id=55498 Bug ID: 55498 Summary: Multiple application and games have difficulties connecting to their online servers Product: Wine Version: 8.11 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 75061 --> https://bugs.winehq.org/attachment.cgi?id=75061 The Lord of the Rings Online default terminal output - wine 8.14 Hello, Since a few days all the applications and games I tested, that uses online services, have trouble connecting to their servers. This includes: - Steam; - Blizzard Battle.net; - World of Warships; - The Lords of the Rings Online; - Dungeons and Dragons Online. I've not tried any other windows application, yet. - World of Warships is very slow to start, and sometimes ends up with 'not connected to the server' in the port, with missing online content. I can play online matches, though, but finding a match is slower than before. I think the game tries hard to start and to reconnect. - Blizzard Battle.net often fails to connect for the login screen. It says 'connecting' for a minute and then shows an blz#### splash screen with buttons to go 'offline' or exit. It sometimes manages to connect, but then can fails to load the online content (world of warcraft videos and news feed for instance), with a message to retry. - Steam is just being slow to open and to display online content, sometimes staying at a blank space; It's overall functioning. - The Lords of the Rings Online and Dungeons and Dragons Online both have slowdowns when opening their respective launchers, and connecting to the world servers fails constantly after several retries (20 retries in 1 sec. each). Sometimes, the launcher display an error message about a socket error. I attach the terminal output from The Lords of the Rings Online as it's the one that does the most visible retries at connecting to its server and is constantly failing. The issue is present with my compiled wine version (from 8.11 to 8.14), as well as the Debian wine 8.0~repack-4 package and the winehq-devel 8.14~bookworm-1 package (Those two I tested to be sure it was not my builds that were broken). I've upgraded to Debian 12 in mid-July. All those applications and games were working by then, with wine 8.11. I don't know what has changed on my system since then that has broken everything. There were a few kernel updates and also updates to those applications (WoWs 12.7, Steam on 1st of August, LOTRO & D&DO had an in-game shop update, blizzard had an update, etc. but the symptoms seem common and I doubt they are caused by individual updates. I also have no more sound from another offline game that worked in July and had no update as it doesn't connect to internet at all, but I'll leave that sound issue for later. It may be a kernel/system library update, though. I have no problem accessing internet from Linux programs including the native Steam & Discord clients. My system is Debian 12 Bookworm with 32 GB of RAM. NVidia RTX 2070 with proprietary driver 535.104.05. 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 54981] New: Visio 2003 When using ux theme icons are not rendered on object property panels
by WineHQ Bugzilla Sept. 3, 2023

Sept. 3, 2023

https://bugs.winehq.org/show_bug.cgi?id=54981 Bug ID: 54981 Summary: Visio 2003 When using ux theme icons are not rendered on object property panels Product: Wine Version: 8.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winebugs(a)copysoft.org Distribution: --- Created attachment 74520 --> https://bugs.winehq.org/attachment.cgi?id=74520 Icons in Visio2003 property panels are rendered blank when using light theme. When using Visio 2003 in Wine 8.7 and 8.8 when the "Light Theme" is enabled in the Desktop Integration panel of the Wine configuration if I select properties in an object the icons are drawn blank, if I select "no theme" the icons are drawn normally. -- 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 10

[Bug 54959] New: winhttp:notification - test_websocket() times out on Windows and Wine
by WineHQ Bugzilla Sept. 3, 2023

Sept. 3, 2023

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 Sept. 3, 2023

Sept. 3, 2023

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 Sept. 3, 2023

Sept. 3, 2023

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 Sept. 3, 2023

Sept. 3, 2023

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 Sept. 3, 2023

Sept. 3, 2023

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