January 2025 - Wine-Bugs - list.winehq.org

[Bug 57636] New: Regression: Black screen in menu until button click in Age of Empires

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57636 Bug ID: 57636 Summary: Regression: Black screen in menu until button click in Age of Empires Product: Wine Version: 10.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: krkos(a)mail.muni.cz Distribution: --- The bug affects original Age of Empires with UPatch HD 1.2 Release 3. Upon program startup, the screen is black and stays that way until a button in the menu (invisible) is clicked, then it is painted correctly. This was bisected to be caused by 786d9d1685ac220081b10cc779d4d331ddd2fc52 winex11: Skip offscreening if the children don't require clipping. The bug is still present in 10.0-rc4. -- 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.

Jan. 5, 2025

[Bug 57635] New: Battle.net Launcher invisible/black with the Wayland driver

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57635 Bug ID: 57635 Summary: Battle.net Launcher invisible/black with the Wayland driver Product: Wine Version: 10.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winewayland Assignee: wine-bugs(a)winehq.org Reporter: wine(a)xarov.net Distribution: ArchLinux Created attachment 77764 --> https://bugs.winehq.org/attachment.cgi?id=77764 Black window with Wayland driver Works fine with the X11 driver. Is completely black with the Wayland driver. -- 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.

Jan. 5, 2025

[Bug 57628] Simple StackWalk64 code example doesn't produce output as expected

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57628 --- Comment #5 from tuxifan(a)posteo.de --- (In reply to Eric Pouech from comment #4) > is this snipnet derived from a real application? If so, can you share which > one? Yes, however I unfortunately can't easily share that application or give further information about it :-( I wrote that code snipped to isolate the issue that occurs within that application, also so that I can simply share it here. -- 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.

Jan. 5, 2025

[Bug 57632] fallout 3 radio broke with gstreamer 1.24.10 (9.22 silent, 10rc4 stalls)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57632 Béla Gyebrószki <gyebro69(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression CC| |gyebro69(a)gmail.com, | |z.figura12(a)gmail.com Regression SHA1| |e6b8e9ee20937f12dbf19145a9f | |2ca1ca3364da3 --- Comment #11 from Béla Gyebrószki <gyebro69(a)gmail.com> --- I can reproduce the problem using the savegame from comment #10. The game locks up immediately after the game was loaded as soon as music begins to play. 0024:err:sync:RtlpWaitForCriticalSection section 003F2C98 "../wine-git/dlls/winegstreamer/quartz_parser.c: pin.flushing_cs" wait timed out in thread 0024, blocked by 01bc, retrying (60 sec) This is a regression from Wine-10.0-rc1: commit e6b8e9ee20937f12dbf19145a9f2ca1ca3364da3 quartz/dsoundrender: Use send_sample_data() to fill the buffer with silence at EOS. Reverting the patch fixes the problem for me. The other issue the bug reporter mentioned: the savegame loads but music doesn't start to play with Wine-9.22. That seems to be another possible regression somewhere between Wine 9.5 and 9.8 which yet to be found. -- 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.

Jan. 5, 2025

[Bug 57634] New: RFE: individual DPI

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57634 Bug ID: 57634 Summary: RFE: individual DPI Product: Wine-staging Version: 9.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ToddAndMargo(a)zoho.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Request for Enhancement: Currently `wine explorer /desktop=...` has two parameters: title and resolution. Would you please consider adding a third parameter for Dots Per Inch (DPI) for only the program being called. For instance wine explorer /desktop=title,resolution,dpi wine explorer /desktop=`date +%%H:%%M:%%S`_wine_virtual_desktop_1680x1050,1680x1050,100 approach.exe This would be of great benefit for those of us with high resolution monitors. Many thanks, -T -- 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.

Jan. 5, 2025

[Bug 57633] Lotus Approach and Word Pro have graphic issues with high resolution monitors

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57633 --- Comment #1 from Todd Chester <ToddAndMargo(a)zoho.com> --- Additional information . The graphics problems happen at resolutions above 1680x1050. -- 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.

Jan. 5, 2025

[Bug 57629] Wine Internet Explorer has encountered a program error in Wine 10.0-rc3

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57629 --- Comment #2 from SuperVictor64 <supervictor64(a)proton.me> --- (In reply to Fabian Maurer from comment #1) > Seems to work for me. Can you try in a clean WINERPEFIX and attach a > complete log? I created a clean WINEPREFIX and tried running Wine Internet Explorer again in the clean WINEPREFIX but it still didn't work for me. -- 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.

Jan. 5, 2025

[Bug 57632] fallout 3 radio broke with gstreamer 1.24.10 (9.22 silent, 10rc4 stalls)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57632 --- Comment #10 from zlice <zlice(a)crtdrift.us> --- Created attachment 77763 --> https://bugs.winehq.org/attachment.cgi?id=77763 fallout_3_save save outside 101 with "inkspots - maybe" about to come on -- 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.

Jan. 5, 2025

[Bug 57632] fallout 3 radio broke with gstreamer 1.24.10 (9.22 silent, 10rc4 stalls)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57632 --- Comment #9 from zlice <zlice(a)crtdrift.us> --- the real problem seems to be 'when a new song plays' if you have a song that is ABOUT to play, and you turn off the radio, and wait some time for it to start, then turn the pipboy radio on, it seems to play fine. wine 10 still hard freezes when a new song starts and you have to kill it. (gstreamer 1.24.9 or 1.24.10) wine 9.12, 9.13, 9.14, 9.18, 9.19 - may have a higher chance to actually play a song at start? at least sometimes they will play a song at start. 9.20, 9.21, 9.22 i don't think i got a radio song to play at start at all -- 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.

Jan. 5, 2025

[Bug 57632] fallout 3 radio broke with gstreamer 1.24.10 (9.22 silent, 10rc4 stalls)

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57632 --- Comment #8 from zlice <zlice(a)crtdrift.us> --- well, i downgraded, things worked, then re-upgrade, things work. not entirely sure what it is. i did wait for a new song to start playing and toggled on/off/on world + pipboy radios. i'll try to sit there and let it play just to see if it's a specific file or something weird. probably a botched update though? -- 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.

Jan. 4, 2025